holocron/docs/issues/0011-governance-reference-doc-updates.md

0011 — Governance reference doc updates ✅

What to build

Four targeted updates to existing reference documents to reflect the governance layer's existence. All four are small edits; they are bundled because they share the same dependency (governance.md must exist first) and the same purpose (keeping reference documents accurate).

1. docs/VISION.md

Add governance as a named capability in the Goals section. The current goals list (single source of truth, provider-agnostic core, layered override model, pull-based distribution, graceful scaling) does not mention governance. Add it.

In the architecture section, note that core/instructions/governance.md is part of the content model — the always-on governance layer loaded via @import rather than on-demand.

2. docs/ROADMAP.md

Add a Governance workstream entry to the roadmap. The workstream has two phases:

• Phase 1 (before Chunk 3): instruction and documentation layer — complete when issues 0009–0012 are done
• Phase 2 (Chunk 6): deterministic enforcement layer — CONTROLS.md in docs/research/governance_principles/ is the spec

Close the "CLAUDE.md always-on refinement" entry in the open questions table — this workstream resolves it. Update the table row to mark it resolved with a reference to the governance workstream.

3. Repo CLAUDE.md

Add the Governance workstream to the Key documents section so future Claude sessions working in this repo know it exists. Add a note to the Key rules section that governance constraints (from core/instructions/governance.md) apply when building content in this repo.

4. core/instructions/coding.md

Review coding.md against governance.md. If any security or credential-related rules are found in coding.md that duplicate governance content, remove the duplicates and replace them with a pointer to governance.md. Duplicate rules across two files create a drift risk. If no overlap is found, no change is needed.

Acceptance criteria

• docs/VISION.md Goals section names governance as a repo capability
• docs/VISION.md architecture section references core/instructions/governance.md and the @import loading mechanism
• docs/ROADMAP.md includes a Governance workstream entry with Phase 1 and Phase 2 described
• docs/ROADMAP.md open questions table marks "CLAUDE.md always-on refinement" as resolved
• Repo CLAUDE.md Key documents section references the governance workstream
• Repo CLAUDE.md Key rules section notes that governance constraints apply when building content
• core/instructions/coding.md has been reviewed — any duplicated governance content removed or redirected (no overlap found)

Blocked by

• 0009 — governance.md must exist before reference documents can accurately describe it