ARCADIA-Studio/harness/PLAN.md

First release execution plan

Updated 2026-09-10. PROJECT_GOAL.md is the authoritative current objective. STATE.md records exact execution/evidence and leases; TASK_LEDGER.md separates facts, assumptions and decisions. The complete previous plan is preserved byte-for-byte. Its earlier goal paths, active-process claims and Escape pauses are historical.

Outcome and working principles

Deliver usable, complete OA/SA engineering workflows on Windows and Linux, with one precise reST contract and equivalent graphical, textual and REST editing. Constraints/calculations, quantities/units and reusable libraries are explicit requirements alongside behavior/state modeling, traceability and navigable help. Later Arcadia layers remain future scope. Compilation, metadata fields and polished screens alone do not satisfy this outcome.

Retain the shared typed core, stable identity, semantic ownership/allocation distinct from geometry, validated atomic commands and exact source/history. Persistent extensions need coherent references/deletion, transition, source/migration, API/schema and reachable graphical authoring. Define observable acceptance before broad downstream changes. Do not silently promote a design proposal to a decision.

Capability milestones

Milestone	Work and acceptance	Dependency/current limit
1. Reliable direct authoring	Finish cold compilation and meaningful regressions; integrate compact named architecture/behavior creation and scenario workspace. Exercise actual minimum/wide native creation, allocation, editing, rejection, cancellation and history without implicit draft application or placement drift.	Root owns this host's Cargo/native lease. External host owns scenario layout/B3/local creation/palette; integrate coherent checkpoints first. No current local Rust/native Studio pass.
2. Coherent process/scenario work	Interactive ordered/explicit process editing; clicked root/nested scenario insertion; exact reuse bindings and caller return; measured canvas/zoom/scroll; visible scoped Create/Delete lifetimes. Validate model/source/identity and no unintended edit during navigation, including stale/deleted/retargeted references and recovery.	B1/B2/B3 adapters are source-integrated; B3 has a known externally owned correction. B4 is cfg(test) projection only, awaiting Scene integration. The independent oracle compiled/self-checked and its generated baseline passed; use it for native checkpoints.
3. Precise engineering analysis	Compare owned properties, analysis contexts and existing-data/external alternatives; settle quantity kind/unit/value, numerical policy, calculation/binding and Boolean/error/unknown semantics through falsifying examples. Implement mixed-unit budgets and reusable calculation/constraint definitions with full UI/source/REST parity and exact history/recovery.	New requirement audit confirms absence. Maximum-reasoning proposal tracks precede root synthesis and independent criticism; no semantic contract is ratified yet. Strings are not evaluation.
4. Maintained reusable libraries	Compare package/definition/instance alternatives. Establish pinned identity/version/dependency closure, local edits, import bindings, detach and explicit three-way updates. Demonstrate two projects, two independent instances, offline reopen, conflicting updates and stable unaffected identities.	Coordinate with milestone 3 definition references and migration. Same-project includes/reuse do not satisfy maintained cross-project libraries. No package contract implemented yet.
5. Understandable complete engineering tasks	Close teaching, OA↔SA transition/reconciliation, typed state/data/interface, artifact, saved-view and hosted workflows. Replace concrete long homogeneous selectors with contextual/searchable bounded choices; verify representative large models, keyboard access, minimum sizes and failure/recovery. Keep offline guide and exact worked examples aligned.	Existing implementations and historical evidence are a coverage starting point. Reassess against current goal instead of reviving stale absence claims or carrying old scope exclusions forward.
6. Release confidence and delivery	Fresh current Windows/Linux suites, strict Clippy/format, normative reST/OpenAPI/migration/examples; actual GUI/service transport, optimized builds, runtime/notices/archive/provenance/checksums and clean-environment launch. Fresh independent requirements/domain/parity/architecture/UX/runtime review; resolve material findings, then final handoff.	Integrates all preceding capabilities. Linux runtime remains open; use an approved supported environment, preserving historical failed/denied experiments. Historical previews are not final distributions.

Milestones are capability gates, not a rigid serial schedule. Root can continue build/native acceptance while independent foundational investigations compare alternatives. Libraries and analysis share definition-resolution assumptions and must converge coherently before broad model/schema edits. User workflows and cross-representation evaluators guide implementation boundaries.

Immediate execution sequence

1. Observe the existing one-job desktop build to completion; preserve failures and fix causes. Run focused corrected cases, then proportionate full gates and GUI.
2. Exchange exact verified commits with the separate host, preserving its workspace ownership. Do not merge the bundle-transfer branch or assume remote publication.
3. Use the self-checked scenario oracle, follow its native procedure, and compare exact whole snapshots for Undo/Redo/reopen at minimum/wide sizes.
4. Synthesize the requirement delta and independent semantic proposals; subject materially different candidates to concrete numerical, identity, migration and engineering-workflow falsifiers.
5. Update current ledgers and durable decisions when evidence changes the plan. Reassess unresolved assumptions before expanding downstream implementation.

Coordination and evidence rules

Use Gitea issue #1 and Wiki for current ownership/handoffs; read before resuming. Codex-956atf and Codex-9e8r6t are distinct hosts. Cargo/native leases are host-local; shared source ownership is coordinated. Root owns local integration and final responsibility. Both hosts currently lack direct push authentication; authenticated MCP and anonymous fetch support verified bundle exchange without shared-ref overwrite.

Record exact source/binary, command exit, test scope and native model/source oracle. Do not add focused reruns to full-suite totals or transfer old binary acceptance. Older denied Linux workaround instructions remain applicable to that action; do not bypass them. Older stopped native sessions do not prevent currently authorized native work. The archived plan and archived progress preserve all previous strategy and scoped evidence; archive report links resolve from their original harness/ directory.