Colibri Glossary

Every Colibri-specific term, alphabetized, cross-linked. Entries are one paragraph. If a term here disagrees with the world-schema or with colibri-system.md, trust the world-schema first, then colibri-system.md.

This page is the single-page glossary — canonical for Colibri vocabulary.

A

α — System Core. The execution-axis concept covering the MCP server entry point, SQLite store, and middleware chain. It is the substrate on which every other concept runs. Target module src/server.ts, src/db/, src/middleware/. See 2-plugin/boot.md. Phase 0 (P0.2). colibri_code: none.

AAL — Action Admission Layer. The entry gate that rate-limits, stake-checks, and quality-filters incoming events before they reach consensus. Part of the legitimacy axis under κ. See spec/s10-admission.md.

ADR — Architectural Decision Record. A numbered document under architecture/decisions/ recording an accepted architectural decision with context, alternatives, and consequences. The R73 corpus introduced ADR-004 (tool surface), ADR-005 (multi-model defer), and ADR-006 (executable meaning).

Agent. A runtime instance operating at one of the four tiers (T1–T3). In Phase 0 every agent is a Claude session. An agent is bound to a contract (see T1/T2/T3 contracts below) and runs a specific skill from .agents/skills/.

Agent tiers. See T0, T1, T2, T3, T4.

AMS — Agentic Management System. The donor project whose runtime code lived under src/ until R53. Its algorithms were extracted to reference/extractions/ and its name survives only in the GitHub repo URL (github.com/E1337Kamal/ams) and in data/ams.db (the legacy task store used during Phase 0 bootstrap). The “484 tools” number is an AMS heritage figure, not a Colibri target. See Donor absorption.

Audit chain. The hash-chained sequence of thought records inside one session, verified by audit_verify_chain. Every thought’s hash includes the previous thought’s hash; breaking the chain invalidates every subsequent record. See 3-world/execution/decision-trail.md.

audit_session_start / audit_verify_chain. MCP tools bracketing a proof-grade work unit. audit_session_start begins a new audit session; audit_verify_chain walks every thought and confirms the hash chain is unbroken. Both are prerequisites for merkle_finalize. See agents/writeback-protocol.md.

Axis. One of the three organizing dimensions of Colibri: execution (work is defined, ordered, delivered), intelligence (work is routed and reasoned about), legitimacy (work is provable and governed). Every level of the pipeline must leave a signal on every axis or it cannot close. See 5-time/round.md §2.

B

β — Task Pipeline. The execution-axis concept implementing the 7-state FSM (INIT → GATHER → ANALYZE → PLAN → APPLY → VERIFY → DONE + CANCELLED). Every task in Colibri is governed by β. Target module src/domains/tasks/. See 3-world/execution/task-pipeline.md. Phase 0 (P0.3).

Backlog. A task state meaning not yet promoted to executable. Only the PM (T2) may promote a backlog task to todo. Executors picking a backlog task is a contract violation. See todo, promotion.

Bootstrap — Chain 0. The startup sequence every agent runs before touching any file: read CLAUDE.md, read AGENTS.md, read colibri-system.md, call unified_init, unified_vitals, unified_set_project, task_next_actions, then pick an unblocked todo task and move to its worktree. Described in CLAUDE.md §4.

BFT — Byzantine Fault Tolerance. A class of consensus algorithms that tolerate up to f < n/3 faulty nodes. Used by θ Consensus. See 3-world/physics/laws/consensus.md.

C

Cancelled. The terminal state a task enters when its scope is rejected or permanently blocked. Distinct from DONE; must carry a written reason. Part of the β FSM.

Chain 0 Bootstrap. See Bootstrap.

Claude. The only LLM Colibri talks to in Phase 0. Multi-model routing (Kimi, Codex, GPT-class) is deferred to Phase 1.5. See architecture/decisions/ADR-005-multi-model-defer.md.

colibri_code frontmatter. A per-concept field recording the executable state of that concept. Values: none (no code), stub (types only), partial (some tools work), complete (all tools work, tests passing). All 15 concepts are currently none. Semantics defined in architecture/decisions/ADR-006-executable-meaning.md.

colibri-docs-sync. The skill that mirrors docs/ into the Obsidian vault. One-way: repo → vault. Never vault → repo. See 3-world/social/surfaces.md §4.

colibri-system.md. The canonical vision document. Every other doc is either a projection of it, a sub-topic of it, or deprecated. Introduced in R73 to replace six overlapping “master” docs. See colibri-system.md.

