Skip to content

Charter-Resolution Program

Who is this for (1)

Status (2026-09-30): resumed for 4.x, tracked by #5431 on 4.x Work. No mission in this program has moved since 2026-08-19. Many of the issues it targets have since closed, so the first step is to re-baseline the mission map below. M1 stopped after plan setup (PlanStarted) and M2 after specify (SpecifyStarted); M3–M6 are still seeds. The state column and “ready for /spec-kitty.plan” below are the 2026-08-19 picture.

Authored governance — org-pack and project-tier doctrine — silently fails to reach the dispatched agent. This program closes that class of defect. It rolls up to reach epic #3530 and fail-loud epic #3410.

One meta-cause: the resolution surface restates canonical facts (recursion policy, kind vocab, name-vs-id) instead of deriving them from a single authority, and reads doctrine through a second DRG path that never reaches the consumer — every divergence failing green.

This program repairs current resolution semantics and supplies conformance evidence for the planned charter-service transition; it does not own that architecture. See ADR 2026-10-03-1 and the living C4 model.

See program-brief.md for the full investigation-grounded brief (root causes, WP decomposition, sequencing, risks, and the 10 spec-time operator decisions).

Missions

#MissionClosesStateArtifact
M1Single-Authority Resolution Parity#3490, #3426, #2981spec’dkitty-specs/single-authority-resolution-parity-01M0CEBQ/
M2DRG Read-Path Bridge#3572, #3573spec’dkitty-specs/drg-read-path-bridge-01M0CHVZ/
M3Operating-Procedures Validate→Triage→Data-Drive#2994, #3352, #3488(edges)seedseeds/seed-m3-operating-procedures.md
M4Deliver Loaded Doctrine to the Agent#3489, #3176, #3389, #3488(render)seedseeds/seed-m4-doctrine-delivery.md
M5Kind-Complete Cascade + Orphan Wiring#2829, #3009 residualseedseeds/seed-m5-kind-complete-cascade.md
M6Project-Tier DRG Node Emission#3038seedseeds/seed-m6-project-tier-nodes.md

Sequencing

M1 ─┐ (enabling; no golden ripple) M1 ─► M6 (carve-out; kind-admission)
M2 ─┼─► M3 ─► M4(org reach)
└─► M4(render/builder) ───►
M5 (LAST — re-ledgers golden counts once, atop M2)
  • M1 ∥ M2 are the enabling fixes — full specs, ready for /spec-kitty.plan.
  • M3–M6 are seeds — each future session runs /spec-kitty.specify from its seed, making that mission’s operator decisions with fresh context (they depend on enabling-mission outcomes).

How to run a mission (fresh session)

  • M1 / M2 (already spec’d): /spec-kitty.plan for the mission, then /spec-kitty.tasks, then spec-kitty next.
  • M3–M6 (seeds): open the seed, run /spec-kitty.specify with it as intake, resolve the seed’s open decisions, then plan→tasks→implement.