Task Ledger — first release

Authoritative objective: attachment10134df9-bea2-4c02-a820-67b53d6b86f7/ goal-objective.md, read fully2026-09-06. STATE.md records execution; PLAN.md retains scope; DECISIONS.md and linked contracts preserve rationale.

Goal and success criteria

System engineers develop and iteratively reconcile OA/SA models through equivalent graphical, textual and REST workflows. Rust/Iced Windows/Linux, strict reST, traceability, navigable offline guidance and reproducible deployment. Acceptance requires native workflows, semantic evaluators and fresh independent review.

Given facts

User prioritizes Capella domain fidelity, hierarchy, typed ports and intuitive transitions in both directions, without its clutter and navigation friction.
Direct exchange drawing must avoid large endpoint dropdowns; ports must move between sides; contextual menus should replace persistent action clutter.
Modular source must be practical for humans/AI and Git. Text/graph/API parity is required. Behavior canvases must support editing and preserve drag selection.
Git/worktrees are authorized. Remote publication is not requested.

Verified facts

Original Capella SAB creates FE function input/output endpoints; component ports are separately Standard/Flow with explicit allocation. Native observations are in release-capella-workflow-benchmark.md; adopted contracts preserve that distinction.
Explorer/port discovery, editable routing, nested modular source and coupled REST bundles have scoped Windows/Linux acceptance. Evidence links are in STATE.md.
Direct palette connections, four-side port anchors, context menus and source folders passed real Windows/Linux operation. Passive stacked Canvas fixes native tooltip overprint; separate Frames did not. See release-port-drawing.md.
Persisted state editing now passes Windows/Linux native and independent review: creation, movement, direct transitions, typed forms, reconnection, fold/reopen. See release-state-editing.md. Scenario/process canvases still need direct editing.
Ordinary Document commands atomically synchronize source/model; failed writes retain drafts. Source comments require occurrence/provenance-aware edits, not whole-model equality or flat reformatting. Independent counterexamples were fixed.
R3 existing-target reconciliation remains name/description only. R6 data shape expansion is active implementation, not accepted functionality.
R6 core/source and actual HTTP semantics pass focused Windows and full Linux core checks; desktop257 tests pass after independent draft/path/paging fixes. Native R6 acceptance and bounded scenario-value authoring remain outstanding.

Assumptions and open questions

Nested aggregate files reduce cognitive load; any additional port/exchange/step shorthand must justify grammar complexity through real authoring tasks.
State placements proved viable without a second geometry system. Scenario/chain gestures still need their own occurrence/order semantics and task verification.
Routing offers a usable initial path plus manual pins; arbitrary dense diagrams are not guaranteed crossing-free. Measured dense full solve119ms remains a limit.
R3 typed historical bodies plus finite proposals appear simpler than a separate recursive semantic-value schema. An isolated probe supports scalar partial review and deleted historical references, but ordered membership/order acknowledgements need separate typed order checkpoints. Historical source reference parsing is still unimplemented; this remains a candidate awaiting independent review.

Decisions and current strategy

Preserve one typed core and validated command boundary. Retain current typed ports; R6 uses schema/source4 with explicit1/2/3 migration and no intermediate public4 shape. Freeze payload, defaults, inheritance, associations and identified interface allocations together. Preserve lexical includes/comments during migration.

Finish and independently verify R6, then semantic R3 reconciliation and direct scenario/process gestures. Complete lifecycle/recovery, hosted editing, guidance and fresh cross-disciplinary Windows/Linux acceptance. No subsystem checkpoint completes the first release. Current work is making measured implementation, review and runtime progress; no external blocker exists.

4.3 KiB Raw Blame History