<?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-m6-project-tier-nodes/">
  <id>https://docs.spec-kitty.ai/plans/charter-resolution/seeds/seed-m6-project-tier-nodes/</id>
  <title>Mission Seed M6 - Project-Tier DRG Node Emission</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-m6-project-tier-nodes/"/>
  <summary>Specify-intake seed for the mission closing #3038: emit hand-authored project-tier agent_profile artefacts as DRG nodes reachable by cascade.</summary>
  <content type="html">&lt;h2 id=&quot;mission-seed--m6-project-tier-drg-node-emission&quot;&gt;Mission Seed — M6: Project-Tier DRG Node Emission&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; #3038 (agent_profile half). &lt;strong&gt;Asset half deferred behind #3037.&lt;/strong&gt;
&lt;strong&gt;Effort:&lt;/strong&gt; L. &lt;strong&gt;Depends on:&lt;/strong&gt; after M1 — reuses the single-authority discipline. Carve-out (separate axis from recursion).&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id=&quot;problem&quot;&gt;Problem&lt;/h2&gt;
&lt;p&gt;The project doctrine tier admits only 3 kinds (directive/tactic/styleguide) as DRG nodes, so a hand-authored project-tier &lt;code dir=&quot;auto&quot;&gt;agent_profile&lt;/code&gt; (or &lt;code dir=&quot;auto&quot;&gt;asset&lt;/code&gt;) &lt;strong&gt;loads and validates but never becomes a DRG node&lt;/strong&gt; — it is invisible to cascade. This is a different axis from the recursion divergence M1 fixes: it is &lt;strong&gt;kind-admission&lt;/strong&gt;, not scanning.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Already landed — do not redo:&lt;/strong&gt; the service/repository half (&lt;code dir=&quot;auto&quot;&gt;PROJECT_KIND_DIRS&lt;/code&gt; is now the single total 12-kind authority in &lt;code dir=&quot;auto&quot;&gt;artifact_kinds.py&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;DoctrineService.assets&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;.agent_profiles&lt;/code&gt; read the project tier). Only the &lt;strong&gt;DRG-node-emission&lt;/strong&gt; half remains open.&lt;/p&gt;
&lt;h2 id=&quot;fix-approach&quot;&gt;Fix approach&lt;/h2&gt;
&lt;p&gt;Emit hand-authored project-tier &lt;code dir=&quot;auto&quot;&gt;agent_profile&lt;/code&gt; artefacts as DRG nodes. The current synthesizer is &lt;strong&gt;answer-driven, not artefact-driven&lt;/strong&gt; — so extending the kind→node-kind map alone reproduces the defect. Needs a &lt;strong&gt;filesystem-walk emission path&lt;/strong&gt; into the project overlay graph, plus the map extension. Convert &lt;code dir=&quot;auto&quot;&gt;project_drg._KIND_TO_NODE_KIND&lt;/code&gt; from &lt;code dir=&quot;auto&quot;&gt;dict[str, NodeKind]&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;ArtifactKind&lt;/code&gt;-keyed so the totality gate (extended in M1) covers it.&lt;/p&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;Node source:&lt;/strong&gt; a new filesystem-walk emitter into the project overlay &lt;code dir=&quot;auto&quot;&gt;graph.yaml&lt;/code&gt;, or is project-tier node presence intended to remain synthesis-answer-driven only? (The issue’s two-map extension is insufficient either way.)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;procedure&lt;/code&gt; at project tier:&lt;/strong&gt; is a project-tier &lt;code dir=&quot;auto&quot;&gt;procedure&lt;/code&gt; supposed to be a DRG node (readable by the loader but not a synthesizer target today)? Deliberate boundary or the same silent gap?&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Asset:&lt;/strong&gt; confirm the asset half stays deferred behind #3037 (asset has no resolution/install path — wiring it as a node yields a half-wired artefact).&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; project-tier &lt;code dir=&quot;auto&quot;&gt;agent_profile&lt;/code&gt; DRG-node emission (filesystem-walk emitter + map extension + enum-keyed map under the gate).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Out:&lt;/strong&gt; asset node emission (behind #3037); the recursion/load-path work (that is M1).&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/synthesizer/project_drg.py&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;_KIND_TO_NODE_KIND&lt;/code&gt; at ~:45 — str-keyed, escapes the totality gate; &lt;code dir=&quot;auto&quot;&gt;_node_kind_for&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;charter/synthesizer/targets.py&lt;/code&gt; (answer-driven target build — the artefact-driven emission gap)&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;doctrine/artifact_kinds.py&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;PROJECT_KIND_DIRS&lt;/code&gt; — already the single authority)&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;note&quot;&gt;Note&lt;/h2&gt;
&lt;p&gt;Cascade only reads project &lt;code dir=&quot;auto&quot;&gt;graph.yaml&lt;/code&gt; / root-level &lt;code dir=&quot;auto&quot;&gt;*.graph.yaml&lt;/code&gt; — so a project-tier node that never reaches &lt;code dir=&quot;auto&quot;&gt;graph.yaml&lt;/code&gt; stays cascade-invisible even after the map extension. The emitter must actually land the node in the graph the cascade walks.&lt;/p&gt;</content>
</entry>
