001-governed-harness
The governed harness (spec-spine self-governance and the session kit)
Lifecycle approvedImplementation completeVerification unknownQualification unknown
This repository's own governance surface: the spec-spine gate chain, the committed .derived shard trees it compares against, the merge driver that keeps those shards mergeable, and the Claude Code session kit that constrains what an agent may do here. Spec 000 governs what the crate emits; this spec governs what the repository does to keep 000 honest. It exists because 000 section 4 became a normative cross-language contract while nothing mechanically checked that the corpus stating it stayed coherent with the code implementing it.
Read the full pinned specification ↗Relationships
depends on
Claimed units
- establishes
{ "kind": "file", "path": ".github/CODEOWNERS" } - establishes
{ "kind": "file", "path": ".github/workflows/statecraft-ai-review.yml" } - establishes
{ "kind": "file", "path": ".github/workflows/statecraft-ci.yml" } - establishes
{ "kind": "directory", "path": ".statecraft/" } - establishes
{ "kind": "directory", "path": "scripts/statecraft/" } - establishes
{ "kind": "file", "path": "Makefile" } - establishes
{ "kind": "file", "path": "AGENTS.md" } - establishes
{ "kind": "file", "path": "CLAUDE.md" } - establishes
{ "kind": "file", "path": ".mcp.json" } - establishes
{ "kind": "file", "path": "spec-spine.toml" } - establishes
{ "kind": "file", "path": ".gitattributes" } - establishes
{ "kind": "file", "path": ".claude/settings.json" } - establishes
{ "kind": "directory", "path": ".claude/skills/" } - establishes
{ "kind": "directory", "path": ".claude/agents/" } - establishes
{ "kind": "directory", "path": ".claude/rules/" } - establishes
{ "kind": "directory", "path": ".githooks/" } - establishes
{ "kind": "directory", "path": "standards/spec/" } - establishes
{ "kind": "file", "path": ".github/workflows/govern.yml" } - establishes
{ "kind": "file", "path": ".github/workflows/ci.yml" }
Source headings
- 001: The governed harness
- 1. Purpose
- 2. Territory
- 3. Behavior
- 4. Out of scope
- 5. Verification
- 6. Resolved decisions
- Managed governance enrollment (2026-10-02)
- Managed governance refresh (2026-10-02)
Frozen anchors
No frozen anchors declared.