<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/plans/charter-resolution/">
  <id>https://docs.spec-kitty.ai/plans/charter-resolution/</id>
  <title>Charter-Resolution Program</title>
  <updated>2026-10-03T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/plans/charter-resolution/"/>
  <summary>Program overview, mission map (M1-M6) and run instructions for the charter-resolution defect cluster: org/project doctrine that loads healthy but reaches no consumer.</summary>
  <content type="html">&lt;span id=&quot;charter-resolution-program&quot;&gt;&lt;/span&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Status (2026-09-30): resumed for 4.x, tracked by #5431 on 4.x Work.&lt;/strong&gt; 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
(&lt;code dir=&quot;auto&quot;&gt;PlanStarted&lt;/code&gt;) and M2 after specify (&lt;code dir=&quot;auto&quot;&gt;SpecifyStarted&lt;/code&gt;); M3–M6 are still seeds. The state
column and “ready for &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.plan&lt;/code&gt;” below are the 2026-08-19 picture.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;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 &lt;strong&gt;#3530&lt;/strong&gt; and fail-loud epic &lt;strong&gt;#3410&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;One meta-cause:&lt;/strong&gt; 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.&lt;/p&gt;
&lt;p&gt;This program repairs current resolution semantics and supplies conformance
evidence for the planned charter-service transition; it does not own that
architecture. See &lt;a href=&quot;/adr/4.x/2026-10-03-1-charter-read-write-service-strangler/&quot;&gt;ADR 2026-10-03-1&lt;/a&gt;
and the &lt;a href=&quot;/architecture/diagrams/&quot;&gt;living C4 model&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;See &lt;a href=&quot;/plans/charter-resolution/program-brief/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;program-brief.md&lt;/code&gt;&lt;/a&gt; for the full investigation-grounded brief (root causes, WP decomposition, sequencing, risks, and the 10 spec-time operator decisions).&lt;/p&gt;
&lt;h2 id=&quot;missions&quot;&gt;Missions&lt;/h2&gt;






















































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;#&lt;/th&gt;&lt;th&gt;Mission&lt;/th&gt;&lt;th&gt;Closes&lt;/th&gt;&lt;th&gt;State&lt;/th&gt;&lt;th&gt;Artifact&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;M1&lt;/td&gt;&lt;td&gt;Single-Authority Resolution Parity&lt;/td&gt;&lt;td&gt;#3490, #3426, #2981&lt;/td&gt;&lt;td&gt;&lt;strong&gt;spec’d&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;kitty-specs/single-authority-resolution-parity-01M0CEBQ/&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;M2&lt;/td&gt;&lt;td&gt;DRG Read-Path Bridge&lt;/td&gt;&lt;td&gt;#3572, #3573&lt;/td&gt;&lt;td&gt;&lt;strong&gt;spec’d&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;kitty-specs/drg-read-path-bridge-01M0CHVZ/&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;M3&lt;/td&gt;&lt;td&gt;Operating-Procedures Validate→Triage→Data-Drive&lt;/td&gt;&lt;td&gt;#2994, #3352, #3488(edges)&lt;/td&gt;&lt;td&gt;seed&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;/plans/charter-resolution/seeds/seed-m3-operating-procedures/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;seeds/seed-m3-operating-procedures.md&lt;/code&gt;&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;M4&lt;/td&gt;&lt;td&gt;Deliver Loaded Doctrine to the Agent&lt;/td&gt;&lt;td&gt;#3489, #3176, #3389, #3488(render)&lt;/td&gt;&lt;td&gt;seed&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;/plans/charter-resolution/seeds/seed-m4-doctrine-delivery/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;seeds/seed-m4-doctrine-delivery.md&lt;/code&gt;&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;M5&lt;/td&gt;&lt;td&gt;Kind-Complete Cascade + Orphan Wiring&lt;/td&gt;&lt;td&gt;#2829, #3009 residual&lt;/td&gt;&lt;td&gt;seed&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;/plans/charter-resolution/seeds/seed-m5-kind-complete-cascade/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;seeds/seed-m5-kind-complete-cascade.md&lt;/code&gt;&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;M6&lt;/td&gt;&lt;td&gt;Project-Tier DRG Node Emission&lt;/td&gt;&lt;td&gt;#3038&lt;/td&gt;&lt;td&gt;seed&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;/plans/charter-resolution/seeds/seed-m6-project-tier-nodes/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;seeds/seed-m6-project-tier-nodes.md&lt;/code&gt;&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;h2 id=&quot;sequencing&quot;&gt;Sequencing&lt;/h2&gt;
&lt;div class=&quot;expressive-code&quot;&gt;&lt;figure class=&quot;frame not-content&quot;&gt;&lt;figcaption class=&quot;header&quot;&gt;&lt;/figcaption&gt;&lt;pre data-language=&quot;plaintext&quot;&gt;&lt;code&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;M1 ─┐   (enabling; no golden ripple)          M1 ─► M6   (carve-out; kind-admission)&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;M2 ─┼─► M3 ─► M4(org reach)&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;    &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;└─► M4(render/builder) ───►&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;                          &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;M5   (LAST — re-ledgers golden counts once, atop M2)&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;M1 ∥ M2&lt;/strong&gt; are the enabling fixes — full specs, ready for &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.plan&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;M3–M6&lt;/strong&gt; are seeds — each future session runs &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.specify&lt;/code&gt; from its seed, making that mission’s operator decisions with fresh context (they depend on enabling-mission outcomes).&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;how-to-run-a-mission-fresh-session&quot;&gt;How to run a mission (fresh session)&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;M1 / M2 (already spec’d):&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.plan&lt;/code&gt; for the mission, then &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.tasks&lt;/code&gt;, then &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;M3–M6 (seeds):&lt;/strong&gt; open the seed, run &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.specify&lt;/code&gt; with it as intake, resolve the seed’s open decisions, then plan→tasks→implement.&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
