(pre-development) Stars! PBeM service on Kubernetes
0
fork

Configure Feed

Select the types of activity you want to include in your feed.

Start detailed implementation planning with requirement-mapped task tracks

rektide bc6d9d03 6ec7b7e5

+117 -1
+2 -1
doc/total-host.codex.md
··· 336 336 337 337 Initial artifact drafted for `PKG-01`: [`/doc/total-host.coverage-matrix.md`](/doc/total-host.coverage-matrix.md) 338 338 Initial artifact drafted for `PKG-02`: [`/doc/total-host.workstream-dependency-map.md`](/doc/total-host.workstream-dependency-map.md) 339 + Initial implementation planning artifact: [`/doc/total-host.implementation-plan.md`](/doc/total-host.implementation-plan.md) 339 340 340 341 ## Stage 5 Deliverables 341 342 ··· 378 379 379 380 - traceability implementation design (annotation format, report shape, CI policy) 380 381 - ATProto lexicon definition details and exact telemetry field mapping 381 - - detailed implementation plan, task breakdown, and execution order 382 + - implementation execution refinements after runtime gate decisions (`AGD-*`) 382 383 383 384 ## References 384 385
+115
doc/total-host.implementation-plan.md
··· 1 + # total-host: implementation plan and task map 2 + 3 + This document starts Stage 5 execution planning from requirements. 4 + 5 + It translates product requirements into workstreams, dependencies, and actionable tasks without locking crate/module structure. 6 + 7 + Primary references: 8 + 9 + - Requirements source: [`/doc/total-host.codex.md`](/doc/total-host.codex.md) 10 + - Coverage matrix (`PKG-01`): [`/doc/total-host.coverage-matrix.md`](/doc/total-host.coverage-matrix.md) 11 + - Workstream map (`PKG-02`): [`/doc/total-host.workstream-dependency-map.md`](/doc/total-host.workstream-dependency-map.md) 12 + - Runtime discovery boundary: [`/doc/agones.md`](/doc/agones.md) 13 + 14 + ## Planning Rules 15 + 16 + - Requirements-first: every task maps to requirement IDs. 17 + - Boundary-safe: no task may violate Stage 3 domain boundaries. 18 + - Evidence-first: each completed task must produce verification evidence. 19 + - Deferral-respecting: deferred policy space (`TPS-IDEA-*`, `OQ-TP-*`) is excluded from MVP execution. 20 + 21 + ## Execution Tracks 22 + 23 + | Track | Purpose | Workstreams | Primary Output | 24 + |---|---|---|---| 25 + | `TRK-00` | Delivery foundation and gates | `WS-08`, `WS-07` | traceability + observability baseline evidence | 26 + | `TRK-01` | Intake, validation, artifact correctness | `WS-05`, `WS-02`, `WS-01` | accepted/rejected submission pipeline | 27 + | `TRK-02` | Lifecycle and generation correctness | `WS-03`, `WS-04` | deterministic turn lock/generate/fail behaviors | 28 + | `TRK-03` | Distribution and operator operations | `WS-06`, `WS-07` | player-isolated delivery + operator diagnostics | 29 + | `TRK-04` | Runtime integration closure | `WS-09` | Agones gate decisions (`AGD-*`) and mapping | 30 + | `TRK-05` | Release gate verification | `WS-08` + all | `RLB-*` go/no-go package | 31 + 32 + ## Detailed Task Breakdown 33 + 34 + ### Track `TRK-00` (Foundation) 35 + 36 + | Task ID | Task | Maps To | Depends On | Exit Evidence | 37 + |---|---|---|---|---| 38 + | `IMP-001` | Define requirement tag format for code/test artifacts | `TRC-01`, `TRC-02`, `TRC-03`, `HND-201` | - | documented tag contract + sample tagged artifacts | 39 + | `IMP-002` | Define machine-readable trace report schema and generation flow | `TRC-04`, `HND-104` | `IMP-001` | report schema + generated sample report | 40 + | `IMP-003` | Define baseline lifecycle OTel span taxonomy | `OBS-01`, `OBS-02`, `OBS-05`, `HND-202` | - | span naming table + required correlation attributes | 41 + | `IMP-004` | Define release gate checklist linking `RLB-*`, `AC-*`, `RSK-*` | `HND-301`, `HND-103` | `IMP-002`, `IMP-003` | release gate checklist artifact | 42 + 43 + ### Track `TRK-01` (Intake, Validation, Artifacts) 44 + 45 + | Task ID | Task | Maps To | Depends On | Exit Evidence | 46 + |---|---|---|---|---| 47 + | `IMP-101` | Implement artifact identity model and state transitions | `ART-01`, `ART-02`, `ART-03`, `INV-02`, `CAP-101` | `IMP-001` | artifact identity validation checks | 48 + | `IMP-102` | Implement structural and identity validation outcomes with stable reason codes | `VAL-01`..`VAL-05`, `CAP-102`, `IFC-002` | `IMP-101` | reject matrix with reason-code assertions | 49 + | `IMP-103` | Implement player-scoped submission and replacement semantics | `LIF-03`, `OWN-02`, `OWN-03`, `CAP-001`, `IFC-001` | `IMP-101`, `IMP-102` | submission replacement behavior checks | 50 + | `IMP-104` | Implement deterministic selection of effective submission at lock boundary | `OWN-04`, `INV-03`, `CAP-002`, `CNS-004` | `IMP-103` | deterministic retry/lock verification | 51 + 52 + ### Track `TRK-02` (Lifecycle and Generation) 53 + 54 + | Task ID | Task | Maps To | Depends On | Exit Evidence | 55 + |---|---|---|---|---| 56 + | `IMP-201` | Implement lifecycle state transition authority and transition guards | `LIF-01`, `LIF-02`, `LIF-04`, `ARC-002`, `CNS-001` | `IMP-104` | transition guard verification matrix | 57 + | `IMP-202` | Implement lock/start/finalize/fail generation contracts | `IFC-003`, `LIF-05`, `LIF-06`, `LIF-07` | `IMP-201` | generation contract tests (success/fail) | 58 + | `IMP-203` | Implement atomic success binding of authoritative state and outputs | `CNS-002`, `INV-01`, `CAP-003` | `IMP-202` | monotonic turn + single-advance checks | 59 + | `IMP-204` | Implement non-destructive failure path with recoverable state | `CNS-003`, `INV-05`, `CAP-004` | `IMP-202` | failure-injection preservation checks | 60 + | `IMP-205` | Implement pause/delay/unpause control flow | `LIF-08`, `CAP-005` | `IMP-201` | pause/resume advancement checks | 61 + 62 + ### Track `TRK-03` (Distribution and Operations) 63 + 64 + | Task ID | Task | Maps To | Depends On | Exit Evidence | 65 + |---|---|---|---|---| 66 + | `IMP-301` | Implement per-player output distribution isolation | `DST-01`, `DST-02`, `SEC-001`, `SEC-002`, `CAP-201` | `IMP-203` | cross-player access denial checks | 67 + | `IMP-302` | Implement delivery state machine (`pending`/`delivered`/`failed`) | `DST-03`, `CAP-202`, `IFC-005` | `IMP-301` | delivery transition checks | 68 + | `IMP-303` | Implement operator diagnostics surface for rejects/failures | `NFR-02`, `CAP-302`, `IFC-006` | `IMP-102`, `IMP-204`, `IMP-302` | diagnostics visibility checks | 69 + | `IMP-304` | Implement auditable lifecycle event stream | `NFR-01`, `CAP-301`, `CNS-005` | `IMP-201`, `IMP-202`, `IMP-302` | lifecycle event coverage report | 70 + 71 + ### Track `TRK-04` (Runtime Integration Closure) 72 + 73 + | Task ID | Task | Maps To | Depends On | Exit Evidence | 74 + |---|---|---|---|---| 75 + | `IMP-401` | Resolve runtime unit model decision (`AGD-01`) | `HND-001`, `HND-003` | - | decision record with tradeoff table | 76 + | `IMP-402` | Resolve control primitive and allocation interface (`AGD-02`, `AGD-03`) | `HND-001`, `HND-003` | `IMP-401` | runtime API boundary decision record | 77 + | `IMP-403` | Define lifecycle mapping and failure semantics (`AGD-05`, `AGD-06`) | `LIF-01`..`LIF-08`, `HND-301` | `IMP-401`, `IMP-402` | lifecycle-to-runtime mapping table | 78 + | `IMP-404` | Define operator/control-plane ownership and security model (`AGD-07`) | `SEC-003`, `HND-302`, `OUT-04` | `IMP-401`, `IMP-402` | operator responsibility + privilege model | 79 + 80 + ### Track `TRK-05` (Release Gate Verification) 81 + 82 + | Task ID | Task | Maps To | Depends On | Exit Evidence | 83 + |---|---|---|---|---| 84 + | `IMP-501` | Run full acceptance matrix against implemented MVP | `AC-001`..`AC-403` | `IMP-101`..`IMP-304` | acceptance run report | 85 + | `IMP-502` | Validate risk controls against release evidence | `RSK-001`..`RSK-005` | `IMP-501` | risk control closure report | 86 + | `IMP-503` | Validate requirement trace report completeness | `TRC-01`..`TRC-05` | `IMP-501` | machine-readable trace report | 87 + | `IMP-504` | Produce first usable release gate packet | `RLB-01`..`RLB-05` | `IMP-501`, `IMP-502`, `IMP-503` | release go/no-go packet | 88 + 89 + ## Immediate Start Queue 90 + 91 + These tasks can start now with minimal unresolved dependencies: 92 + 93 + - `IMP-001`, `IMP-002`, `IMP-003`, `IMP-101`, `IMP-102`, `IMP-103`, `IMP-401` 94 + 95 + ## Blocked Until Runtime Gate Decisions 96 + 97 + These should not be finalized until `AGD-*` decisions close: 98 + 99 + - `IMP-403`, `IMP-404`, runtime-coupled portions of `IMP-202`, `IMP-203`, `IMP-204` 100 + 101 + ## Definition of Planning Readiness 102 + 103 + Planning is considered ready for execution when: 104 + 105 + - all tasks have requirement mappings and dependency clarity 106 + - immediate start queue has owners and verification expectations 107 + - runtime-gated tasks have explicit blockers (`AGD-*`) tracked 108 + - release gate packet structure (`IMP-504`) is agreed 109 + 110 + ## References 111 + 112 + - Requirements source: [`/doc/total-host.codex.md`](/doc/total-host.codex.md) 113 + - Workstream map (`PKG-02`): [`/doc/total-host.workstream-dependency-map.md`](/doc/total-host.workstream-dependency-map.md) 114 + - Coverage matrix (`PKG-01`): [`/doc/total-host.coverage-matrix.md`](/doc/total-host.coverage-matrix.md) 115 + - Runtime boundary discovery: [`/doc/agones.md`](/doc/agones.md)