Prototype Specifications

A Prototype Specification is the executable blueprint produced from a reference architecture and a journey. It is how a decision moves from a pattern to something a client can build, expressed in open standards so it stays portable and vendor-neutral.

Where a specification sits

From the mission down to a system a client runs. A reference architecture and a journey produce a Prototype Specification, proven in a working model, carried out as a working specification, and built into an executable system.

Preservation Evolution Augmentation Three themes cut across every layer below Mission Principles Seven Intelligences Experience Journeys Reference Architectures Prototype Specifications Ultim8 held until stable Executable Systems

Five terms, each with one job

We keep these distinct so a client always knows what they are looking at.

Reference architecture

A reusable pattern for a recurring problem, such as C3. It is not specific to one bank or one journey.

Prototype specification

The executable blueprint produced from a reference architecture and a journey. The bridge from pattern to build.

Working prototype

A running proof on Accountable Bank, on synthetic data, with test consumers and never real customers.

Working specification

The portable artefact a client takes to any vendor, expressed in ISO 20022, BIAN, and recognised control frameworks.

Executable system

What the client builds and runs from the specification, with their chosen vendor and stack.

Published examples, with status and provenance

Each carries an honest label. A demonstration genuinely runs; a blueprint is designed and specified, not yet demonstrated end to end.

C3

A reference architecture: the Capability, Context, and Consent pattern, stable and reused across journeys. In the Architecture Library.

Accountable Bank Demonstrated

Our working prototype: four journeys run as interactive demonstrations; Franchise Network is a blueprint. Explore it.

Vendor-neutral working specification Specified

The artefact a client takes to whatever vendor and build they choose. Produced from an engagement, expressed in open standards.

Synthetic Bank Migration Twin Blueprint

A prototype specification for migrating into a governed target architecture, as a sequence of commercial propositions. See the migration journey.

The claim boundary stays explicit

Provenance, stability, and claim status are separate questions. We never let one stand in for another.

Demonstrated

The mechanism genuinely runs in the prototype.

Simulated

Inputs are generated test fixtures.

Specified

Production scale and cutover are described, not executed here.

The boundary. Synthetic data. Test consumers, never real customers. Production-grade controls. Not a production banking system.

Have a journey worth specifying?

Bring the proposition and the journey. We will prove the hard parts in a working model and leave you a specification you own.

Discuss a challenge