Roadmap & milestones

Nine gates, from an empty repo to three markets live

Each milestone has a demonstrable exit criterion \u2014 not a date. M0 and M1 are foundation; M5 is the first real tenant; M8 is all three markets live.

Delivery phases

Phase by phase

Sequential where the dependency graph forces it; parallel everywhere else. Full detail \u2014 squads, streams and exit criteria \u2014 is in Document 29.

PhaseFocusDurationDetailGate

Open Document 29 \u2014 full plan with squads and risks \u2197

Sprint-level timeline across all squads
Figure \u2014 parallel tracks and milestones across roughly 33 sprints (Document 29)
Sprint timeline

Six squads, six tracks, nine gates

Pakistan go-live (M5) lands around sprint 21 \u2014 roughly ten months at a two-week cadence. The Platform Adapters and Identity tracks stay close to continuously busy; the JVM track has deliberate gaps that absorb critical-path pressure.

Open Document 29 \u2197
Ledger service milestone sequence
Figure \u2014 a component-level milestone plan, derived from the programme plan
Component-level example

The same discipline, one service deep

The Ledger \u2014 on the critical path \u2014 gets its own six-milestone sequence between programme gates M1 and M2: money & domain core with no database at all, then persistence, holds, balances, and finally consumer-readiness.

  • L2 (posting & append-only) is flagged as the milestone to protect \u2014 cheap to build correctly now, expensive to retrofit later.
Open the Ledger milestone plan \u2197