<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/architecture/charter-synthesis-drg/">
  <id>https://docs.spec-kitty.ai/architecture/charter-synthesis-drg/</id>
  <title>Understanding Charter: Synthesis, DRG, and Governed Context</title>
  <updated>2026-10-08T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/architecture/charter-synthesis-drg/"/>
  <summary>How charter synthesize works, what the DRG is, how governed context flows to agents, the shipped-graph orphan residual, and known limitations.</summary>
  <content type="html">&lt;span id=&quot;understanding-charter-synthesis-drg-and-governed-context&quot;&gt;&lt;/span&gt;
&lt;p&gt;This document explains the Charter synthesis model and the DRG-backed context system. For a
practical walkthrough, see &lt;a href=&quot;/context/charter-overview/&quot;&gt;How Charter Works&lt;/a&gt;. For step-by-step
how-to instructions, see &lt;a href=&quot;/guides/how-to/governance/synthesize-doctrine/&quot;&gt;How to Synthesize and Maintain Doctrine&lt;/a&gt;.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;what-the-charter-bundle-is&quot;&gt;What the charter bundle is&lt;/h2&gt;
&lt;p&gt;The &lt;strong&gt;charter bundle&lt;/strong&gt; is the machine-readable synthesis of your &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt; governance document.
It is not a simple copy of the prose — it is a structured set of YAML artifacts that the runtime
can traverse, merge, and inject as context for specific workflow actions.&lt;/p&gt;
&lt;p&gt;The core bundle lives in &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/&lt;/code&gt; and consists of:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;governance.yaml&lt;/code&gt; — testing, quality, performance, branch, and doctrine-selection config&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;directives.yaml&lt;/code&gt; — extracted directive list with IDs, descriptions, and severity&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;metadata.yaml&lt;/code&gt; — bundle metadata: charter hash, last-sync timestamp, provenance&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;references.yaml&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;context-state.json&lt;/code&gt;, synthesis manifests, and provenance sidecars are also
Charter-era files, but they are outside the narrow CharterBundleManifest v1.0.0 core scope.&lt;/p&gt;
&lt;p&gt;Why is the bundle needed rather than raw prose? Because the runtime context injection requires a
structured artifact. When &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; prepares a prompt for the &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; action, it
needs to select the directives that apply specifically to &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; (not to &lt;code dir=&quot;auto&quot;&gt;specify&lt;/code&gt; or
&lt;code dir=&quot;auto&quot;&gt;review&lt;/code&gt;). A flat prose document cannot serve that purpose efficiently. The bundle provides the
structure for action-scoped context injection.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;how-synthesis-works&quot;&gt;How synthesis works&lt;/h2&gt;
&lt;p&gt;The synthesis pipeline has four logical phases:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Parse&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt; reads &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt; and the interview answers. It also reads any
agent-generated YAML from &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/generated/&lt;/code&gt; (artifacts the LLM harness has written).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;DRG edge computation&lt;/strong&gt;: The synthesizer constructs the Directive Relationship Graph (DRG) by
resolving typed relationships between actions, directives, tactics, procedures, profiles,
templates, and glossary terms.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Directive resolution&lt;/strong&gt;: With the DRG computed, the synthesizer determines which artifacts
need to be generated or updated. Artifacts whose provenance points to unchanged inputs are
left intact (this is what makes &lt;code dir=&quot;auto&quot;&gt;charter resynthesize --topic &amp;#x3C;selector&gt;&lt;/code&gt; work — only affected
artifacts are regenerated).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Promote artifacts&lt;/strong&gt;: The synthesizer writes resolved artifacts to &lt;code dir=&quot;auto&quot;&gt;.kittify/charter-packs/&lt;/code&gt;
(project-local doctrine) and records synthesis state under &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/&lt;/code&gt;. The &lt;code dir=&quot;auto&quot;&gt;--dry-run&lt;/code&gt;
flag stops after validation, before promotion.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;The authoritative file throughout is always &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt;. The synthesizer reads it; it does not
write to it. Doctrine artifacts are outputs, not inputs.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;drg-edge-computation&quot;&gt;DRG edge computation&lt;/h2&gt;
&lt;p&gt;The &lt;strong&gt;Directive Relationship Graph (DRG)&lt;/strong&gt; is a directed graph with typed nodes such as actions,
directives, tactics, procedures, profiles, templates, and glossary terms. Edges use these
relations:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;scope&lt;/code&gt;: action-to-artifact scoping&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt;: hard dependencies between artifacts&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;: softer recommendations traversed to a bounded depth&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;vocabulary&lt;/code&gt;: links from resolved artifacts to glossary scope/term context&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;instantiates&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;replaces&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;delegates_to&lt;/code&gt;: additional graph relations used by specific
doctrine surfaces&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;When the runtime prepares context for a specific mission action (e.g., &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt;), it traverses
the DRG from the action’s entry node. It follows &lt;code dir=&quot;auto&quot;&gt;scope&lt;/code&gt; edges first, then transitive &lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt;
edges, bounded-depth &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; edges, and one-hop &lt;code dir=&quot;auto&quot;&gt;vocabulary&lt;/code&gt; edges from the resolved nodes.
That keeps implementation prompts focused on implementation-relevant doctrine instead of
specification-phase concerns.&lt;/p&gt;
&lt;p&gt;The DRG is not stored as a standalone file that you can inspect directly. It is computed by the
synthesizer and manifests as the structured content of the bundle artifacts.&lt;/p&gt;
&lt;h3 id=&quot;mission-type-governance-grains&quot;&gt;Mission-type governance grains&lt;/h3&gt;
&lt;p&gt;Per-mission-type governance also resolves &lt;em&gt;through&lt;/em&gt; the charter layer, keyed off the
&lt;code dir=&quot;auto&quot;&gt;mission_type&lt;/code&gt; recorded in a mission’s &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; — never inferred from
&lt;code dir=&quot;auto&quot;&gt;template_set&lt;/code&gt; and never defaulted to &lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt;. It is authored at two grains
that the resolver unions and de-dupes: an &lt;strong&gt;action-grain&lt;/strong&gt; source
(&lt;code dir=&quot;auto&quot;&gt;missions/&amp;#x3C;type&gt;/actions/&amp;#x3C;action&gt;/index.yaml&lt;/code&gt;, which generates the DRG &lt;code dir=&quot;auto&quot;&gt;scope&lt;/code&gt;
edges described above) and a &lt;strong&gt;type-grain&lt;/strong&gt; source
(&lt;code dir=&quot;auto&quot;&gt;missions/&amp;#x3C;type&gt;/governance-profile.yaml&lt;/code&gt;), which is also the project-override
target. A full explanation of that seam — the reserved slots for templates and
gates, the per-type override, and the leak-closure invariant — lives in
&lt;a href=&quot;/architecture/mission-type-resolution/&quot;&gt;Mission-Type Resolution&lt;/a&gt;.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;bootstrap-vs-compact-context&quot;&gt;Bootstrap vs compact context&lt;/h2&gt;
&lt;p&gt;The DRG traversal for a given action can produce large payloads for complex governance structures.
Two modes handle this:&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Bootstrap mode&lt;/strong&gt;: On the first load for an action (or after a fresh synthesis), the full
relevant DRG subgraph is injected into the governed profile invocation. The agent sees all
applicable directives, tactics, and glossary terms for its current action, plus the full doctrine
library references.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Compact-context mode&lt;/strong&gt;: When the DRG context payload exceeds the size threshold for inclusion,
the runtime falls back to compact-context mode. In this mode, the agent receives only the resolved
paradigm list, directive list, and tool list — without the full doctrine library text. This is a
known limitation (see issue #787 in the project issue tracker; check that issue for current
resolution status). Do not assume full-context behavior unconditionally on large governance layers.&lt;/p&gt;
&lt;p&gt;First-load state is tracked per action in &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/context-state.json&lt;/code&gt;. Each action
(specify, plan, implement, review) has an independent first-load timestamp.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;why-the-authoritative-vs-generated-distinction-matters&quot;&gt;Why the authoritative vs generated distinction matters&lt;/h2&gt;
&lt;p&gt;Charter governance is built on a strict read/write boundary:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Authoritative policy source&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/charter.md&lt;/code&gt; — human-edited, the source of
truth for project governance policy.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Derived config and runtime state&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;governance.yaml&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;directives.yaml&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;metadata.yaml&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;references.yaml&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;context-state.json&lt;/code&gt;, synthesis manifests, and provenance sidecars — owned
by their respective CLI commands.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Project layer&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;.kittify/charter-packs/&lt;/code&gt; — promoted by &lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt; and
read alongside the built-in Charter Pack.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Agent-generated synthesis input&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/generated/&lt;/code&gt; — written by the harness and
validated by &lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If you edit a derived file (for example, add a directive to &lt;code dir=&quot;auto&quot;&gt;governance.yaml&lt;/code&gt; directly), the edit
can be lost on the next &lt;code dir=&quot;auto&quot;&gt;charter generate&lt;/code&gt; run because those files are
re-derived from &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt;. There is no merge step for derived config.&lt;/p&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;charter status&lt;/code&gt; detects drift between &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt; and the bundle hash. &lt;code dir=&quot;auto&quot;&gt;charter lint&lt;/code&gt; detects
decay within the DRG (orphaned artifacts, contradictions, staleness). Both tools exist precisely
because the authoritative/generated boundary creates a risk of divergence if synthesis is not run
after charter edits.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;known-limitations&quot;&gt;Known limitations&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Compact-context mode (issue #787)&lt;/strong&gt;: Large governance layers may trigger compact-context
fallback, causing agents to receive summarized rather than full doctrine context. The workaround
is to reduce governance scope or break the project into smaller governance domains.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Fresh-project synthesis&lt;/strong&gt;: On a project where &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/generated/&lt;/code&gt; is missing or
empty (no agent-generated artifacts), &lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt; produces only the minimal artifact
set (directory marker and PROVENANCE.md). The runtime falls back to the built-in Charter Pack until a
full synthesis run with agent-generated content completes.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Synthesis requires &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt;&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt; will exit non-zero if &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt;
does not exist. Run &lt;code dir=&quot;auto&quot;&gt;charter interview&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;charter generate&lt;/code&gt; first.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;hr&gt;
&lt;h2 id=&quot;the-shipped-graph-orphan-residual-current-state&quot;&gt;The shipped-graph orphan residual (current state)&lt;/h2&gt;
&lt;p&gt;An &lt;strong&gt;orphan&lt;/strong&gt; is a DRG node with no inbound and no outbound edge. Some orphans are intentional —
a deliberately authored artifact with no single natural referent, or a structural node that is
resolved by lookup rather than by traversal. Doctrine forbids deleting such an artifact or
manufacturing an edge to zero the metric (D-C2 / C-003): every orphan is either &lt;strong&gt;wired&lt;/strong&gt; to a real
referent or &lt;strong&gt;recorded here&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;This section is the live, current-state record. It is bound to the measurement by
&lt;code dir=&quot;auto&quot;&gt;test_documented_residual_matches_measured_shipped_orphans&lt;/code&gt; in
&lt;code dir=&quot;auto&quot;&gt;tests/specify_cli/cli/commands/test_doctrine_regenerate_graph.py&lt;/code&gt;: the URNs in the block below must
equal the shipped graph’s orphans exactly, so an unrecorded new orphan, or a recorded one that has
since been wired, fails a test rather than passing as prose drift.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;How to recompute it&lt;/strong&gt; — never copy the list from prose:&lt;/p&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;python&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:#C792EA;--1:#8844AE&quot;&gt;from&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; charter.offering.drg.loader &lt;/span&gt;&lt;span style=&quot;--0:#C792EA;--1:#8844AE&quot;&gt;import&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; load_built_in_graph&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;/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;g &lt;/span&gt;&lt;span style=&quot;--0:#C792EA;--1:#8844AE&quot;&gt;=&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#B2CCD6;--1:#096E72&quot;&gt;load_built_in_graph&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;()&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;incident &lt;/span&gt;&lt;span style=&quot;--0:#C792EA;--1:#8844AE&quot;&gt;=&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; {u &lt;/span&gt;&lt;span style=&quot;--0:#C792EA;--1:#8844AE&quot;&gt;for&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; e &lt;/span&gt;&lt;span style=&quot;--0:#C792EA;--1:#8844AE&quot;&gt;in&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; g.edges &lt;/span&gt;&lt;span style=&quot;--0:#C792EA;--1:#8844AE&quot;&gt;for&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; u &lt;/span&gt;&lt;span style=&quot;--0:#C792EA;--1:#8844AE&quot;&gt;in&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; (e.source, e.target)}&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;orphans &lt;/span&gt;&lt;span style=&quot;--0:#C792EA;--1:#8844AE&quot;&gt;=&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#C5E478;--1:#3B61B0&quot;&gt;sorted&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;(&lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;{n.urn &lt;/span&gt;&lt;span style=&quot;--0:#C792EA;--1:#8844AE&quot;&gt;for&lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt; n &lt;/span&gt;&lt;span style=&quot;--0:#C792EA;--1:#8844AE&quot;&gt;in&lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt; g.nodes} &lt;/span&gt;&lt;span style=&quot;--0:#C792EA;--1:#8844AE&quot;&gt;-&lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt; incident&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;)&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:#C5E478;--1:#3B61B0&quot;&gt;print&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;(&lt;/span&gt;&lt;span style=&quot;--0:#C5E478;--1:#3B61B0&quot;&gt;len&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;(&lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;orphans&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;))&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:#C5E478;--1:#3B61B0&quot;&gt;print&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;(&lt;/span&gt;&lt;span style=&quot;--0:#7FDBCA;--1:#096E72&quot;&gt;*&lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;orphans&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;,&lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#D7DBE0;--1:#403F53&quot;&gt;sep&lt;/span&gt;&lt;span style=&quot;--0:#C792EA;--1:#8844AE&quot;&gt;=&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#F78C6C;--1:#AA0982&quot;&gt;\n&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;)  &lt;/span&gt;&lt;span style=&quot;--0:#919F9F;--1:#5F636F&quot;&gt;# the membership the block below must equal&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;p&gt;&lt;strong&gt;Current state:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;mission_step_contract:documentation/accept&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;mission_step_contract:documentation/audit&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;mission_step_contract:documentation/design&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;mission_step_contract:documentation/discover&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;mission_step_contract:documentation/generate&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;mission_step_contract:documentation/publish&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;mission_step_contract:documentation/validate&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;mission_step_contract:plan/plan&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;mission_step_contract:plan/research&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;mission_step_contract:plan/review&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;mission_step_contract:plan/specify&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;mission_step_contract:research/gathering&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;mission_step_contract:research/methodology&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;mission_step_contract:research/output&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;mission_step_contract:research/scoping&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;mission_step_contract:research/synthesis&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;mission_step_contract:software-dev/implement&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;mission_step_contract:software-dev/plan&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;mission_step_contract:software-dev/review&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;mission_step_contract:software-dev/specify&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;mission_step_contract:software-dev/tasks&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;glossary_pack:spec-kitty-core&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;agent_profile:human-in-charge&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;styleguide:deployable-skill-authoring&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;toolguide:powershell-syntax&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&quot;why-each-group-is-residual&quot;&gt;Why each group is residual&lt;/h3&gt;



































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Group&lt;/th&gt;&lt;th&gt;Count&lt;/th&gt;&lt;th&gt;Disposition&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;mission_step_contract:&amp;#x3C;mission&gt;/&amp;#x3C;action&gt;&lt;/code&gt;&lt;/td&gt;&lt;td&gt;21&lt;/td&gt;&lt;td&gt;&lt;strong&gt;Edge-less by construction.&lt;/strong&gt; The step-contract fragment ships &lt;code dir=&quot;auto&quot;&gt;edges: []&lt;/code&gt;; the activation engine resolves a contract by URN lookup on the &lt;code dir=&quot;auto&quot;&gt;(mission_type, action)&lt;/code&gt; join, never by traversal. Deleting or edging them to shrink the metric is what D-C2 / C-003 forbid. The 21 are the 17 shipped by &lt;code dir=&quot;auto&quot;&gt;doctrine-controlled-transition-gates&lt;/code&gt; (7 documentation + 5 research + 5 software-dev) plus the 4 &lt;code dir=&quot;auto&quot;&gt;plan/*&lt;/code&gt; contracts vendored by #6379. Membership is pinned as &lt;code dir=&quot;auto&quot;&gt;_EDGELESS_BY_CONSTRUCTION&lt;/code&gt;.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;glossary_pack:spec-kitty-core&lt;/code&gt;&lt;/td&gt;&lt;td&gt;1&lt;/td&gt;&lt;td&gt;&lt;strong&gt;Awaiting references.&lt;/strong&gt; The pack node ships with zero outbound references; its enforcement fields stay inert until a follow-up mission gives it a real referent. Inventing one now would be a guessed edge. Pinned in &lt;code dir=&quot;auto&quot;&gt;_AWAITING_REFERENCES&lt;/code&gt;.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;agent_profile:human-in-charge&lt;/code&gt;&lt;/td&gt;&lt;td&gt;1&lt;/td&gt;&lt;td&gt;&lt;strong&gt;Runtime-assignment sentinel.&lt;/strong&gt; Signalled by assigning a work package to a human at runtime, never by a static doctrine edge.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;styleguide:deployable-skill-authoring&lt;/code&gt;&lt;/td&gt;&lt;td&gt;1&lt;/td&gt;&lt;td&gt;&lt;strong&gt;Direct-activation-only.&lt;/strong&gt; Reached by &lt;code dir=&quot;auto&quot;&gt;charter activate styleguide deployable-skill-authoring&lt;/code&gt;; no defensible source artifact exists to carry an inbound edge (a guessed one is refused, C-003). Pinned in &lt;code dir=&quot;auto&quot;&gt;_DIRECT_ACTIVATION_ONLY&lt;/code&gt;.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;toolguide:powershell-syntax&lt;/code&gt;&lt;/td&gt;&lt;td&gt;1&lt;/td&gt;&lt;td&gt;&lt;strong&gt;Runtime tooling.&lt;/strong&gt; Real PowerShell-authoring content consumed by agents at runtime; no built-in artifact cites it. Admitted by PR #2936.&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;h3 id=&quot;ceiling-history&quot;&gt;Ceiling history&lt;/h3&gt;
&lt;p&gt;There is no numeric ceiling any more: the membership block above, checked for equality against the
measured shipped orphans, is the only guard (a ceiling could not see a shrink or a silent raise). The
history of the retired ceiling, so the old numbers are never bare:&lt;/p&gt;





































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Ceiling&lt;/th&gt;&lt;th&gt;Cause&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;14&lt;/td&gt;&lt;td&gt;Post-WP05 curated baseline (9 Fowler tactics wired, 12 orphans wired).&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;18 -&gt; 14&lt;/td&gt;&lt;td&gt;A stopgap raise for 8 structural mission-type nodes, reverted once &lt;code dir=&quot;auto&quot;&gt;mission-type-drg-edges&lt;/code&gt; (#2677) emitted the &lt;code dir=&quot;auto&quot;&gt;mission_type -&gt; action&lt;/code&gt; edges.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;29&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;doctrine-controlled-transition-gates&lt;/code&gt; (epic #2535 half A) shipped 17 edge-less step contracts.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;30&lt;/td&gt;&lt;td&gt;PR #2936 promoted &lt;code dir=&quot;auto&quot;&gt;toolguide:powershell-syntax&lt;/code&gt; from a dead file to a live, edge-less node.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;30 -&gt; 21&lt;/td&gt;&lt;td&gt;Ratcheted after both #3007 residuals were retired/wired and six other artifacts were wired; a ceiling cannot see a shrink, so it was ratcheted rather than left with nine points of silent slack.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;22 -&gt; 21&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;charter-delivery-finish-context-degod&lt;/code&gt; (#3064) relocated &lt;code dir=&quot;auto&quot;&gt;asset:common-charter-scaffold-minimal&lt;/code&gt; to charter-pack status, removing the node.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;21 -&gt; 25&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The built-in pin bump of PR #6379 vendored the plan mission’s four step contracts (#6432), which are edge-less by construction like the other 17. No edge was wired; &lt;code dir=&quot;auto&quot;&gt;packs/built-in/&lt;/code&gt; was untouched. Recorded by mission &lt;code dir=&quot;auto&quot;&gt;charter-synthesis-graph-and-languages-01M59RZ5&lt;/code&gt;, and the live record above was added under #6513 so the raise has a writable home.&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;h3 id=&quot;where-the-older-records-live&quot;&gt;Where the older records live&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;kitty-specs/mission-lifecycle-dispatch-drg-closeout-01KV0S99/drg-orphan-residual.md&lt;/code&gt; is the
canonical &lt;strong&gt;historical&lt;/strong&gt; record (WP05, #1923). It sits under &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt;, an immutable archive
root (&lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_archive_root_byte_identical.py&lt;/code&gt;), so it is &lt;strong&gt;frozen&lt;/strong&gt;: cite it for
the curation narrative of its date, never edit it, and do not read its last ceiling (29 -&gt; 30 over
17 step contracts) as current state.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;_INTENTIONAL_ORPHANS&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;_SHIPPED_ORPHANS&lt;/code&gt; in
&lt;code dir=&quot;auto&quot;&gt;tests/charter_offering/drg/migration/test_extractor_projection.py&lt;/code&gt; are the &lt;strong&gt;pure-extractor frame&lt;/strong&gt;
membership pins. This page records the &lt;strong&gt;shipped&lt;/strong&gt; frame (&lt;code dir=&quot;auto&quot;&gt;load_built_in_graph()&lt;/code&gt;), which is the
frame the membership guard measures; the two differ only by &lt;code dir=&quot;auto&quot;&gt;_ORPHANS_RESOLVED_BY_OVERLAY&lt;/code&gt;, so neither may
be “corrected” against the other.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tests/charter_offering/drg/test_reachability.py&lt;/code&gt; pins the companion &lt;strong&gt;reachability&lt;/strong&gt; measure
(action-unreachable vs profile-delivered), which is a different question from incidence: a node
can be edge-incident and still unreachable from any action.&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;h2 id=&quot;see-also&quot;&gt;See Also&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;/context/charter-overview/&quot;&gt;How Charter Works&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/context/governance-files/&quot;&gt;Governance Files Reference&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/guides/how-to/governance/synthesize-doctrine/&quot;&gt;How to Synthesize and Maintain Doctrine&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/guides/how-to/governance/troubleshoot-charter/&quot;&gt;Troubleshooting Charter Failures&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
