Dependency map

What depends on what, and why

All 24 services and adapters, both applications, and the external providers they bind to. Hover or click any node to trace its connections and open its documents.

Applications Services Adapters New build External / provider
Layered top to bottom: applications call services and adapters; services and adapters depend on each other and on external providers. Hover isolates a node's direct connections; click opens its documents.
Critical path diagram
Figure \u2014 the critical path versus everything that runs beside it (Document 29)
Why this matters for scheduling

One chain decides the go-live date

Sprint 0 \u2192 Control Plane \u2192 Ledger \u2192 Pricing + FX \u2192 Payments + Payout rail \u2192 go-live. Everything else in the graph above has slack \u2014 it's necessary, but a delay there doesn't move the date the way a delay on this chain does.

  • External certification (NADRA, Raast, SBP) is tracked separately because it can dominate the date regardless of engineering progress.
  • E-Signature (26) must be built before Credit Bureau (24) \u2014 a legal ordering, not an architectural preference.
Open Document 29 \u2197