<?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/seeds/seed-m4-doctrine-delivery/">
  <id>https://docs.spec-kitty.ai/plans/charter-resolution/seeds/seed-m4-doctrine-delivery/</id>
  <title>Mission Seed M4 - Deliver Loaded Doctrine to the Agent</title>
  <updated>2026-08-19T00: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/seeds/seed-m4-doctrine-delivery/"/>
  <summary>Specify-intake seed for the mission closing #3489/#3176/#3389: fix silent delivery-table and render no-ops so loaded doctrine reaches the dispatched agent.</summary>
  <content type="html">&lt;h2 id=&quot;mission-seed--m4-deliver-loaded-doctrine-to-the-dispatched-agent&quot;&gt;Mission Seed — M4: Deliver Loaded Doctrine to the Dispatched Agent&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Status:&lt;/strong&gt; seed. Feed to &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.specify&lt;/code&gt; in a fresh session.
&lt;strong&gt;Part of:&lt;/strong&gt; charter-resolution program (see &lt;code dir=&quot;auto&quot;&gt;../program-brief.md&lt;/code&gt;).
&lt;strong&gt;Closes:&lt;/strong&gt; #3489, #3176, #3389, and the render half of #3488.
&lt;strong&gt;Effort:&lt;/strong&gt; M. &lt;strong&gt;Depends on:&lt;/strong&gt; the render/builder parts are independent; the &lt;strong&gt;org-authored&lt;/strong&gt; reach for glossary/op-proc acceptance is &lt;strong&gt;gated on M2&lt;/strong&gt; (the DRG bridge). Land M4’s built-in/project reach first if M2 is not yet in.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id=&quot;problem&quot;&gt;Problem&lt;/h2&gt;
&lt;p&gt;Two delivery pipelines carry doctrine to a dispatched agent — the &lt;strong&gt;action-doctrine bundle&lt;/strong&gt; and the &lt;strong&gt;profile channel&lt;/strong&gt; — and each has silent no-ops. Everything validates clean and warns nothing, yet content never arrives:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;#3489&lt;/strong&gt; — &lt;code dir=&quot;auto&quot;&gt;GLOSSARY_PACK&lt;/code&gt; has &lt;code dir=&quot;auto&quot;&gt;slot=None&lt;/code&gt; in the delivery table (one of two &lt;code dir=&quot;auto&quot;&gt;None&lt;/code&gt; rows lacking the module’s required “stated reason”), and no profile-channel renderer. Glossary packs are diagnostically present but structurally unreachable in every config.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#3488 (render half)&lt;/strong&gt; — styleguide/toolguide reference channels pass &lt;code dir=&quot;auto&quot;&gt;body_fn=None&lt;/code&gt;, so they always emit a fetch pointer, never a budgeted inline body; and procedure step &lt;code dir=&quot;auto&quot;&gt;description&lt;/code&gt; is dead code (&lt;code dir=&quot;auto&quot;&gt;title&lt;/code&gt; is required, so &lt;code dir=&quot;auto&quot;&gt;title or description&lt;/code&gt; never reaches &lt;code dir=&quot;auto&quot;&gt;description&lt;/code&gt; — measured 63% of step content undeliverable).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#3176&lt;/strong&gt; — &lt;code dir=&quot;auto&quot;&gt;build_activation_aware_doctrine_service&lt;/code&gt; derives its project root from three fixed candidates, none of which is &lt;code dir=&quot;auto&quot;&gt;.kittify/agent_profiles&lt;/code&gt;, so a project-overlay profile is silently dropped (three named projection tests are red-carved-out C-002 today).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#3389&lt;/strong&gt; — &lt;code dir=&quot;auto&quot;&gt;charter context --json&lt;/code&gt; omits a &lt;code dir=&quot;auto&quot;&gt;procedures[]&lt;/code&gt; array the text render ships; &lt;code dir=&quot;auto&quot;&gt;procedure&lt;/code&gt; is folded only into the flat &lt;code dir=&quot;auto&quot;&gt;references[]&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;fix-approach-three-groupings&quot;&gt;Fix approach (three groupings)&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;WP-A — delivery-table/render family:&lt;/strong&gt; give &lt;code dir=&quot;auto&quot;&gt;GLOSSARY_PACK&lt;/code&gt; a real slot + term-list render row (or ratify document-only) and &lt;strong&gt;restore the “stated reason” for every remaining &lt;code dir=&quot;auto&quot;&gt;None&lt;/code&gt; row&lt;/strong&gt; (close the class, incl. &lt;code dir=&quot;auto&quot;&gt;ANTI_PATTERN&lt;/code&gt;’s twin); render step &lt;code dir=&quot;auto&quot;&gt;description&lt;/code&gt;; decide styleguide/toolguide inline-body-vs-pointer.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;WP-B — builder overlay seam (#3176):&lt;/strong&gt; thread an optional &lt;code dir=&quot;auto&quot;&gt;agent_profile_overlay_dir&lt;/code&gt; param through &lt;code dir=&quot;auto&quot;&gt;_build_activation_aware_doctrine_service&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;_build_doctrine_service&lt;/code&gt;, default &lt;code dir=&quot;auto&quot;&gt;None&lt;/code&gt; (byte-identical when unset); migrate &lt;code dir=&quot;auto&quot;&gt;default_profile_repository&lt;/code&gt; onto it; delete the composite-key carve-out. &lt;strong&gt;Preserve the single-wrapper-body invariant.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;WP-C — &lt;code dir=&quot;auto&quot;&gt;procedures[]&lt;/code&gt; in context JSON (#3389):&lt;/strong&gt; promote &lt;code dir=&quot;auto&quot;&gt;procedure&lt;/code&gt; from &lt;code dir=&quot;auto&quot;&gt;extra_delivered&lt;/code&gt; to a fifth typed array; &lt;strong&gt;versioned-contract bump&lt;/strong&gt; (increment &lt;code dir=&quot;auto&quot;&gt;context_schema_version&lt;/code&gt; + ledger deliberately).&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;open-operator-decisions-resolve-at-this-missions-discovery&quot;&gt;Open operator decisions (resolve at this mission’s discovery)&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Glossary delivery:&lt;/strong&gt; real delivery slot vs document-only exclusion? If delivered — action-bundle slot, profile channel, or both? inline terms vs surface-list + fetch pointer (token budget)?&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;styleguide/toolguide:&lt;/strong&gt; grant a budgeted inline body, or ratify pointer-only and make it discoverable in schema/docs? (Was pointer-only &lt;em&gt;by design&lt;/em&gt; for the NFR-001 token budget.)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#3389 asset asymmetry:&lt;/strong&gt; after promoting &lt;code dir=&quot;auto&quot;&gt;procedures[]&lt;/code&gt;, is &lt;code dir=&quot;auto&quot;&gt;asset&lt;/code&gt; deliberately reference-only forever, or a follow-up sixth typed array? State it in the contract.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Org acceptance gating:&lt;/strong&gt; require M2 landed for glossary/op-proc &lt;em&gt;org&lt;/em&gt; acceptance, or scope M4’s first pass to built-in/project reach with an org follow-up?&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;scope&quot;&gt;Scope&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;In:&lt;/strong&gt; the delivery-table/render no-ops, the builder overlay seam, the context-JSON &lt;code dir=&quot;auto&quot;&gt;procedures[]&lt;/code&gt; parity.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Out:&lt;/strong&gt; the operating-procedures &lt;em&gt;edge wiring&lt;/em&gt; (that is M3); cascade traversal completeness (M5).&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;key-seams&quot;&gt;Key seams&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;charter/context_renderers/delivery_table.py&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;_ACTION_BUNDLE_DELIVERY_BY_KIND&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;_classify_artifact_urns&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;charter/context_renderers/profile_sections.py&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;format_inline_named_body&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;render_profile_styleguides/toolguides&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;charter/context_renderers/bootstrap_text.py&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;_ACTION_RENDER_ROWS&lt;/code&gt;); &lt;code dir=&quot;auto&quot;&gt;charter/action_doctrine_bundle.py&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;_ActionDoctrineBundle&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;charter/doctrine_service_builder.py&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;_build_doctrine_service&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;_build_activation_aware_doctrine_service&lt;/code&gt;); &lt;code dir=&quot;auto&quot;&gt;charter/_doctrine_paths.py&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;specify_cli/tool_surface/profiles/projection.py&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;charter/progressive_disclosure.py&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;_ARRAY_BY_KIND&lt;/code&gt;); &lt;code dir=&quot;auto&quot;&gt;charter/context.py&lt;/code&gt; (~L487-494)&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;risk&quot;&gt;Risk&lt;/h2&gt;
&lt;p&gt;Widening styleguide/toolguide/glossary bodies can blow the NFR-001 token budget (the reason they were pointer-only). &lt;code dir=&quot;auto&quot;&gt;procedures[]&lt;/code&gt; is a versioned-contract change — bump deliberately. Totality tests redden until slot + render row land together (that is the guard working).&lt;/p&gt;</content>
</entry>
