This catalogue describes the current implementation. Check verification for checks actually performed; a feature description alone is not test evidence.
| Workflow | Support | Limit |
|---|---|---|
| Entry and shell | OpenMBEE landing, explicit project launcher, example/new/import/recovery actions; live-session resume and browser navigation | Folder write-back and remote checkout remain planned; exploration scope/camera are transient |
| Model exploration | Read-only nested project/package ownership overview and explicit part-definition/usage tree or compact structural projection without view declarations; independent source-file navigation | No inferred system root, automatic typed-instance expansion, exploration persistence or graphical editing |
| Project sources | Multiple imported SysML files resolve together | 20 files / 5 MiB per source set; one active source editor |
| Source editing | CodeMirror lexical highlighting, line numbers, bracket matching/closing, indentation, find/replace, Toolkit draft formatting, draft history, apply/discard and accepted source history | Toolkit formatting remains a draft until apply; no inline diagnostics or syntax-aware folding; unsafe declaration/context matches lose affected positions |
| Source assistance | Toolkit completion, hover, project-file definitions and references bound to the full current draft source set | Explicit plain-text completion only; snippets/additional edits, ambiguous and library-only definition targets are unavailable |
| Named views | Open declarations; create GeneralView/InterconnectionView usages in a package | Custom filters/definitions remain editable in source |
| Diagram rendering | Native requirement graphs with identifiers, documentation, typing, direct/type-based ownership and declared positive/negated satisfaction; flat tree views; nested interconnection parts, declared attribute compartments, ports and resolved endpoints; bounded native action/state diagrams with initial/final nodes and directed relationships | Requirement constraints/subject compartments, generalized typed-instance trace expansion, owned-port boundary notation, effective conjugated directions, modeled layout/routes and case/mixed/sequence/geometry renderers remain future work |
| Semantic editing | Reviewed part definition/usage rename, native view creation, typed part creation and directed same-type port connections | Simple identifiers and qualified names; explicit out/inout to in/inout with identical resolved types; conjugated, ambiguous or undirected endpoints, reconnect, delete, duplicate and behavior editing are unavailable |
| Model navigation | Expandable ownership tree, declared members, type/kind labels, keyboard navigation and diagram-selection reveal | View declarations use the separate Views list; inherited members are not cloned beneath usages; no full-model search or virtualized rendering |
| Source navigation | Recorded origin range from diagram/port selection, snapshot-bound Issues file/line navigation and explicit file-only handling | Explorer-only selection does not yet resolve a source range; stale, unknown and out-of-range diagnostic locations are explained without guessing |
| Diagram presentation | Move nested groups, retain descendant positions, reconcile compatible positions across reviewed edits and bounded source changes, save/reopen and refit panes | Changed bindings, headers, owners or ambiguous correspondence invalidate affected positions; manual overlap avoidance, parent resizing, camera persistence, route edits and independent layout undo remain future work |
| Workbench panels | Resizable Explorer, Inspector, source/diagram split and Issues; collapse/restore, keyboard and button resizing, reset and browser layout preferences | Full docking/floating windows are unavailable; preferences do not recover source work |
| Save/reopen | Version-1 bundle of source, drafts and positions; local recovery with explicit restore/discard and active file/view | One IndexedDB recovery copy per browser origin; storage can be cleared or unavailable; no camera persistence or folder write-back |
| Runtime validation | TypeBox project/command/message/engine schemas | Schema validity is separate from SysML semantic validity |
| Appearance | Shared shadcn/Radix controls; Light/Dark/System, six palettes and custom muted package/part fills | Browser preferences, separate from project files; detailed port color controls remain unavailable |
| Execution | No simulation controls | Rendered behavior or declared verify links would not imply execution results |
This repository does not claim full SysML v2 language, notation, execution or interchange conformance.
Requirements diagrams are read-only for graphical model edits. They retain native selected versus related-context elements, expose full available documentation in the Inspector, and reveal exact node/relationship source ranges through pointer or keyboard selection. Satisfaction and negated satisfaction are declarations, not executed verification results. Their positions use the existing portable presentation flow; keyboard movement is retained as well as pointer movement. See requirements projection and limits.
Use New part and Connect ports in supported structural diagrams, or the corresponding Inspector actions, to review source-backed creation commands. Part creation chooses an explicit source owner and existing definition; connections choose actual usage-qualified endpoints. Toolkit supplies source edits, OpenSysML validates the complete candidate, and the workspace checks ownership, bindings and exact connection endpoints before accepting one transaction. New symbols receive automatic layout; source exposure still determines whether they appear in an open view.
Layout reconciliation checks every saved view, including inactive views. Verified commands use source-bound UTF-8 splices; free-form edits use conservative replacement ranges and require unchanged engine-recorded declaration headers, complete usage contexts and compatible resolved bindings. Unknown or ambiguous mappings are invalidated explicitly. This is bounded preservation, not a general persistent-identity guarantee. See the implemented policy and authoring contracts.
The explicit Load example project is Inspection rover: six source files and five views covering architecture, mission, lifecycle, requirements and component definitions. All five render bounded projections; their catalog entries retain limits. Inspection rover is the only bundled example; the legacy Smart air workshop remains available for explicit source import and regression coverage. Declared attributes show effective source members, with shorter labels for simple scalar defaults and exact declaration text on hover. Larger named structural diagrams use narrower cards and tighter spacing. Values are not evaluated. Action/state graphs show authored behavior, not execution.
The visualization example library records representative models, named views, intended visual quality and current gaps. Its checks distinguish successful engine evaluation from application rendering; use-case, package-graph and other unsupported renderer fixtures remain explicit development targets.
The read-only requirements table inspects all applied requirement declarations, identifiers, owned documentation and declared satisfaction/verification links. It supports search, name sorting and CSV export. The traceability matrix uses requirements as rows and linked satisfiers/verifiers as columns, retaining exact declaration identities and negation. It does not infer missing relationships, compute verification verdicts or edit model content. Unknown/incomplete extraction is unavailable rather than an empty result. Source reveal requires that file's draft to match applied source. Requirements data contract.
The optional Guide in the project header introduces Explorer, layout, source application, model representations and project download for any open project. It can be dismissed and restarted, and does not alter project data.