English | 简体中文
Cambium is a governance standard and reference toolset for knowledge repositories maintained with LLM agents.
It helps an operator answer five practical questions:
- What rules apply to this repository?
- What work is required, and who may change shared state?
- What evidence must exist before work can close?
- How can an interrupted task resume without guessing?
- Which decisions belong to the operator rather than the agent?
Cambium is not a knowledge base, a RAG engine, an agent scheduler, or a default domain policy. It governs work; it does not supply the corpus or decide its meaning.
- To understand the model, read The Mental Model.
- To adopt Cambium for a repository, follow Adopt Cambium.
- To resume existing work, run the command in Start Or Resume A Task before writing anything.
- To connect an agent host, see Use Cambium From An Agent Host.
- For every tool and its exact arguments, see Tools/README.md.
- For what is complete, in progress, or only conditional, see ROADMAP.md.
effective governance
= Cambium kernel
+ exactly one selected profile
+ adopter-owned runtime state
The diagram shows how these layers connect to runtime routes, deterministic tools, and agent execution contexts.
| Layer | What it owns |
|---|---|
kernel/ |
Cross-domain governance semantics, invariants, state meanings, and extension points |
Card/ |
Curated, non-authoritative flight checklists for an already selected task route or phase |
Read Set/ |
Machine-resolvable declarations of what canonical material an already selected route or phase must load |
| Selected profile | One repository's scope, language, architecture, sources, priorities, roles, scans, and allowed extensions |
.cambium/ |
The adopter's current governance identity, task state, Queue, plans, deltas, receipts, and recovery evidence |
Tools/ |
Stable public commands and Area/Domain implementations for deterministic checks, controlled writes, schemas, and generated projections |
The kernel is normative. A profile can fill or tighten an extension point, but cannot disable a kernel rule. Tools execute declared rules; they do not make the final semantic judgment.
