Seven stages carry a case from intent to rule learning: proposal, envelope, negotiation, agreement, execution, evidence, learning.
Functional catalogue
Functions, services, and domains.
A reference to the 21 functions that make up Civic Ledger: what each one needs, what it produces, and the role it plays in a case. Then see how functions chain together into a service.
21 functions
Functions × domains, grouped by role
Every function on one page. Rows are grouped by the role a function plays in a case; columns are the seven domains. A filled mark is the function's primary domain, an outlined mark a domain it also connects to. Select a function name to open it.
primary domain connected domain
How to read the catalog
The catalog describes Civic Ledger as a set of governed capabilities. Domains say what kind of outcome a capability produces; structure says what role it plays in a case — moving it forward, governing it, or describing the world it acts on; service chains show how capabilities compose into something a person would recognise as a service.
Identity, authority, consent, security, audit, interface, operations, and agentic support apply across the lifecycle rather than sitting in it.
Spaces, organizations, and jurisdictions are the world the lifecycle acts on; domains group all functions by the outcome they produce.
A real service sequences lifecycle stages while controls and context are invoked at each step.
Glossary
- Domain
- One of seven areas of the architecture, each named for the principal state it produces — a context graph, a trust and authority state, a bounded decision envelope, Conditions for Yes, executable commitments, an auditable record, or proposed institutional updates. Every function has one primary domain (its colour) and may connect to others. Domains are for orientation, not deployment boundaries.
- Function
- The unit of the catalog (sometimes called a function area): a governed capability with defined inputs, outputs, and worked examples. There are 21. "Function" here means a product capability, not a single code function.
- Lifecycle stage
- One of seven steps a case moves through: intent & proposal → decision envelope → conditions & negotiation → conditional agreement → access & execution → evidence & completion → rule learning. A lifecycle function changes the state of a case; it is the reason the case advances.
- Cross-cutting control
- A capability that governs every stage rather than sitting in one — identity, authority, consent & privacy, security, audit & provenance, interface, operations, and agentic support. Controls decide who may act, under what consent, with what record, and how the interaction is delivered; they do not themselves move a case forward. Shown with dashed markers.
- Context registry
- Functions that describe what exists — civic spaces, organizations, jurisdictions — and keep that description verified and current. They are the world that lifecycle stages act on. Shown with square markers.
- Service chain
- A worked example of how function areas compose, in sequence, into a service a person would recognise — opening a meeting, running a market, activating cooling centres. Chains are illustrative: the same function can appear in different sequences, and a chain is not a fixed deployment boundary. "Build your own" lets you compose one and share it by URL.
- Inputs and outputs
- What a function needs in order to act, and what it produces. In a chain, one step’s outputs are typically the next step’s inputs.
- Overview matrix
- The Overview matrix tab: a grid of functions × domains, grouped by role. A filled mark is the primary domain, an outlined mark a connected one; it shows at a glance which functions span many domains and which are narrow.