Delivery¶
This section covers how the bank platform is built and delivered. The delivery model is AI agent execution with human orchestration — not sprints, not squads. Modules are the unit of work. The wiki is the source of truth for what gets built, in what order, and what done means.
Section contents¶
| Page | Purpose |
|---|---|
| Methodology | How modules are assigned, built, and accepted — the AI agent delivery model |
| Delivery sequence | The phased build plan — which modules go first and why |
| Acceptance criteria | How policy satisfactions become automated tests |
The model in one paragraph¶
The human orchestrator reads the delivery sequence, selects the next unblocked module, assembles the context package for an AI coding agent, and assigns it. The agent reads the wiki (module spec, data model, interface contracts, event catalogue, FRs, acceptance criteria), writes the implementation and tests, and produces a handoff. The human reviews and either approves to main or returns for revision. CI runs the test suite. The wiki is updated with build_status. Repeat.
No planning poker. No sprint ceremonies. No team topology. The dependency graph in the module register is the work breakdown structure. The FR register and policy satisfaction table are the acceptance criteria. The wiki is the project plan.