Skip to main content
Proposed sequence. No code implementation or production release is authorised by this review.

​
Build organisation

Each execution packet includes a bounded module/product slice, actors, terms, source contracts, diagrams, sample data, expected book entries, failure states and acceptance IDs. Deliver one complete economic lifecycle rather than many screens that only save requests. The engineering stack and three web app separation can reuse current project patterns after review. ATM/device and processor boundaries may require separately deployed components. No arbitrary microservice split, scheduler, connector or cloud vendor is chosen by this plan.

​
Tests before user handoff

Run relevant unit/calculation, database/transaction and contract tests; then browser/mobile-client and hardware/switch acceptance. Include fraud/restriction changes during execution, exact monetary boundaries, stale approval, duplicate and reordered events, unknown results and recovery. Test native saved document/CSV contents where offered. Use seeded synthetic data with two institutions and independent maker/checker identities. State the exact environment/build/URL and verify every test credential in that environment. Passwords remain outside repository/Mintlify content.

​
Release readiness checklist

  • Institution licence/capability and product terms accepted by accountable bank owners.
  • Authoritative interfaces certified; processor/network and ATM hardware acceptance where applicable.
  • Financial books, subledgers, controls and settlement reconcile.
  • Required disputes, complaints, recovery and exception ownership available; explicit bank-approved fallback where allowed.
  • Security/PCI assessment scope, privilege review, secrets and data-residency controls accepted.
  • Capacity/latency targets and monitoring agreed and verified.
  • Backup/restore/failover meets accepted RPO/RTO with in-flight operations reconciled.
  • Migration, operational training, support and rollback accepted.
  • Named bank UAT owner and explicit release authority approve the actual build.
No local preview, passing mock suite, signed-out smoke test or saved form establishes these gates. CI was previously excluded for local legacy review; the new project’s release checks must be agreed, not silently bypassed or started here.