OpenMBEE View Editor is a sandbox browser workspace for SysML v2 source and named views. This index separates current behavior, implementation contracts and planned work. Setup and everyday use live in the project README.
| Guide | Purpose |
|---|---|
| Capabilities and limits | What the application supports today |
| Next steps | Current priorities and the gates for future work |
| Architecture | Module ownership, engine boundaries and transaction rules |
| Design system | Shared shadcn controls, themes and UI conventions |
| Testing | Running checks, reviewing baselines and diagnosing failures |
| Verification | Latest recorded results, regression evidence and coverage limits |
| Git workflow | Branches, PR targets and release integration |
| Guide | Purpose |
|---|---|
| Application shell | Landing, launcher, navigation and session preservation |
| Workbench layout | Panels, toolbar alignment, model tree and editor lifetime |
| Source editing and recovery | Draft queries, issue navigation and browser recovery |
| Structural views | Hierarchy, ports, connections and geometry projection |
| Requirements and satisfaction | Native graphs, identifiers/docs, relationship polarity, source reveal and bounded limits |
| Graphical authoring | Reviewed semantic commands and supported endpoint rules |
| Identity and layout preservation | Identity domains, verified edits and conservative invalidation |
| Project format | Portable version-1 data and compatibility rules |
- Read-only requirements data: source-bound tables, matrices, CSV and preservation rules.
- OpenSysML 0.12 compatibility: ported overlay seams and real-worker evidence.
- Model exploration: bounded read-only browsing without authored views and its remaining opening/persistence work.
- Exploration engine investigation: pinned renderer/WASM evidence and the next contract boundary.
- Flexo MMS integration: dated source research and unresolved interchange/concurrency gates; not implemented.
Related sources: domain glossary, engine preparation and provenance, example library, contribution guide.
Keep current behavior in capabilities and owning contracts; put future acceptance criteria in the roadmap or exploration plan. Verification records observations, not promises. Superseded milestone narratives remain available in Git history rather than parallel archive documents. Local sandbox/ evidence paths are ignored artifacts and may be absent from another checkout.