WS5 · Platform Engineering & Data.
Lead: AI-augmented workforce · Provider: CoSai · Current state: Absorbed by design
1 · Current state & lifecycle
2 · Transition history
Every state transition this workstream has made. Each row carries the trigger event that caused the transition — the single sentence that justifies the state change.
| Date | Transitioned to | Trigger |
|---|---|---|
| 1 March 2026 | Absorbed by design | Workstream architecturally absorbed into WS2 at PMO design stage · the 73% Year-1 burn saving from $1.87M (human-only) to $500k (AI-blended) |
3 · PMO commentary
WS5 is the workstream that does not progress along the four-state ladder, because it is not a separable line of work. The original Vol 4 Ch 12 design had it as a parallel platform-engineering team. The economics did not support that — a separate engineering team modelled at $1.87M Year-1 burn. CoSai's AI-augmented delivery model collapses WS5 into WS2 and reduces that cost to $500k Year-1 (a 73% saving, documented at /investors/memorandum §7). The workstream remains named here for taxonomic completeness, but it is structurally Absorbed and is reported as such on every PMO surface.
4 · Phase 1 / Phase 2 deliverables
No separate deliverable. All platform-engineering work delivered inside WS2.
No separate deliverable. Continues inside WS2.
5 · Phase 1 milestones
No Phase 1 milestones — this workstream is Absorbed by design and does not progress along the build-out ladder in Phase 1.
6 · KPI architecture
| KPI category | N/A (rolled into WS2 financial KPI) |
|---|---|
| Examples | Inherits WS2 KPIs · no separate measurement |
| Volume / Chapter source | Vol 1 Ch 10.3 (Future-state PMO economics) + Vol 2 Ch 1-12 (Platform spec, delivered inside WS2) |
7 · Cross-workstream interfaces
How this workstream supplies and consumes from the other six. Reading these interfaces is how you read the operating model end-to-end.
| Partner | Supplies to partner | Consumes from partner |
|---|---|---|
| WS2 | AI-augmented engineering capacity · all platform-engineering work delivered inside WS2 retainer | — |
8 · Physical artefacts in the repo
Every artefact that exists today as evidence this workstream is at the claimed maturity. 3 routes.
| Route | Description |
|---|---|
| /investors/memorandum | §7 AI-economics · the structural argument for absorbing WS5 into WS2 |
| /architecture | Platform-engineering decisions live inside WS2 architecture document |
| /blueprint | PMO Stage-Gate model · WS5 work is gated through WS2 sprints |
9 · Bottom-up evidence-based status reports
No bottom-up status reports have yet been compiled for WS5. The PMO authors these approximately 5 working days ahead of each Steerco — see the WS2 example at /engagement/pmo/ws-status/WS2/2 for the format Carla and the workstream leads use.