Definition · Translation review candidate
What is C³
Control Trust Engineering is a design field that connects the operating practices of AI and institutions to the formation of trust. The C³ Social Design Center is an early implementation hub for that field.
C³ (Currency × Credit × Cycle) is an institutional operating-system concept for handling the currency-credit cycle in a form that can be disclosed, paused, reviewed, and verified.
Here, the currency-credit cycle does not mean discretionary monetary-policy operation itself. It means an institutional architecture that connects public finance, credit, welfare, and markets with rules, history, and verification paths. C³ is a proposal for institutional architecture, not an ideology.
This definition page explains the core concept of C³. It does not fix a final policy conclusion; it organizes the structural framework of the institutional design and its position on the public surface.
Position of this page
This is the public definition page for the core concept of C³.
It does not fix final policy conclusions or value judgments. It organizes the structural framework of the institutional design and its position on the public surface.
Why it is needed
Existing institutions and governance can compress social complexity into a single aggregate score or a simplified causal narrative.
Structures such as public finance, credit, welfare, and markets inherently operate on different time horizons and under different constraints.
C³ is needed to treat them as control layers that can be paused, reviewed, and verified, instead of collapsing them into one answer.
The C³ position
C³ does not embed the value judgment of how much weight to assign to each concern inside an algorithm. It leaves that judgment with people while seeking to increase institutional transparency, interruptibility, and verifiability.
What C³ addresses
- Public finance
- Credit
- Welfare
- Markets
It addresses them while connecting them to mechanisms such as public surfaces, verification paths, ledgers, rail separation, and history management.
Public-surface components
C³ Anchor organizes the concept through the following public components.
- Verify ID →
A verification identifier that fixes the entry point to versions, procedures, verification paths, and history.
- Verified Web →
A structured reference surface that publishes definitions, specifications, update history, and verification paths together with their version and time relationships.
- Two-Rail Kernel →
The canonical structure that separates and connects the public rail and the private rail.
- Registry / Verification Surface (Japanese reference) →
A public surface that identifies routes to versions, procedures, evidence, history, and verification kits.
The state C³ seeks
C³ does not seek automation of institutions or operations for its own sake.
What matters is not unstoppable automation but automation that can be stopped; not operations that cannot be reviewed but operations that can be reviewed; and not inexplicable outputs but a public surface with verification paths.
Meaning for organizations and implementers
For organizations and implementers, it is not enough for C³ to exist only as an abstract concept.
They need to be able to organize what is disclosed, what is shown with a verification path, and where conformance, licensing, and support begin.
This page presents the C³ framework as that entry point.
What it does not mean
This page does not indicate that a policy is correct, provide quality assurance, promise investment returns, grant exclusive rights, or confer specification-setting authority.
It also does not indicate that C³ is already a completed institutional implementation or a fully operational social operating system.
Detailed conformance conditions, license conditions, support design, and verification operations are delegated to other pages and future institutional documents.
Source documents for this page
C3 Master Book — ANCHOR v1.1
Primary source corpus • Core conceptual foundation
C3 Anchor OS Adoption Pack v1 — S-0K_MDS
Supporting source • Implementation guidance
Institutional AI Roadmap (RFD)
Supporting source • Policy roadmap reference
Time layer
Status: Draft Concept
Version: 1.0
Last Updated (source): 2026-04-19
Source Doc Versions: C3 Master Book — ANCHOR v1.1, C3 Anchor OS Adoption Pack v1, RFD
Document lineage ID: C3-DEF-C3-01
Source semantic revision: sr-0.1.0
Governance identity boundary
C3-DEF-C3-01 is this translation group's document lineage ID. It is not a Registry snapshot Verify ID and it does not issue or inherit a C3-REF value.
This English review candidate has no Registry binding of its own. Translation status and Registry identity remain separate.