Skip to main content
Source review, 13 October 2026. No new application tests or bank operations were executed to prepare this gap assessment. The existing workspace is banking_app, with separate Super Admin, Banking, Customer and shared server applications. Its 23 legacy module documents describe a mixture of bounded implementation, partial work, gaps and excluded scope. The new Banking proposal has 35 modules and a broader application/offering boundary.

​
Evidence inventory

​
What is missing for a bank deployment

  1. Chosen authoritative customer/account/ledger model and complete relationships.
  2. Verified customer onboarding and approved institution-specific product policy.
  3. Exact posting, accrual, balance/hold, quote and reversal behaviour.
  4. Deposit, payment and loan instruction/status/finality interfaces or owned engines.
  5. Debit/PPI/credit issuance, processing, billing, settlement and disputes.
  6. Certified ATM/device/switch and physical-cash custody integration.
  7. Reconciliation, business-date/EOD controls and financial/regulatory records.
  8. Privileged identity commissioning, recovery, security assessment and bank-owned UAT.
  9. Data migration/control totals, capacity, restore/failover and production operating ownership.

​
Status interpretation

All new-project modules are proposed, not built. Reuse candidates can reduce duplicated engineering after targeted audit; they cannot supply missing business rules or certifications. Legacy M01 is ready for local acceptance in its approved scope, not bank-wide production readiness. Some historical access documents say routes are development-only. Current apps/server/src/app.ts mounts implemented staff routes in production; the 12 October production-parity record supersedes those route-absence statements. Mounted endpoints still do not establish authenticated hosted acceptance, real identity or financial execution.

​
Review next

Choose the core ownership boundary first. Then agree the first institution/offering and source contracts. Reassess each reused feature against new institution/programme/channel permissions before adopting it. Preserve existing customer data and configuration; this documentation creates no migration, deployment or silent permission changes.