Private reference
Delivery roadmap
Stages and dependencies derived from the current delivery map.
Sources: PROJECT_CAPABILITY_REGISTER.md · Last refreshed:
Stage forecast
| Stage | Status | Delivered basis | Estimated remaining | Next outcome |
|---|---|---|---|---|
| Stage 1 | Planning open | 3 planning outputs delivered | 2–3 planning blocks | Settle pilot mechanics/interfaces and the finite evaluation envelope. |
| Stage 2 | Active; Batch 4 planned | 8 independently accepted bounded blocks | 8–13 build/evidence blocks | Build/review loadout Block 9; present process review before handoff; WI14 open. |
| Stage 3 | On hold | Prior bounded spatial/knowledge and first-slice evidence retained | Not yet estimated | Estimate after selected mechanics and shared-path readiness. |
| Stage 4 | Open | Retained setup/context/recovery evidence | Not yet estimated | Estimate after the pilot/evaluation envelope and domain interfaces are selected. |
| Stage 5 | Open | New-pilot publication/play remains unproved | Not yet estimated | Estimate after setup and operational arrangements. |
| Stage 6 | Open | No stage closure claimed | Not yet estimated | Assemble whole-effort evidence, independent review, and any identified repair work. |
Delivery route
| ID | Work | Status | Next action |
|---|---|---|---|
| FND | Retained storage, setup, context and connected first slice | Accepted (bounded) | Reuse proven paths; preserve broader capability limits |
| RE01 | Inventory retained components and prepare rule examples | Done (bounded preparation) | Hand off retained owner/case inventory and open decisions to RE02 |
| VIEW | Generate overview, current work and evidence views | Done (development aid) | Refresh and review the local page after any register change affecting current direction, forecast, delivery status/evidence or capability status/evidence |
| RE02 | Settle executable rule format and shared execution contract | Done (bounded design) | Implement the settled contract in RE03; all runtime gates remain open |
| RE03 | Prove healing through retained shared execution and repair boundaries | In progress / Blocks 1–8 accepted; B9 planned | Implement B9-01–08 loadout blueprint; final Batch 4 process review before successor/archival |
| RE04 | Prove a second definition reuses the same path | Not started | Use a reviewed isolated resource-restoration variant; identify any new semantics |
| RE05 | Independent shared-path review and reuse disposition | Not started | Review actual implementation, independent cases and all retained affected gates |
| PLAY | Remaining checks, encounters, NPC activities and rewards | On hold | Reconcile all original prerequisites including WI14 before resuming dependent work |
| LIVE | Actual GM interpretation and Discord proof | Later / gates retained | Carry C05/C19/C20/C22-C31 integration and operational gates; local tests are insufficient |