Kit Reference

One page per kit. Each page orients and sequences; it owns no contract — the contract lives in the kit that enforces it, and the page cites downward.

The kits

Read in this order: each kit assumes the machinery of the ones above it.

• gate-sdk — the lint framework the other kits register into.
• lifecycle-kit — the iteration stage state machine for stateless sessions.
• queue-kit — the git-native, agent-readable task tracker.
• canon-kit — spec discipline for agent-authored components.
• guard-kit — permission-friction tooling for agent sessions.
• delegation-kit — safe delegated-agent execution under a token budget.
• context-kit — token-economics-aware context management.
• drift-kit — advisory drift reporting across the governed surfaces.
• evidence-kit — a held-constant test baseline and a committed per-run evidence manifest.
• site-kit — deployment-truth governance for a repo-served docs site: a CNAME-host parity gate, a rendered-page fidelity gate, and a live-site monitor template.
• doctrine-kit — the experience-packaging rung: the cross-kit delivery doctrine, referenced by link into a consumer’s always-loaded agent file.

The walkthrough and evidence pages join this map when their kits land.