Cold reader. A newcomer to the project who has not seen the history. Cold-reader navigation is the set of entry points (index, agent bootstrap, quick start, FAQ, glossary) designed to orient this reader in under 30 minutes.

Concept. One of the 15 Greek-letter elements of Colibri’s design. Concepts are parts of the runtime (α through ξ). Concepts are not agents. See world-schema.md.

Concept docs. The 15 Greek-letter specs distributed across the World Schema (see world-schema.md): laws (physics), actors (social), pipeline (execution). Each doc contains TL;DR, promise, behavior, operations, data model, and status. These are authoritative when they disagree with any other file.

CogniMesh. One of three donor projects absorbed by Colibri. CogniMesh contributed intelligence patterns (routing, thought chains, audit scoring). Its source was deleted in R52; patterns live in reference/extractions/.

Consensus. See θ.

Contract (5-step chain). The second step in the executor chain, producing docs/contracts/<name>-contract.md. The contract records the behavioral contract for the work (inputs, outputs, invariants, failure modes) before the packet is written. See 5-time/round.md §5.2.

Contract (tier). The authority and obligations of a tier — Sigma contract (agents/sigma-orchestrator.md), PM contract (agents/pm-contract.md), executor contract (agents/executor-contract.md), writeback protocol (agents/writeback-protocol.md).

D

δ — Model Router. The intelligence-axis concept implementing multi-factor scoring over candidate models. In Phase 0 the router is a Claude-only stub; multi-model scoring lands in Phase 1.5. Target module src/domains/router/. See 3-world/social/llm.md and architecture/decisions/ADR-005-multi-model-defer.md.

Decision Trail. See ζ.

Donor absorption. The pattern by which Colibri folded in three upstream projects: AMS (execution runtime), CogniMesh (intelligence patterns), Phoenix (legitimacy specs). Absorption is complete; all donor source code is deleted (R52–R53). What survives are algorithm extractions in reference/extractions/.

E

ε — Skill Registry. The execution-axis concept managing reusable skill definitions, sub-agent spawning, and capability profiles. The 23 canonical skills under .agents/skills/ are registered through ε. Target module src/domains/skills/. See 3-world/execution/skill-registry.md. Phase 0 (P0.6).

Executable meaning. The semantics of the colibri_code frontmatter values (none, stub, partial, complete). Defined in architecture/decisions/ADR-006-executable-meaning.md.

Execution axis. One of the three axes. Covers α β γ ε. Its promise: work is defined, ordered, delivered. Every task must signal on this axis by reaching the DONE state of the β FSM. See 5-time/round.md §2.1.

Executor. See T3.

Extraction. A language-agnostic description of an algorithm harvested from a donor project. 49 extractions live in reference/extractions/ — 22 original R45–R50 extractions plus 27 function-level R53 extractions. Extractions are the only executable knowledge Colibri carries from its donors.

F

FAQ. Cold-reader “what is this?” questions are answered at the bottom of guides/quick-start.md and in the FAQ row at the end of cross-reference.md.

Finality. The consensus state at which a decision becomes irreversible. θ Consensus defines multiple finality levels (soft / hard / final). No irreversible side effects may happen before HARD finality. See 3-world/physics/laws/consensus.md.

FSM — Finite State Machine. The mechanical model of β Task Pipeline. Seven states plus a terminal CANCELLED branch. See β.

Four surfaces. The four simultaneous physical locations of Colibri work: (1) the repository, (2) the worktrees, (3) the Obsidian vault, (4) GitHub Pages. Each has a distinct direction of truth. See 3-world/social/surfaces.md.

Four-tier agent hierarchy. T0 Human → T1 Sigma → T2 PM → T3 Executor → T4 Model. Only the tier below may execute on behalf of the tier above. No skipping. See colibri-system.md §4.

G

γ — Server Lifecycle. The execution-axis concept describing the server’s 6-phase boot sequence and its 5 runtime modes. Graceful boot and shutdown are its responsibility. Target module src/server.ts (boot/shutdown). See 2-plugin/modes.md. Phase 0 (P0.4).

GitHub Pages surface. The public reading surface for Colibri. Jekyll + just-the-docs remote theme, built from docs/ by GitHub Actions on every push to main. Read-only from an agent’s perspective. See 3-world/social/surfaces.md §2.2.

