# First release execution plan Updated 2026-09-11, Codex-9e8r6t `/root`. [PROJECT_GOAL.md](../PROJECT_GOAL.md) defines the outcome; [TASK_LEDGER.md](TASK_LEDGER.md) separates evidence from assumptions; [STATE.md](STATE.md) owns active leases and results. Resumed after the user's virtualization/reboot update. STATE.md supersedes the historical [RESTART_HANDOFF.md](RESTART_HANDOFF.md) for live status. Postboot focused3 ran25 passing tests and one failing overflow-fixture assertion; its test-only correction passed all26 focused4 tests. Strict Clippy, formatting and matching GUI5657 build also passed; fresh native acceptance continues. Nondeleting compression completed across282 generated binaries with identical hashes and11.78GB free; supported Ubuntu26.04 installation passed exit0. Actual root shell identifies Ubuntu26.04/WSL2. User328 replaces failed mirrored mode with VirtioProxy; the VPN is immutable. Both new guest startups timed out before execution, then the distinct WslService restart failed at OS access permissions. All60 apt archives and five Rust components are downloaded and hash-verified; guest signature verification/install and Linux Cargo remain pending. No compiler or WSL client lease is active. The user has now paused Linux builds/checking until they report WSL networking resolved; do not schedule more Linux setup, launches, diagnostics or checks before that notice (Gitea comment356). Lifeline/Chain history and Machine Create/Undo/postboot reopen passed on GUI52; Fresh GUI5657 cancellation/recovery, Lifeline direct creation/history and Machine minimum-size owner/Create/Undo/Redo/reopen now pass; full679 desktop tests pass. ## Immediate implementation and acceptance 1. Preserve and publish the completed native acceptance of GUI `5657BAB5…D3846CE` using the [v2 plan](release-contextual-source-native-v2-plan-20260911.md). All26 affected tests, strict all-target Clippy, formatting and matching build pass; the full679 immutable Windows test run also passed. Minimum-size child visibility, exact recovery/cancel and direct Lifeline Create/Undo/Redo now pass, along with Machine owner visibility/Create/Undo/Redo/reopen. Preserve independent first UUID carriers and serialize future compiler/source leases. Prepare an updated Windows prerelease only with honest per-binary source identity, package verification and clean packaged runtime checks. 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. Peer956 now reports focus regression5/5 and isolated numeric26/26 plus analysis28/28; their codec/lifecycle work remains isolated. Local integration and coherent union gates remain necessary. Do not replace peer efforts with a parallel local implementation. Comment338 separately reserves our bounded syntax-only outline seam for current-text navigation; its private query module and prepared tests remain uncompiled pending review. 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](history/2026-09-10-ledgers-before-second-consolidation/PLAN.md). They do not supersede current user scope or imply current-tree acceptance.