v0.2.0 Limitations¶
This page records the known limitations for the v0.2.0 local lab release so
downstream work can focus on the highest-value gaps without rediscovering them.
Scope Boundary¶
- The documented happy path is local Docker on a developer workstation.
- Remote Flexo and SysON endpoint profiles are not a release promise, even though several commands accept explicit URL options.
- This repo is tooling, not a private model repository. Real models, private exports, rendered snapshots, run logs, and evidence bundles should live in a private model workspace.
Bridge And Model Fidelity¶
- The Flexo-to-SysON path is snapshot based:
- Live bidirectional synchronization between Flexo and SysON is not implemented.
- Diagram layout and SysON graphical views are not round-tripped.
- The renderer emits only the conservative subset documented in
docs/lab/modeling-conventions.md. - Requirement satisfaction, derivation, verification relationships, allocation, imports, metadata, multiplicities, value expressions, and many specialized SysML v2 relationship forms are not rendered yet.
- Unsupported elements remain preserved in the raw Flexo JSON export but are not
emitted into the
.sysmlsnapshot. - Render coverage reports count rendered, skipped, and unsupported elements, but they are not yet impact analyses or semantic diffs.
SysON Import Behavior¶
- SysON import depends on SysON's textual SysML parser and project/template behavior.
- A successful textual import does not guarantee that useful diagrams or graphical layouts appear automatically.
- The routine bridge command can create a SysON review project, but lower-level import commands still require users to provide an existing target project and namespace.
Deployment And Runtime Operations¶
- The Docker Compose stacks are intended for local lab use, not production hosting.
- Routine stop commands preserve runtime data, but full lifecycle management of SysON database backup/restore is not yet automated.
- Flexo graph backup support exists, but users must choose when graph state is important enough to persist.
- Runtime credential handling is local-file based. The repo does not integrate a production secrets manager.
- Port conflict handling relies on documented
.envoverrides and diagnostics, not automatic port selection.
Verification¶
make checkand deterministic evals do not require live services.- Live evals are optional and require the local Docker stacks to be running.
- The default CI path does not start the full Flexo and SysON runtime on every push.
- Share-safety checks are guardrails, not a complete secret-detection solution.
Packaging And Release¶
- Installation from GitHub and editable local installs are documented.
- Publishing to PyPI is deferred beyond
v0.2.0. - Shell completion snippets are generated, but installer-specific completion setup is left to users.
Model And Template Coverage¶
- The MBSE lab tool-system model is an initial backbone model. It captures landed requirements, architecture, workflows, and verification concepts, but rich trace relationships are limited by the current renderer.
- Published model fixtures are synthetic and intentionally small.
- Rich reusable model templates are deferred beyond the tiny
first-modelworkflow.
Downstream Development Focus¶
Recommended post-v0.2.0 focus areas:
- Add fixture coverage for more SysML v2 element types and keep the bridge capability matrix tied to deterministic tests.
- Add snapshot diffing between Flexo exports and rendered SysML snapshots.
- Expand renderer support for traceability relationships and requirement verification structure.
- Turn render coverage reports into deeper semantic impact analyses.
- Add CLI backup/restore polish for both Flexo and SysON runtime state.
- Decide whether remote endpoint profiles are in scope.
- Promote model specs into reusable model templates.