governance plans¶

Plans for cross-cutting governance concerns that don't fit one product plane. These are the rules-of-the-road for the platform itself.

What classifies here¶

Markdown lifecycle policy (where docs are durable, where they archive, how staleness is detected)
File-taxonomy standardization (which directories own which content classes)
Repo-ownership models and separation-of-duties enforcement
Auth-control-plane policy (1Password wrapper standards, approved refs catalog, forbidden patterns)
Failure-prevention rules (e.g. destructive-op authorization model, conflicting-instruction precedence)
Lifecycle policies (when content is constitution vs memory vs context)
Naming conventions and metadata contracts
Cross-cutting compliance frameworks (SOC2, NIST, EU AI Act mappings at the platform level — not per-policy)

Out of scope¶

Cedar policy bodies → worktrees/cedar-policies/ (those are the executable artifacts; this subdir holds the plans for changing them)
Product-specific plans → ../{openclaw-control-plane,gascity-blu-realignment,contractplane,contextcontrol}/
Migration plans → ../migration/

Naming¶

YYYY-MM-DD__domain__subject__state.md

Examples:

2026-05-11__governance__markdown-lifecycle-policy__draft.md
2026-05-11__governance__destructive-op-authorization-model__accepted.md
2026-05-11__governance__auth-control-plane__implemented.md

Lifecycle¶

Governance plans that reach accepted or implemented state are typically promoted into binding documents at the workspace level (.agents/context/BLU-*.md, root CLAUDE.md, AGENTS.md, etc.) — the plan source stays here for provenance with state: implemented and implementation_ref pointing to the binding doc. Then they move to ../archive/.

Rejected plans archive immediately with state: rejected and a reason field.

Required metadata per plan¶

Same frontmatter shape as ../openclaw-control-plane/README.md.

This subdir is one of the seven canonical plans buckets under PLATFORM-Context/plans/.