Version 1 release plan

Delivery instruction

The user's October 7, 2026 instruction supersedes the open-ended delivery sequence: use the next goal continuation to wrap up Version 1 within two days, and prepare Version 2 as a separate goal afterward. The 48-hour delivery window started October 7, 2026 at 06:17:48 UTC. The deadline is October 9, 2026 at 06:17:48 UTC (08:17:48 Europe/Berlin). This deadline persists across continuations and must not restart. Keep the existing work and saves; do not restart the project.

Finish a coherent playable release. Prioritize bugs, incomplete player instructions and release verification over additional feature breadth. Remaining original-plan work moves explicitly into Version 2; it is not claimed complete. The original M0–M8 plan remains the full design reference.

Version 1 scope

• Found one persistent woodland, farming or coastal settlement with real starting stock, current charter rights and no repeat founding grant.
• Navigate the live city overlay, City management, Region and Hex; place a legal building, pay its inputs, complete its crew work and assign actual workers.
• Keep households supplied through the daily/offline loop using local food, storage, reserves and honest production blockers. Recover from a controlled shortage.
• Use the resource/supply graph and an actual material bottleneck. Manufacture goods and move finite cargo through reviewed physical trade, including the current mixed barter feature.
• Research and separately adopt working techniques across the six branches. Include the existing first eighteen-node release; advanced choices remain subject to their actual implemented limits.
• Recruit and equip a small force, pay its labor and food cost, protect a real route, and return survivors/equipment through the existing commands.
• Make one useful paid land improvement, survey and obtain rights to an outpost, send existing founders, and exchange real supplies with home.
• Preserve family/leader continuity, lawful authority and paid ongoing work through restart and the supported death/handover rules.
• Explain later and experimental features honestly. Existing advanced systems may remain accessible with their current restrictions; Version 1 does not promise the deferred Version 2 scope.

Two-day execution

Do not spend the deadline repeatedly re-certifying every historical branch when unchanged evidence already covers it. Re-test affected behavior, material shared invariants and the release journey. Run the complete automated suite if it fits the window; otherwise state the actual selected scope and any unrun checks plainly. Do not report an incomplete or failing check as passed.

Release acceptance checklist

• [x] Record the actual continuation start and the deadline 48 hours later.
• [x] Complete the current mixed-barter implementation, served journey, documentation and compatibility checks — City v263, 109 selected tests and 49 restored checkpoints; see the current implementation status.
• [x] Verify a fresh start, founding once, first useful building and staffing, current guidance and same-identity reload.
• [x] Verify the integrated village/production/patrol/land/outpost journey and normal offline food behavior with conserved people, goods and labor.
• [x] Verify the first eighteen technology choices and separate adoption gates; identify any real release blocker.
• [x] Verify competing claims/stock/workers, blocked/full/depleted production, physical shipment restart and save migration on the affected paths — 177/177 core cases plus complete affected-file runs of 28/28, 6/6, 9/9 and 35/35 after ten explicit test/helper corrections; 255 distinct selected cases across twenty-four files. The original broad run retains sixteen failures, each resolved by the complete current affected file. Historical perimeter predecessor copies retain their explicit normalization and controlled QA scope.
• [x] Run catalog validation, appropriate tests, syntax checks, wiki build/check and whitespace checks. Record exact scope and failures — see the release notes for the completed original broad run, sixteen verified failure resolutions and current-source selected scope.
• [x] Inspect the release controls at mobile and desktop widths; distinguish automated UI checks from human playtesting — fresh first-project checks at 320/390/640/1440 pixels, retained mixed-barter checks and inspected mobile previews; human usability remains uncertified.
• [x] Write docs/version-1-release-notes.md with launch steps, playable features, limitations and verification results.
• [x] Finalize the Version 2 plan with priorities, acceptance gates, dependencies and a ready-to-use new-goal objective — including the first thirty-day sustained-supply milestone. No Version 2 goal has started.

Version 1 deliverables are complete for this explicitly revised release scope. The wider original requirements remain deferred to Version 2. Do not silently extend the deadline to finish Version 2 features. The user's later October 7 instruction update git and live authorizes committing and pushing this release and publishing it through the existing Railway production service. Check the actual staged documentation coverage, deployment status, health and served release files. Keep disposable QA, local saved worlds and private attachments outside the commit.