ARCADIA-Studio/harness/PLAN.md

First release execution plan

Updated 2026-09-11, Codex-9e8r6t /root. PROJECT_GOAL.md defines the outcome; TASK_LEDGER.md separates evidence from assumptions; STATE.md owns active leases and results.

Immediate implementation and acceptance

1. Preserve the verified creation integration and matching GUI stage, committed as 4bb4aaf and transferred with independent anonymous readback/hash verification. Final immutable desktop653/653 passed after creation ancestry/guide changes, alongside focused creation21/guide3. StrictClippy/fmt pass after a behavior-equivalent history rewrite; affected history63 and GUI build also pass. Preserve exact artifact scopes and serialize future Cargo/source leases.
2. Named process/scenario/machine creation, exact Undo/Redo and nine-file reopen have passed at actual minimum size. Wide/minimum cancellation passed; SA draft crash recovery is active. Address observed blank canvases and prerequisite creation detours through the staged-source plan: source subform retains the parent draft and final adoption atomically creates prerequisite and consumer. First slice covers Lifeline, process Work and machine owner, with semantic first-action prompts. Independent review precedes final integration/native QA.
3. Operate the rebuilt app at minimum/normal sizes. Complete the saved basic supplementary move/camera/invalid-draft and minimum-size story; the main basic model and explicit transition passed full Project+SourceBundle, Undo/Redo and reopen on candidate3 at wide size. Exercise new scenario workspace, creation and caller return with real inputs and saved model evidence, then correct and reverify concrete defects.
4. Integrate standalone B4 scenario lifetimes and the external independent scenario contract without overwriting local layout work. Resolve source-derived lifetime versus insertion bounds, activation-after-Delete and lane-map issues. Close remaining contextual operand, missing-source and state-naming workflow gaps identified by the current behavior audit and native study.

Foundational semantic additions

The updated objective explicitly requires functional constraints/calculations, quantities/units and maintained model libraries. Current metadata/includes are insufficient. This work runs independently of useful behavior improvements.

The newest objective also requires complete uncluttered text-only workflows. Combine the local three-task usability audit with the other host's language/ identity/API design. Two concise current-grammar recipes now pass their bounded REST identity/source/persistence experiment. Next evaluate cross-file definitions/references, safe alias rename and identity-preserving patch preview on repeated-name modular models. Do not equate shorter examples or parser throughput with task usability, and do not silently change omissions.

• Compare real candidate semantics before large changes. Use primary Capella, SysML and quantity/unit evidence, with explicit compatibility limits.
• Falsify candidates through mass/power/latency budgets, mixed/affine units, unknown/error/false results, dependency cycles, reference identity and bounded evaluation. Separate descriptive existing text from executable declarations.
• Probe libraries through two projects/two instances, pinned offline content, exports/dependency closure, bindings, distinct origin/local identities, updates with local divergence, detachment and exact transactional rollback.
• Run a small pure-core experiment for the selected candidate. Independent criticism must precede broad schema/source/API migration. Retain current typed Project, Command and source-writer boundaries unless evidence requires change.
• Implement the ratified contracts across validation, visitors, deletion, identity, OA/SA transitions, source/reST, schema/REST, ergonomic graphical authoring and help. Add real examples and independent parity acceptance.

Integration and release

• Publish coherent commits and verified bundle transfers through Gitea; keep concise host-scoped handoffs and Wiki. Do not overwrite another host's branch.
• Refresh relevant source/schema/example/doc gates and run current core, desktop/server and real REST transport/restart/ETag/draft-conflict workflows.
• Build matching optimized desktop/server packages. Regenerate complete notices for actual inputs and verify archive contents, hashes and clean-runtime launch. Historical ELF fixtures and build preparation do not replace execution.
• Obtain a viable Linux environment and run current GUI/server workflows there. Supported WSL2 failed; no repeated rejected workaround. Continue independent work while the environment question is pending.
• Conduct fresh independent requirements, semantic, usability, architecture, correctness, runtime and documentation reviews. Resolve all material findings, reverify affected behavior and only then declare release completion.

Historical milestones and evidence remain intact in the dated plan archive. They do not supersede current user scope or imply current-tree acceptance.