Skip to content

next-steps.md

Latest commit

 

History

History
51 lines (29 loc) · 5.52 KB

next-steps.md

File metadata and controls

51 lines (29 loc) · 5.52 KB
Raw

Next steps

Updated 2026-11-05. This is the forward plan; capabilities describes shipped behavior and verification records actual checks. No delivery dates are assigned.

Current position

The editor supports reviewed rename/view/part/connection commands, bounded layout preservation, CodeMirror source editing and draft language queries, issue navigation, resizable panels and explicit browser recovery. The OpenMBEE landing → launcher → workbench flow is implemented. Opening the app does not load an example implicitly. The in-progress feature/automatic-exploration slice also opens project/package overviews and explicit part subjects without authored views.

1. Requirements and satisfaction diagrams

Merged into develop through PR #10 on 2026-11-05: a bounded native requirements renderer, with identifiers/documentation, typing/ownership, declared satisfaction polarity, source reveal and presentation preservation. The capacity and traceability fixtures establish this subset; the compressor requirements view remains a generic tree. Declared satisfaction is not a test result. Verification coverage and graphical relationship authoring remain separate follow-ups.

2. Read-only automatic exploration

The first bounded slice inspects an imported model without adding view declarations. Use a project/package overview when a system subject is ambiguous; offer structural exploration only where the engine demonstrates the intended definition or usage expansion.

The engine investigation is complete for its bounded probes: native RenderExposed now has a separate validated browser-worker operation for overview and explicit structural subjects. The tested typed usage did not unfold its definition's internals. Automatic system-root selection and generalized usage expansion still need proof before promising a consolidated system diagram.

Acceptance is owned by the exploration plan:

  • No-view and multi-file/multi-system imports open useful, correctly scoped projections.
  • Scope, representation and source-file navigation remain independent; repeated usages retain their context.
  • Browsing and failed/superseded evaluation preserve exact source, drafts, semantic history and saved named-view positions.
  • Temporary exploration does not modify source or borrow another subject's geometry.
  • Actual-engine browser, keyboard and desktop/narrow light/dark checks establish the delivered subset.

Then add reviewed named-view creation from an exploration and define browsing-context persistence. Portable bundles and recovery do not currently store exploration scope/representation; any format change needs schema/version and compatibility fixtures.

3. Local folder workflow

Start with explicit import semantics: membership, exclusions, source limits, permission cancellation and unsupported-browser fallback. Existing Open imports copies and Download exports a bundle.

Direct file saving is a separate gate: identify written files, validate permission, detect external changes and retain local work on failed or ambiguous writes. Do not label imported copies as folder-backed editing. See shell capability gates.

4. Flexo checkout, then reviewed publication

Follow the integration research: prove unchanged interchange and foreign element identity preservation on a pinned deployment, then read an immutable commit selected through project/branch. Identify generated authoring text explicitly.

Publication follows only after one reviewed command preserves repository UUIDs and unedited semantics, with server-enforced stale-head rejection and defined retry/ambiguous-outcome handling. Authentication, conversion and publication failures must retain local work. No deployment/authentication target has been selected here.

Follow-on usability and rendering

Named structural and bounded action/state diagrams now retain generated orthogonal routes and labels. Follow-on edge interaction and routing work includes accessible endpoint descriptions, hit targets and obstacle rerouting after arbitrary individual-node movement. Read-only exploration retains its separate routing geometry.

  • Consistent selection and source/canvas reveal, including Explorer-only selection; model-wide search and discoverable language shortcuts.
  • Broader structural notation, effective conjugated directions and new representation families, each backed by actual engine/renderer evidence.
  • Accessibility and large-model performance work based on measured workflows.

Keep arbitrary source reconciliation conservative; general persistent identity, independent layout undo, camera persistence, reconnect/delete/duplicate and behavior editing remain gaps. Use the authoring contract, identity policy and example targets when extending them. Completed assembly milestones and earlier delivery sequences are retained in Git history, not repeated as pending work.

The inspection-rover showcase now has bounded named action/state rendering and effective declared-attribute compartments. Remaining representation work includes case/mixed/sequence/geometry families and richer notation, each requiring independent engine and renderer evidence; execution and behavior editing remain separate work.