GitHub remote surface. The cloud-side repository at github.com/E1337Kamal/ams. The merge target for PRs. Only T0 may merge. The source of truth for every tool that checks out the repo.

Governance. See π.

Greek-letter concept. See Concept.

H

η — Proof Store. The legitimacy-axis concept building a SHA-256 Merkle tree over all operations, generating inclusion proofs, and managing retention zones (Hot / Warm / Cold). Shipped module src/domains/proof/ (directory name is proof, not merkle). See 3-world/physics/laws/proof-store.md. Phase 0 (P0.8) — complete in Wave F.

Hash chain. The linked list of thought records where each record’s hash includes the previous record’s hash. Tamper-evident: changing any record invalidates every record after it. Implemented by ζ. See 3-world/execution/decision-trail.md.

Hot / Warm / Cold zones. The retention policy implemented by η Proof Store. Hot is recent in-memory data (7d); Warm is on-disk SQLite (30d); Cold is out-of-process archival (365d). A Frozen tier is spec-only. See 3-world/physics/laws/proof-store.md.

Human (T0). See T0.

I

ι — State Fork. The legitimacy-axis concept describing context branching and the P2P sovereignty fork protocol. Spec-only, Phase 5. Target module src/domains/fork/. See 3-world/physics/laws/state-fork.md.

Inclusion proof. A Merkle path (leaf hash + sibling hashes + positions) that proves a single operation is part of the Merkle tree without downloading the entire dataset. Generated by merkle_proof, verified by merkle_verify. See 3-world/physics/laws/proof-store.md.

Intelligence axis. One of the three axes. Covers δ and ζ. Its promise: work is routed to the right model and reasoned about in hash-chained steps. Every task must signal on this axis by producing at least one reflection thought record. See 5-time/round.md §2.2.

Integrations. See ν.

Integrity Monitor. See μ.

J

Jekyll. The static site generator that builds GitHub Pages from docs/. Uses the just-the-docs remote theme and a custom hero block defined in docs/_includes/ and docs/assets/css/custom.css.

K

κ — Rule Engine. The legitimacy-axis concept implementing a deterministic 64-bit integer interpreter and a domain-specific language (DSL) for rules. Forbids randomness, floating-point, and clock reads. Spec-only, Phase 1. Target module src/domains/rules/. See 3-world/physics/laws/rule-engine.md.

L

λ — Reputation. The legitimacy-axis concept implementing acknowledgement-based scoring, decay, and experience tokens (L0–L3). Spec-only, Phase 2. Target module src/domains/reputation/. See 3-world/social/reputation.md.

Legitimacy axis. One of the three axes. Covers η θ ι κ λ μ π ξ. Its promise: work is provable, constrained, governed — not only the result, but the right to the result. Every task must signal on this axis via Merkle leaves or audit verification. See 5-time/round.md §2.3.

M

μ — Integrity Monitor. The legitimacy-axis concept running circular-logic detection, anomaly detection, and coercion traps. Partial, Phase 4. Target module src/domains/integrity/. See 3-world/physics/enforcement/integrity.md.

