Skip to main content
All decisions below are open for the new Banking project unless explicitly recorded as confirmed. Describing a candidate module or fictional example does not approve it.

Confirmed project scope

New project name Banking; Super Admin, Banking Operations, Customer Web, mobile-facing APIs and ATM application; bank/NBFC and debit/prepaid/credit-card coverage; configurable offerings; Mintlify-first review with module flows/examples; confirmation before implementation.

Decision 1: core ownership

Required selection: Pending. The authoritative account, deposit/loan subledger and general-ledger ownership model must be recorded as owned core, external-core operations or an explicitly defined hybrid. The selected core boundary determines financial-book ownership, implementation scope, interface contracts and release evidence for the first institution.

Sequenced remaining decisions

The following inputs are sequenced after core ownership and require accountable-owner confirmation.

Decision record format

For each answer record authorised owner, date, selected option, rationale, scope, impacted modules, exact policy/contract/version, synthetic examples and remaining dependencies. Keep implementation authorisation separate from production release. Legacy permissions/holds remain facts about the old project. They are not automatically new financial grants and need not be re-asked to preserve their current behaviour. M01 acceptance is separately pending; reviewing Banking does not start M02 or accept the legacy release.