Dune/docs/CURRENT_STATUS.md

Current development status

Updated 13 September 2026. This is the short navigation dashboard; detailed evidence remains in the linked records. The complete twelve-faction goal is unfinished. Basic is playable; Advanced and unfinished expansion starts remain gated. No completion or publication gate is opened by this document.

Evidence and source of truth

• First Discovery prototype: genuine base-faction Basic/Advanced setup, seven Spice Cards, eight tokens, Great Maker, Collection inspection/rewards and revealed nested locations are connected. Focused checks pass; final broad checkpoint evidence is pending. Free entry, special location benefits and Ornithopter spending remain missing.

• Ix prototype checkpoint 5a76ae0: types, lint, 4,211 offline tests, build and 40 HTTP tests passed. Genuine Basic/Advanced setup and two seeded complete simulations were exercised; a short browser game finished with private hand restoration. All 64 opening saved rooms were preserved; 31 QA rooms were added. This is bounded prototype evidence, not complete Ix compliance.

• Rules implementation checklist: RULE_TOPICS, topic implementation-checklist, and each feature's implementation, controls, AI, documentation and verification entries. Coverage is per stated boundary, not an implicit whole-game certificate.

• Latest verified gameplay checkpoint: Truthtrance hand inventory, 13 September 2026 (7454456): types, lint, 4,200 offline tests, production build and 40 HTTP tests passed, with a phone/browser refresh journey and preserved saved games. These are recorded results, not checks rerun for this dashboard.

• Latest verification checkpoint 4a0b1ee: genuine Advanced full-plan interaction tests; types, lint and 4,205 offline tests passed. Private inspection restored after restart, with desktop/phone checks and all 64 saved games unchanged. No runtime change; prior build/HTTP evidence applies.

• Development guide defines focused verification; rule decisions locates settled contracts and pending interpretations. Read the newest checkpoint and relevant feature document before consulting older log entries.

The user authorized a one-time local reset on 13 September: the 3,644 historical rooms were archived privately and cleared. Fresh checkpoint and preservation policy now apply to new games; historical room IDs are no longer active local fixtures.

The first three efficiency milestones are pushed: tooling 6e26ba5, typed Advanced shipment commitments 32791ed, and hand inventory facts 7454456. See pilot measurements.

The current Atreides full-plan audit verifies Truthtrance/Voice/Prescience/Ghola interactions from genuine Advanced setup, replacing the old Basic-then-flip test fixture. These existing paths pass without a runtime change. Exact special-offer timing and target-first ordering remain source interpretations; they are not settled by test results.

The development server is reused until a change or observed condition warrants a restart. The user removed hourly restarts; preserve saved games and verify restoration after necessary restarts. No recurring automation is installed.

Remaining readiness

Area	Established evidence	Remaining gate
Basic core	Playable loop; shared setup, Fremen movement cancellation, structured Truthtrance facts and bounded Basic/no-Guild Advanced reserve-shipment promises.	Ordinary Guild rate/transport cancellation; wider truthful questions/action commitments; integrated rules and human/AI acceptance.
Six-faction Advanced	Genuine offline setup across 456 configurations; four-profile full-game simulations and JSON continuations.	Base gaps plus provisional special-Karama outcomes, remaining timing audits and authentic multiplayer/browser acceptance. Public starts remain disabled.
Twelve factions and optional modules	Many bounded faction, card, Homeworld and Nexus slices have controls, bots and recovery evidence; the first Discovery actions now have a connected prototype.	Every unfinished effect and interaction, occupation entitlement, remaining Discovery effects and complete combined games. Inventory or fixture coverage does not enable a module.
AI difficulty	Four profiles consume private legal views; recorded Basic and Advanced studies complete.	Demonstrate a consistent Medium → Hard → Brutal strength ordering, improve strategic gaps, and repeat targeted studies after relevant policy/rule changes.
Multiplayer	Versioned writes, saved seats, owner recovery kits, uncertain-request retry and voluntary own-seat AI control.	Intentional transfer, unprepared abandoned-seat recovery, unattended continuation and remaining network-failure acceptance. Preserve privacy and existing games.
Player experience	Internal component inspectors and many desktop/phone feature journeys verified.	Complete end-to-end games, accessible controls, responsive layout, clear rules/errors and recovery across all supported combinations.

The base/Advanced audit includes historical missing-feature rows. Its follow-ups supersede the Fremen cancellation and BG setup findings; genuine setup and the Advanced study supersede the old Basic-then-flip testing concern. They do not settle the remaining rules.

Likewise, the Truthtrance readiness audit predates spice facts, card-count facts and Basic shipment promises. Current TruthFact already includes these facts; do not rebuild them. Typed preparation and BG conversion now support the active reserve-shipment scope in base Advanced without Guild or optional modules. Broader facts, earlier-phase promises, remaining Advanced/expansion commitment scope and freeform interpretation remain incomplete.

Next milestone: rapid functional coverage

The first connected batch is the Ixians & Tleilaxu prototype: genuine setup, both expansion factions, full Ix deck and Sandtrout, shared human/AI controls and saved continuation. The checklist now distinguishes its Prototyped development stage from Partial rules coverage. The next connected action is the CHOAM Nexus Collection trade, with private controls, all four AI profiles and a saved payment/discard continuation. Its after-victory inspection remains missing. The first Discovery batch now connects the sourced components to Great Maker, destructive Discovery blows, private inspection/reveal, stash rewards, carried Ornithopter custody and five revealed nested locations. Only Jacurutu counts toward stronghold victory. Next dependencies are free entry at the next turn, the five special location benefits, and spending Ornithopter on a later move; complete variant acceptance and normal public starts remain gated.

The user changed the development order on 13 September: get working prototypes of all remaining functions into the game, then use integration and play to find issues and refine them. Complete core certification no longer precedes independent expansion prototyping. Final rules compliance and release requirements still apply.

1. Reconcile the existing checklist with current helpers, controls, AI and saved-state paths. Mark remaining work as missing, prototyped, integrated, verified or polished; retain explicit blockers and reuse completed features.
2. Implement the next connected batch across Basic, Advanced, factions or modules according to dependencies. Include real actions, usable controls, a legal AI path and saved continuation. Keep fast checks for crashes, deadlocks, legality, custody, privacy and save integrity; avoid exhaustive refinement of each small feature before broad coverage exists.
3. Continue independent functions while material rulings are pending. Ordinary Guild repricing/settlement and special Karama interpretations remain unresolved; do not invent their outcomes to fill the inventory.
4. Integrate prototypes and play complete games to discover issues, then deepen combination coverage, multiplayer recovery, AI calibration and visual polish. Required checkpoint checks, reviewed Git pushes, selective subagents and the 80%-used weekly stop remain in force. Keep unfinished modes and publication gated until acceptance.

Consult AI calibration, multiplayer audit, autopilot, component inventory and visual playtest for their measured scope and follow-ups. Use current code and later checkpoints to interpret historical results. Publication still requires the completion and integrated verification gates in README.