Architecture Library

Stable public views of the reference architectures we work with. A reference architecture is a reusable pattern for a recurring problem, designed to be read, questioned, and reused. We publish the concepts, outcomes, and boundaries here; detailed schemas and methods stay protected.

C3, the reference architecture for governed action

Capability, Context, and Consent. Our most-used reference architecture, and how a bank lets an agent act while staying accountable. It sits beneath the Seven Intelligences, not above them.

Capability Governed banking capabilities, the Domain Building Blocks Context A shared semantic layer of meaning agents can reason over Consent Every agent action authorised, evidenced, and revocable

Read the argument in C3: the spine of Owned Autonomy.

Stable views

Each links to a public paper or a demonstration. The deeper detail is worked through under an engagement, not published.

C3 reference architecture

Capability, Context, and Consent: governed human and machine action. Read the paper.

Domain Building Blocks

Reusable banking capability units, the Capability plane of C3. Read the paper.

Governed data products

Engines built on the products, not the other way round. See the data products.

Value exchange

Payments, deposits, and programmable value on open standards. See the demonstration.

Platform evolution

Define the target architecture first, then choose the platform that conforms to it. See the platform.

Trust and inclusion

Justified trust through consent, evidence, and design from the excluded edge. See Trust Intelligence.

Reconciliation by construction Demonstrated

An authoritative ledger commit journal, drift detection that classifies divergence as clean, drift, or incomplete, and maker-checker repair, demonstrated in the prototype. Reconciliation never mutates the authoritative ledger.

Resilience Blueprint

A self-diagnosing estate that watches itself and reports who was harmed. Distinct from reconciliation above and not yet built. See the resilience architecture.

Continuous control

Authority set, outcomes observed, intervention, and evidence as the bank runs. See Control Intelligence.

What is public, and what is protected

We publish concepts, outcomes, named roles, and evidence boundaries. Detailed schemas, control internals, catalogues, and implementation mechanics are worked through under an engagement, through the Architecture Room. This keeps the public views honest and the methods protected.

Want to go deeper on one of these?

Tell us the decision in front of you and we will walk the relevant reference architecture, and the evidence behind it, with you.

Discuss a challenge