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.

Paused for the user's reboot. RESTART_HANDOFF.md takes precedence for immediate resume: validate WSL/Ubuntu, frozen input provenance, then a fresh focused3 gate. The corrected layout build was interrupted before tests; no new GUI exists. Lifeline/Chain exact history passed on GUI52DE82; Machine Create/Undo passed, with Redo/reopen still pending.

Immediate implementation and acceptance

1. Natively verify frozen contextual GUI 52DE82E4…, now launched in the isolated contextual-source stage (now closed for reboot). The 13-file source slice passed 23 focused tests, 3 guide tests, strict all-target Clippy, matching build and formatting. Full 675/675 covers the preceding snapshot only; no full 676 result exists. Preserve immutable artifacts and serialize future compiler/source leases.
2. Exercise the implemented source subform for Lifeline, process/chain Work and machine owner, plus semantic first-action prompts. Verify parent-draft retention, explicit prerequisite and consumer adoption, exact source/history, cancellation and recovery against the independent staged-source oracle. Final source guards and guide corrections are complete and reviewed; native acceptance remains; source/evidence are integrated in df6f595. Named creation, nine-file reopen and SA pending-draft recovery already have their separate native passes.
3. Complete local SA B2 and 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 candidate 3 at wide size. OA B2 Action, State, bound Reuse and Fragment now pass complete model/two-source Create, one Undo, one Redo and final OA reopen/Save with exact original identities. Preserve the existing B3 layer/size scope; do not infer SA B2 or broader camera/focus coverage from these passes.
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.

Peer comment 231 ratifies schema 8/local-definition core steps in an isolated worktree. Coordinate those actual shared types and ownership before local integration; the current local core remains descriptive. Source grammar, evaluation, server/CLI/UI representation and acceptance are separate unfinished steps. Peer chooser comment 224's corrected mounted tests remain prepared, not executed. Do not replace either peer effort with a parallel local design.

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. The published CLI now covers checked stabilization and typed alias rename with exact source-preserving preview/write. Next evaluate cross-file definitions/references and engineering task completion 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.
• Review and test the peer-ratified pure core and its explicit migration/admission boundaries before local integration. Retain independent falsifiers and current typed Project, Command and source-writer guarantees across representations.
• 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

• GUI/server release 1, v0.2.0-preview.authoring.20260911, and standalone CLI release 2, cli-v0.2.0-preview.authoring.20260911, are published and read back. Their exact notices, archive, runtime and uploaded-asset evidence is preserved. CLI packaging is integrated at 27df4a3; instruction sync 07eb3cd and contextual source checkpoint df6f595 and its raw evidence are integrated. CLI publication d95b1ab and OA native checkpoint c4bad4b are also integrated; then publish later coherent milestones under the assigned owner. Preserve each artifact's source/profile/native scope and complete final-release gates separately.
• 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.
• Follow the external owner's supported Linux guest route and run current GUI/server workflows when viable. This local host has no usable Linux runtime; supported WSL2 failed. Preserve failed attempts rather than repeating rejected workarounds, and continue independent Windows/semantic work.
• After the user reboot, check local Ubuntu registration and launch first. A version2 default alone is not an installed/running Linux environment.
• 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.