Banking.
Define a banking participation dataset.

Banking would model the financial accounts behind everyday city life — customers, accounts, balances and transactions belonging to the same synthetic citizens who already have an age, a household, an employment history and a housing situation elsewhere in FCTE.

None of that exists in the engine today. This page is a scoped, honest roadmap — not a live domain page — because the correct alternative was inventing account numbers, balances and certification scores that don't exist. We chose not to.

Lagos City Twin™ · 1940–2026

The six capabilities below describe what a Banking domain would need to cover to deliver the experience this page's own signature section illustrates. None are active in the current release today; this page is roadmap scope rather than an design specification.

Synthetic citizens (and, if scoped in, businesses) participating in the banking system — would extend Citizen and Business, the same implemented release entities every other domain already links to, rather than inventing a parallel identity concept.

Individual financial accounts tied to exactly one valid customer — the same strict either/or ownership discipline PrivateVehicle and TaxAccount already enforce in this engine today.

A product vocabulary (e.g. Savings, Current, Business, Credit) — would need real Nigerian retail-banking product research before any vocabulary is finalized, the same evidence-first approach this engine used for Vehicles' plate/ownership vocabularies.

Financial state associated with an account, where modeled — no balance-generation logic (opening balance, drift, minimums) has been designed yet.

Deposits, withdrawals, transfers and other account activity through time — would require its own temporal financial-activity model, distinct from Transport mobility and government-finance activity.

Opening, activity, status change and closure, temporally coherent against the owning citizen's own lifecycle (birth, death, migration) — the same DOB/DeathDate guard pattern this engine already applies to Vehicles, Land and Business ownership.

Synthetic by design, once built: FCTE would contain no real bank customers, account numbers, balances or transactions — only analytical representations of a plausible banking system, generated for synthetic citizens who don't exist either.

No field list, no integrity rule, no stable identity strategy has been decided for any of the above — naming them here is scope-setting, not an design announcement.

No live result is shown because this domain is not yet published as a generated release. Compare this to the published semantic query on Vehicles → or Taxation → , both of which show release-backed data.

Possible connections for scoping a future release. No implemented record links are asserted.

This is the experience Banking would deliver once real — shown here as a labeled wireframe, not a real citizen, account, or transaction record. No citizen numbered below exists; no account numbered below exists.

Every record in the diagram above resolves to real FCTE domains except Banking itself — Citizen, Household, Employment and Business are real, deployed, and already cross-linked to each other. Banking is the one missing layer that would connect them into a financial lifecycle.

FCTE's catalog lists all three, and the distinction matters before any of Banking is built: it prevents the eventual domain model from silently duplicating what the Finance domain and the real Economy domain already do.

Banking would model the financial institution relationship. The deployed government-finance domains model tax and budget, not household or business banking. Economy models the macro climate around both. The catalog's own separate "Finance" card (household/business income, spend and credit) is a fourth, still-unbuilt concept distinct from all three — deliberately out of scope for this page.

• Customer
• Account
• Transaction
• Banking participation

• TaxAccount / TaxAssessment / TaxPayment
• BudgetHead / BudgetAllocation / BudgetExpenditure
• Department / Directorate

• Historical Economic Event record
• Economic Modifier (feeds Employment)
• Sector / Investment ledger

Unlike every published domain in this catalog, Banking has no deployed domain model, so there is no realism angle, no structural check, and no live count to report — not "not yet written," but "nothing exists to write a check against."

Current release history explicitly records that resident banking relationships were scoped out as a separate future domain, before this graduation started — this is a documented, deliberate deferral, not an oversight discovered while writing this page.

Every other domain page in this catalog reports either a real certification count or, at minimum, a real generated table with a disclosed absence of certification (as Vehicles does). Banking cannot honestly claim even that — no generated release exists yet to certify.

There is no release history for a Banking domain anywhere in the engine, because no Banking work has been started.

This is the single limitation underlying every section above. Nothing on this page should be read as describing current engine behavior — it describes a scoped, honest roadmap.

No domain in this engine — Banking or otherwise — currently represents mobile-money wallets or transaction networks.

No credit-scoring, lending, or default-behavior concept exists anywhere in the engine today, for Banking or the separate, also-unbuilt catalog "Finance" (household/business credit) card.

domain-docs.html lists a household/business income-spend-credit "Finance" card, distinct from both this page and the deployed government-finance domains documented on Taxation and Public Finance . All three "Finance"-named concepts in this catalog answer different questions — worth reading carefully.

Unlike Vehicles, which was grounded in Nigeria NBS/FRSC registration evidence before data structure work, Banking has not yet completed an equivalent financial-inclusion evidence review. A future build should start with sources such as World Bank Findex and CBN publications before any production data structure is claimed.

Back to Domain Directory →

Already deployed, connected, and certified elsewhere in this catalog.

Customer, Account, Transaction — the missing layer this page scopes but does not build.

Government tax/budget and macro climate — real, deployed, and already bounded away from Banking above.

A conventional synthetic-banking product can generate millions of realistic-looking transactions with no context behind them. FCTE's argument, once Banking is real, would be that the person behind each transaction already has an age, a household, an employment history and a housing situation elsewhere in the same synthetic city — that connective tissue is the differentiator, and it's exactly why this page refused to fabricate the account numbers to make that case prematurely.

Citizen → Employment → Income → Account → Activity — a real workflow, once Banking exists to complete it.

Available as Standalone Domain · Multi-Domain Bundle · Full City Twin™