<?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-m5-kind-complete-cascade/">
  <id>https://docs.spec-kitty.ai/plans/charter-resolution/seeds/seed-m5-kind-complete-cascade/</id>
  <title>Mission Seed M5 - Kind-Complete Cascade and Orphan Wiring</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-m5-kind-complete-cascade/"/>
  <summary>Specify-intake seed for the mission closing #2829 and the residual of #3009: expand the cascade relation set and wire the remaining orphaned artefacts.</summary>
  <content type="html">&lt;h2 id=&quot;mission-seed--m5-kind-complete-cascade--orphan-wiring&quot;&gt;Mission Seed — M5: Kind-Complete Cascade + Orphan Wiring&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; #2829, and the residual of #3009.
&lt;strong&gt;Effort:&lt;/strong&gt; L, &lt;strong&gt;ADR-worthy.&lt;/strong&gt; &lt;strong&gt;Depends on:&lt;/strong&gt; land &lt;strong&gt;LAST&lt;/strong&gt; — it changes cascade reach and ripples golden counts, so it must re-ledger once, atop M2’s fragment edges.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id=&quot;problem&quot;&gt;Problem&lt;/h2&gt;
&lt;p&gt;Two complementary reach gaps:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;#2829 — relation-set dead-end.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;REFERENCE_RELATIONS = {requires, suggests, refines}&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;mission_type&lt;/code&gt; nodes carry only &lt;code dir=&quot;auto&quot;&gt;requires→action&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;action&lt;/code&gt; nodes carry &lt;code dir=&quot;auto&quot;&gt;scope→{directive,tactic,…}&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;instantiates→template&lt;/code&gt; — never requires/suggests/refines. The forward closure reaches the &lt;code dir=&quot;auto&quot;&gt;action&lt;/code&gt; node, &lt;code dir=&quot;auto&quot;&gt;_referenced_artifacts&lt;/code&gt; drops it (action is not an artifact kind), and finds nothing. &lt;strong&gt;Measured: cascade from every built-in mission_type returns 0 activated kinds.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#3009 residual — absent inbound edges.&lt;/strong&gt; A handful of charter-activated artefacts have zero inbound edges of any followed relation, so cascade reaches none of them. &lt;strong&gt;Most of #3009 already landed&lt;/strong&gt; (membership set replacing the bare count, wire-8-delete-1, reachability companion metric); only ~5 &lt;code dir=&quot;auto&quot;&gt;_ACTIVATED_BUT_ORPHANED&lt;/code&gt; artefacts remain to author edges for (or mark direct-activation-only): &lt;code dir=&quot;auto&quot;&gt;styleguide:deployable-skill-authoring&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;quadruple-a-test-format&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;given-when-then-authoring&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;toolguide:sonar&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;toolguide:gherkin&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;These are complementary, not one subsuming the other: #2829 fixes nodes that &lt;em&gt;have&lt;/em&gt; &lt;code dir=&quot;auto&quot;&gt;scope&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;instantiates&lt;/code&gt; inbound but are never followed; #3009 fixes nodes with &lt;em&gt;no&lt;/em&gt; inbound edges at all.&lt;/p&gt;
&lt;h2 id=&quot;fix-approach&quot;&gt;Fix approach&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;#2829:&lt;/strong&gt; expand the cascade traversal so activating a &lt;code dir=&quot;auto&quot;&gt;mission_type&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;action&lt;/code&gt; reaches every kind its actions depend on — add &lt;code dir=&quot;auto&quot;&gt;scope&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;instantiates&lt;/code&gt; (the action-hop relations; consider &lt;code dir=&quot;auto&quot;&gt;vocabulary&lt;/code&gt;) to the followed set, OR reuse &lt;code dir=&quot;auto&quot;&gt;resolve_context&lt;/code&gt;’s scope→requires→suggests algorithm for the action hop. Keep &lt;code dir=&quot;auto&quot;&gt;in_tension_with&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;reconciles_tension&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;rejects&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;delegates_to&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;applies&lt;/code&gt; excluded. &lt;code dir=&quot;auto&quot;&gt;_referenced_artifacts&lt;/code&gt; must still yield terminal artifact kinds, not intermediate &lt;code dir=&quot;auto&quot;&gt;action&lt;/code&gt; nodes. &lt;strong&gt;Likely its own ADR; re-ledger golden counts.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#3009 residual:&lt;/strong&gt; author real inbound edges for the ~5 remaining orphaned artefacts (or mark by-design direct-activation-only) and shrink the ledger membership set accordingly. Shares the per-artefact-review authoring activity with M3’s triage.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;open-operator-decisions-resolve-at-this-missions-discovery--adr&quot;&gt;Open operator decisions (resolve at this mission’s discovery / ADR)&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Which relations join the followed set&lt;/strong&gt; for the action hop — &lt;code dir=&quot;auto&quot;&gt;scope&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;instantiates&lt;/code&gt; only, or also &lt;code dir=&quot;auto&quot;&gt;vocabulary&lt;/code&gt;? This is the ADR’s core call.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Orphan dispositions:&lt;/strong&gt; for each of the ~5 &lt;code dir=&quot;auto&quot;&gt;_ACTIVATED_BUT_ORPHANED&lt;/code&gt; artefacts — author an inbound edge or mark direct-activation-only?&lt;/li&gt;
&lt;/ul&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 cascade relation-set expansion (with ADR), the ~5 residual orphan-edge authoring, the single golden re-ledger.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Out:&lt;/strong&gt; everything the other missions own. Do not re-do the already-landed #3009 pieces.&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/cascade.py&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;REFERENCE_RELATIONS&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;_referenced_artifacts&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;_forward_reference_closure&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;the golden-count ledger surfaces (re-ledger once)&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;resolve_context&lt;/code&gt;’s scope→requires→suggests algorithm (reuse candidate)&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;sequencing&quot;&gt;Sequencing&lt;/h2&gt;
&lt;p&gt;Land &lt;strong&gt;after&lt;/strong&gt; M2 so the fragment edges are already in the graph when the relation-set expansion re-ledgers golden counts — counts move once, not twice.&lt;/p&gt;</content>
</entry>
