Colibri cross-reference

The docs tree is organised by topic. This page flips the index: pick a lens — Greek letter, axis, tier, phase, or surface — and find the documents that address it. Every entry points at a real file in docs/.


1. By Greek concept

All 15 concepts carry colibri_code: none at R74 — Phase 0 implementation has not started. Each row lists the concept spec, the how-it-works prescriptive page (if written), and the Phase 0 task prompt (if assigned).

World schema index: world-schema.md.


2. By axis

Colibri is a three-axis control plane: execution of work, management of intelligence, legitimacy of action. Each concept belongs to exactly one axis — see colibri-system.md §2.

Execution axis — “get the work done”

Related docs: 5-time/round.md, 3-world/social/surfaces.md, agents/executor-contract.md.

Intelligence axis — “manage the models”

Related docs: architecture/decisions/ADR-004-tool-surface.md, architecture/decisions/ADR-006-executable-meaning.md.

Legitimacy axis — “prove the work was done right”

Related docs: agents/writeback-protocol.md, agents/sigma-orchestrator.md (for Phase B seal).


3. By tier

Four-tier agent hierarchy; see colibri-system.md §4 and memory/reference_4tier_hierarchy.md for the canonical list.

T0 — Human (owner)

What they do Where it’s specified
State intent Chat logs, issues (no formal doc)
Merge PRs 3-world/social/surfaces.md §3
Veto / authorise destructive actions CLAUDE.md §5, agents/sigma-orchestrator.md §6

T1 — Sigma orchestrator

What they do Where it’s specified
Phase A round planning agents/sigma-orchestrator.md §2
Phase B round sealing agents/sigma-orchestrator.md §3
Writeback audit agents/sigma-orchestrator.md §4, agents/writeback-protocol.md §6
Round decomposition 5-time/round.md §4

T2 — PM

What they do Where it’s specified
Promote backlog → todo agents/pm-contract.md §3
Wave dispatch agents/pm-contract.md §4
Gate decisions (packet approval) 5-time/round.md §5.2

T3 — Executor

What they do Where it’s specified
Chain 0 bootstrap CLAUDE.md §4
Worktree discipline CLAUDE.md §3, 3-world/social/surfaces.md §2
5-step chain (audit / contract / packet / implement / verify) agents/executor-contract.md §2, 5-time/round.md §5
Writeback agents/writeback-protocol.md §2

T4 — Model

What they do Where it’s specified
Token-level completions inside T3 architecture/decisions/ADR-004-tool-surface.md
Phase 0: Claude only CLAUDE.md §2, 3-world/social/llm.md
Phase 1.5+: Claude + Kimi + Codex 3-world/social/llm.md §3 (deferred)

4. By phase

Colibri’s phased roadmap is in 5-time/round.md §3. R74 closes the documentation finish; R75 starts Phase 0 code.

Phase 0 — foundation

Phase 1 — intelligence expansion

Phase 1.5 — θ ι κ

Phase 2+ — legitimacy expansion and governance

Maturity summary (R74): Execution 100% specified · Intelligence 100% specified · Legitimacy 33% specified. All 15 concepts still at colibri_code: none.


5. By surface

The four surfaces — repo, GitHub remote, GitHub Pages, Obsidian vault — are the places Colibri state physically lives. See 3-world/social/surfaces.md for the full topology.

Surface 1 — repo (E:/AMS)

Surface 2 — GitHub remote

  • Topology rules: 3-world/social/surfaces.md §3
  • Push auth rule: memory/feedback_git_push_auth.md (unset GITHUB_TOKEN before push)
  • PR open/merge mechanics: 4-additions/index.md §2
  • Merge rule: only T0 merges; gh pr merge is never called by ν

Surface 3 — GitHub Pages

Surface 4 — Obsidian vault


6. By artifact type

Every 5-step chain step (see 5-time/round.md §5) produces artifacts in a specific folder:

Step Folder Suffix Commit template
1 Audit docs/audits/ -audit.md audit(<name>): inventory surface
2 Contract docs/contracts/ -contract.md contract(<name>): behavioral contract
3 Packet docs/packets/ -packet.md packet(<name>): execution plan
4 Implement src/ or target dir source feat(<name>): <change>
5 Verify docs/verification/ -verification.md verify(<name>): test evidence

Roadmap artifacts live in docs/roadmap/. ADRs live in docs/architecture/decisions/.


7. Quick questions → direct answers

Question Go here
What is Colibri? colibri-system.md
What is a “tier”? colibri-system.md §4, memory/reference_4tier_hierarchy.md
What is a Greek letter? world-schema.md
Where do I put a new task? guides/implementation/task-breakdown.md
How do I open a PR? 4-additions/index.md §2
How do I sync to Obsidian? 4-additions/index.md §3
Why can’t I use /MIR? 4-additions/index.md §3 (“The R20 rule”)
Why does reflection come before Merkle? 3-world/execution/decision-trail.md §5
What’s the full task lifecycle? 5-time/master-flow.md, 3-world/execution/task-pipeline.md §6
What’s the boot order? 2-plugin/boot.md
What’s the shutdown order? 2-plugin/modes.md
Can I add a skill? 3-world/execution/skill-registry.md §2
What’s a thought record? 3-world/execution/decision-trail.md §1
What’s a Merkle proof? 3-world/physics/laws/proof-store.md §5
Where do I find the glossary? glossary.md
Where do I find the FAQ? reference/glossary.md

8. External references

These are not in docs/, but are part of the Colibri surface:

  • Skills inventory: .agents/skills/ (23 canonical colibri-* skills) — also .claude/skills/ (23 canonical mirrors; no ams-* compat stubs — removed in R75)
  • Memory index: memory/MEMORY.md
  • Claude-Code project rules: CLAUDE.md at repo root
  • Agent-agnostic rules: AGENTS.md at repo root
  • Legacy runtime DB: data/ams.db (AMS donor namespace, kept through R78)

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


Back to top

Colibri — documentation-first MCP runtime. Apache 2.0 + Commons Clause.

This site uses Just the Docs, a documentation theme for Jekyll.