Main branch. main is the only long-lived branch. All work happens on feature/* branches and merges via PR. Force-pushes to main are forbidden; only T0 may merge.

Manifest (Phase A). The round-planning document Sigma emits at the start of every round. Lists slices, owners per slice, dependencies, and definition of done. Lives at .agents/spawns/rNN-<theme>/manifest.md. See agents/sigma-orchestrator.md.

MCP — Model Context Protocol. The Anthropic protocol Colibri implements as its primary I/O surface. MCP defines tool registration, request/response shapes, and transport (stdio in Phase 0). See the @modelcontextprotocol/sdk reference.

MCP server. The Colibri process itself, viewed from the outside. It registers MCP tools and listens on a stdio transport. Target entry point src/server.ts. See 2-plugin/boot.md.

MCP tool. A named, schema-bound function exposed by the Colibri MCP server. Zod schemas govern inputs and outputs. Target tool count: 60–80 across 10 domains (see architecture/decisions/ADR-004-tool-surface.md).

Merkle root. The single hash at the top of the Merkle tree summarizing the entire session state. Produced by merkle_root; archived in the session seal document. Changing any leaf changes the root. See 3-world/physics/laws/proof-store.md.

Merkle tree. The binary tree whose leaves are operation hashes and whose interior nodes are SHA-256 of child concatenations. Incremental; new leaves append. Finalization locks the tree. See Merkle root, Inclusion proof.

merkle_finalize. The MCP tool that locks the current Merkle tree — no more leaves may be added. Required at task close for proof-grade work. Must come after the final thought record. See agents/writeback-protocol.md.

Middleware chain. The ordered set of wrappers through which every MCP tool call passes. Phase 0 ships four layers (logging, error handling, rate limiting, request validation); the full 11-layer chain is deferred. Target module src/middleware/. See 2-plugin/boot.md.

Mirror zone. The subtree of the Obsidian vault (Obsidian Vault/Colibri/docs/) that mirrors the repo’s docs/. Never edit files here — every edit is silently overwritten on next sync. Planning lives in _vault/. See 3-world/social/surfaces.md §3.

N

ν — Integrations. The cross-cutting concept (not an axis) bridging the runtime to GitHub, Obsidian, Claude API, and editor tooling. Partial, Phase 0.9+. Target module src/domains/integrations/. See 4-additions/index.md.

O

Obsidian vault surface. The human reading and planning surface at C:\Users\Kamal\Documents\Obsidian Vault\Colibri\. Has two zones: the docs/ mirror (repo → vault, read-only) and _vault/ planning (vault-only, never committed). See 3-world/social/surfaces.md §3.

P

π — Governance. The legitimacy-axis concept running proposal lifecycle, quadratic voting, and constitutional protection. Spec-only, Phase 6. Target module src/domains/governance/. See 3-world/physics/enforcement/governance.md. Note: in earlier doc-loop agent naming, π was also used as a verifier role — that collision was retired in R73.

Packet. The third step in the executor 5-step chain, producing docs/packets/<name>-packet.md. The packet is the concrete execution plan and gates implementation: Step 4 (implement) may not begin until the packet is approved. See 5-time/round.md §5.2.

Phase (runtime). One of the 6 phases of γ Server Lifecycle boot: transport → lock → DB → domains → watchers → ready. Not to be confused with Phase (project).

Phase (project). One of Colibri’s nine implementation phases (Phase 0 through Phase 8). Phase 0 is the bootstrap (runtime alive); Phase 1 is κ; Phase 2 is λ; Phase 3 is θ; Phase 4 is μ; Phase 5 is ι; Phase 6 is π; Phase 8 is ξ. See guides/implementation/task-breakdown.md.

Phase A / W / B (round). The three phases of every round. Phase A is Sigma planning; Phase W is PM dispatching executors in five sequential waves; Phase B is Sigma sealing the round. See 5-time/round.md §4.

Phoenix. One of three donor projects absorbed by Colibri. Phoenix contributed legitimacy specs (Merkle, consensus, fork protocol, rule engine). Source deleted in R52; specs live in spec/ and reference/extractions/.

PM. See T2.

Promotion. The act of moving a task from backlog to todo. Only PM (T2) may promote. An executor who promotes is in contract violation. See agents/pm-contract.md.

Proof store. See η.

Proof-grade. A task classification requiring full Merkle anchoring: audit_session_start → work → audit_verify_chain → thought_record → merkle_finalize → merkle_root. All legitimacy-axis tasks are proof-grade; other tasks can be marked proof_grade: true in their prompt. See agents/writeback-protocol.md.

Q

Quick start. The 5-minute orientation guide at guides/quick-start.md. Cold-reader entry point.

R

R73 unification corpus. The 19-document rewrite that closed Session 6 by fixing the ξ/π collision, deleting stale “master” docs, and producing colibri-system.md as the single canonical vision. See session-seal-s6.md.

R74. The current round (Session 7 opener). Theme: design polish, documentation finish, hero rewrite. Final documentation-only round before R75 begins Phase 0 code.

Repo surface. The on-disk repository at E:\AMS and its GitHub remote. The authoritative source for every other surface. Only edited via worktree PRs. See 3-world/social/surfaces.md §1.

Retention zone. See Hot / Warm / Cold zones.

Round. A unit of orchestrated work spanning days. Named RNN (e.g. R73). Every round runs Phase A → Phase W → Phase B on a single branch namespace feature/rNN-<theme>. See 5-time/round.md §4.

Rule engine. See κ.

Runtime mode. One of the five runtime states of γ Server Lifecycle: starting, ready, degraded, draining, stopped. See 2-plugin/modes.md.

S

SBT — Soul-Bound Token. A non-transferable cryptographic token binding an identity to actions and achievements. Used by ξ Identity. See 3-world/social/identity.md.

Session. A months-long arc of 5–15 rounds sharing a theme. Ends with a seal document (docs/session-seal-sN.md). Sessions 1–5 complete; Session 6 sealed at R73; Session 7 opens at R74. See 5-time/round.md §3.

Session 7. The active session. Opens at R74 (design polish + documentation finish), closes at R80 (Phase 0 end-to-end flow and session seal). See 5-time/roadmap.md.

SHA-256. The cryptographic hash function used throughout Colibri — for thought chaining (ζ), Merkle leaves and interior nodes (η), and audit trail integrity. No other hash functions are permitted.

Shamir Secret Sharing (SSS). The (N, M) secret-splitting scheme used by ξ Identity for key recovery. Recommended parameters: N=5, M=3 (5 shares, any 3 reconstruct). See 3-world/social/identity.md.

Sigma. See T1.

Skill. A reusable tool-call sequence defined in .agents/skills/<name>/SKILL.md with YAML frontmatter and a Markdown body. 23 canonical colibri-* skills are tracked in the repo; ams-* redirect stubs were removed in R75. See ε.

Skill Registry. See ε.

Slice. One discrete work unit listed in a Phase A manifest, mappable to exactly one task. A round’s manifest is a list of slices with owners and dependencies. See agents/sigma-orchestrator.md.

Soul vector. The 8-domain × 7-trait multi-dimensional vector encoding an agent’s behavioral history. Implemented by ξ Identity. Dimensions grow logarithmically; all values bounded 0.0–1.0. See 3-world/social/identity.md.

SQLite. The single database Colibri uses. Single-writer, file-backed, ACID. Accessed via better-sqlite3. Phase 0 target file: data/colibri.db. See architecture/decisions/ADR-001-sqlite-migration.md.

SQLite migration. A versioned schema change applied at startup by the db wrapper. Migrations are forward-only; rollback is not supported. See architecture/decisions/ADR-001-sqlite-migration.md.

Stack (R73). TypeScript 5.3+ · @modelcontextprotocol/sdk · Zod 4 · better-sqlite3 · Chevrotain · Jest (ESM). See colibri-system.md §2.

Stdio transport. The I/O transport used by the Phase 0 MCP server. No HTTP surface in Phase 0. See 2-plugin/boot.md.

System core. See α.

T

T0 — Human (owner). The single source of intent. Authorizes rounds, merges PRs, sets canonical vision. No agent may self-promote work or merge. Every destructive operation requires T0 authorization. See colibri-system.md §4.

T1 — Sigma Orchestrator. The round-level planner and sealer. Runs Phase A (manifest) and Phase B (audit + seal). Does not write code. Does not merge. See agents/sigma-orchestrator.md.

T2 — PM (Project Manager). The task-level manager. Runs the startup chain, promotes backlog → todo, dispatches executors by wave, enforces wave gates. Never writes code directly. See agents/pm-contract.md.

T3 — Executor. The hands-on worker. Runs the 5-step chain (audit → contract → packet → implement → verify) inside a dedicated worktree on feature/<task-slug>. Produces the writeback contract. May not promote backlog, may not merge, may not edit the main checkout. See agents/executor-contract.md.

T4 — Model. The underlying LLM powering agents at Tiers 1–3. Phase 0 assumes Claude only. Multi-model routing (Kimi, Codex, GPT-class) lands at Phase 1.5. See architecture/decisions/ADR-005-multi-model-defer.md.

Task. A single unit of work assigned to one executor. Lives in mcp_tasks. Governed by the β FSM. Every task completes with a writeback. See β.

Task pipeline. See β.

Theta. See θ.

θ — Consensus. The legitimacy-axis concept implementing Byzantine fault-tolerant quorum voting, equivocation detection, and finality levels. Spec-only, Phase 3. Target module src/domains/consensus/. See 3-world/physics/laws/consensus.md.

thought_record. The MCP tool that appends a thought to the hash chain maintained by ζ Decision Trail. Every task must produce at least one reflection thought_record as part of its writeback. For proof-grade work, the final thought_record must come before merkle_finalize. See agents/writeback-protocol.md.

Thought types. The taxonomy of thought records used by ζ: reflection, decision, observation, plan, demotion, etc. The writeback-protocol document lists the canonical set. See 3-world/execution/decision-trail.md.

Todo. The task status meaning ready to execute. Only PM may promote backlog → todo. Executors may only pick tasks already in todo. See backlog, promotion.

U

unified_init. An MCP tool in the bootstrap chain that initializes the agent’s working context. Run as step 4 of Chain 0 Bootstrap. See CLAUDE.md §4.

unified_set_project. An MCP tool that sets the active project namespace. Run as step 6 of Chain 0 Bootstrap. For Colibri work, always called with project_name="colibri".

unified_vitals. An MCP tool returning runtime health JSON (task counts, chain state, storage metrics). Run as step 5 of Chain 0 Bootstrap.

V

_vault/. The Obsidian vault’s planning zone — vault-only, never committed to the repo. Daily notes, round scratch, PM dispatch scratch, Sigma scratch all live here. See 3-world/social/surfaces.md §3.

Verify (5-step chain). The fifth and final step in the executor chain, producing docs/verification/<name>-verification.md with test evidence. Closes the β FSM by transitioning VERIFY → DONE. See 5-time/round.md §5.2.

Verifiable Random Function (VRF). A cryptographic primitive used by θ Consensus for arbiter selection. See architecture/decisions/ADR-002-vrf-implementation.md.

W

Wave. One of the five sequential phases of Phase W (round-level): (1) governance, (2) runtime, (3) domain, (4) integrations, (5) test / CI / docs. Wave N+1 may not begin until Wave N writeback is complete. See 5-time/round.md §4.2.

Wave gate. The hard rule that a wave may not start until the previous wave’s writeback is complete. A task in wave N+1 depending on a task in wave N is blocked, not started early. Empty waves pass the gate trivially but still log “empty — gate passed”.

Worktree. A per-task isolated copy of the repository under .worktrees/claude/<task-slug> on branch feature/<task-slug>. The only place T3 agents may edit files. Created via git worktree add, removed after PR merge. See CLAUDE.md §3.

Worktree surface. One of the four surfaces. Editable. Per-task isolated. Feeds back to the repo via PRs.

Writeback. The mandatory closing ritual every task performs: task_update(status="done", progress=100) followed by thought_record(thought_type="reflection", ...). For proof-grade work, additionally audit_verify_chain → thought_record → merkle_finalize → merkle_root. Ordering matters — thought before Merkle, always. See agents/writeback-protocol.md.

Writeback contract. The binding requirement that task_update(done) is only accepted if a matching thought_record has been written. Phase 0 P0.3.4 wires this enforcement into β Task Pipeline.

X (ξ)

ξ — Identity (Soul Vector). The legitimacy-axis concept implementing per-agent persistent identity via an Ed25519 keypair and a multi-dimensional Soul Vector (8 domains × 7 traits). Shamir Secret Sharing for recovery. Spec-only, Phase 8. Target module src/domains/identity/. See 3-world/social/identity.md. Note: in the old doc-loop naming, ξ was also used as an agent role — that collision was retired in R73.

Z (ζ)

ζ — Decision Trail. The intelligence-axis concept implementing SHA-256 hash-chained thought records with tamper detection. Every decision ever made is recorded; any modification after the fact invalidates the chain from that point forward. Shipped module src/domains/trail/ (directory name is trail, not thought). See 3-world/execution/decision-trail.md. Phase 0 (P0.7) — axis closed in Wave G.

Greek Letter Quick Reference

Letter	Name	Axis	Phase	Status
α	System Core	Execution	0 (P0.2)	Spec-ready
β	Task Pipeline	Execution	0 (P0.3)	Spec-ready
γ	Server Lifecycle	Execution	0 (P0.4)	Spec-ready
δ	Model Router	Intelligence	0 (P0.5)	Spec-ready
ε	Skill Registry	Execution	0 (P0.6)	Spec-ready
ζ	Decision Trail	Intelligence	0 (P0.7)	Spec-ready
η	Proof Store	Legitimacy	0 (P0.8)	Spec-ready
θ	Consensus	Legitimacy	3	Spec-only
ι	State Fork	Legitimacy	5	Spec-only
κ	Rule Engine	Legitimacy	1	Spec-only
λ	Reputation	Legitimacy	2	Spec-only
μ	Integrity Monitor	Legitimacy	4	Partial
ν	Integrations	Cross-cutting	0 (P0.9)	Partial
π	Governance	Legitimacy	6	Spec-only
ξ	Identity	Legitimacy	8	Spec-only

All 15 concepts currently carry colibri_code: none. Source: world-schema.md.

Part of the R74 documentation finish. Governed by colibri-system.md.