<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/plans/doctrine/delivery-reachability-wiring-table/">
  <id>https://docs.spec-kitty.ai/plans/doctrine/delivery-reachability-wiring-table/</id>
  <title>Delivery-reachability wiring table (FR-015)</title>
  <updated>2026-07-29T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/plans/doctrine/delivery-reachability-wiring-table/"/>
  <summary>Per candidate artefact: proposed inbound source, its measured action-reachability (WP08 helper), and the C-007 wire/defer disposition; the deferred set is the decision surface.</summary>
  <content type="html">&lt;h2 id=&quot;delivery-reachability-wiring-table-fr-015-wp09&quot;&gt;Delivery-reachability wiring table (FR-015, WP09)&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Retired (deprecated).&lt;/strong&gt; Design shipped via merged mission &lt;code dir=&quot;auto&quot;&gt;doctrine-delivery-reachability-01KYMXD6&lt;/code&gt; (15 WPs). Preserved as a historical record.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;This is the enumerated wiring table FR-015 requires. Its purpose is to make
“obvious” a &lt;strong&gt;computation&lt;/strong&gt; rather than a judgement, so this work package does
not reproduce PR #3007’s failure — 4 edges authored to sources that were
themselves unreachable, so the wired artefacts still reached nobody.&lt;/p&gt;
&lt;h2 id=&quot;the-disposition-rule-c-007-operator-ruling-2026-07-28&quot;&gt;The disposition rule (C-007, operator ruling 2026-07-28)&lt;/h2&gt;
&lt;p&gt;An unreachable &lt;strong&gt;activated&lt;/strong&gt; artefact is &lt;em&gt;obvious&lt;/em&gt; (in scope to wire now) &lt;strong&gt;iff&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;(a)&lt;/strong&gt; the relationship is &lt;strong&gt;attested in the artefact’s own text&lt;/strong&gt; — not
inferred from topic adjacency — &lt;strong&gt;and&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;(b)&lt;/strong&gt; the proposed inbound source is &lt;strong&gt;itself action-reachable&lt;/strong&gt; under the
WP08 measure, &lt;strong&gt;or&lt;/strong&gt; the edge is a &lt;code dir=&quot;auto&quot;&gt;scope&lt;/code&gt; edge from an &lt;strong&gt;action&lt;/strong&gt; node.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Everything failing &lt;strong&gt;(b)&lt;/strong&gt; is &lt;strong&gt;deferred&lt;/strong&gt; to an after-mission operator
interview. &lt;code dir=&quot;auto&quot;&gt;wire&lt;/code&gt; = passes (a)+(b); &lt;code dir=&quot;auto&quot;&gt;defer&lt;/code&gt; = fails (b).&lt;/p&gt;
&lt;h2 id=&quot;how-every-reachability-value-here-was-measured-r-1&quot;&gt;How every reachability value here was measured (R-1)&lt;/h2&gt;
&lt;p&gt;Reachability is &lt;strong&gt;measured, never eyeballed&lt;/strong&gt;. Every &lt;code dir=&quot;auto&quot;&gt;source action-reachable?&lt;/code&gt;
value below is the result of &lt;em&gt;calling&lt;/em&gt; WP08’s helper
&lt;code dir=&quot;auto&quot;&gt;doctrine.drg.reachability.action_channel_reachable&lt;/code&gt;, which itself &lt;em&gt;calls&lt;/em&gt;
&lt;code dir=&quot;auto&quot;&gt;doctrine.drg.query.resolve_context&lt;/code&gt; (the single canonical walk) once per action
seed and unions the result. No BFS was reimplemented — R-1 forbids it, and every
hand-rolled walk in this mission’s history produced a wrong number.&lt;/p&gt;
&lt;p&gt;Baseline, shipped built-in graph before this WP:&lt;/p&gt;





























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;measure&lt;/th&gt;&lt;th&gt;value&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;nodes / edges&lt;/td&gt;&lt;td&gt;310 / 781&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;action-reachable artefacts, &lt;code dir=&quot;auto&quot;&gt;d=1&lt;/code&gt; (compact)&lt;/td&gt;&lt;td&gt;111&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;action-reachable artefacts, &lt;code dir=&quot;auto&quot;&gt;d=2&lt;/code&gt; (bootstrap)&lt;/td&gt;&lt;td&gt;118&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;resolved activated artefacts (node form)&lt;/td&gt;&lt;td&gt;184&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;activated &lt;strong&gt;and&lt;/strong&gt; action-unreachable at &lt;code dir=&quot;auto&quot;&gt;d=2&lt;/code&gt;&lt;/td&gt;&lt;td&gt;78&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;h2 id=&quot;the-wiring-table&quot;&gt;The wiring table&lt;/h2&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;source action-reachable?&lt;/code&gt; is the &lt;strong&gt;measured&lt;/strong&gt; value for the &lt;em&gt;proposed source&lt;/em&gt;
(the value C-007(b) turns on). For a &lt;code dir=&quot;auto&quot;&gt;scope&lt;/code&gt;-from-action row the source is an
&lt;code dir=&quot;auto&quot;&gt;action&lt;/code&gt; node, which is the reachability seed itself — C-007(b)‘s second clause.&lt;/p&gt;


















































































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;#&lt;/th&gt;&lt;th&gt;candidate artefact&lt;/th&gt;&lt;th&gt;proposed inbound source&lt;/th&gt;&lt;th&gt;source action-reachable? (measured)&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;1&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;directive:DIRECTIVE_042&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;action:documentation/generate&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;scope&lt;/code&gt;)&lt;/td&gt;&lt;td&gt;&lt;strong&gt;n/a — action seed&lt;/strong&gt; (C-007b clause 2)&lt;/td&gt;&lt;td&gt;&lt;strong&gt;wire&lt;/strong&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;2&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;asset:common-docs-structural-lint&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;directive:DIRECTIVE_042&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt;, already present)&lt;/td&gt;&lt;td&gt;&lt;strong&gt;False → True after row 1 lands&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;strong&gt;wire (transitive)&lt;/strong&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;3&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;styleguide:common-docs&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;directive:DIRECTIVE_042&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;, already present)&lt;/td&gt;&lt;td&gt;&lt;strong&gt;False → True after row 1 lands&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;strong&gt;wire (transitive)&lt;/strong&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;4&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:common-docs-curation&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;directive:DIRECTIVE_042&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;, already present)&lt;/td&gt;&lt;td&gt;&lt;strong&gt;False → True after row 1 lands&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;strong&gt;wire (transitive)&lt;/strong&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;5&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:common-docs-find&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;directive:DIRECTIVE_042&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;, already present)&lt;/td&gt;&lt;td&gt;&lt;strong&gt;False → True after row 1 lands&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;strong&gt;wire (transitive)&lt;/strong&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;6&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:common-docs-scaffold&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;directive:DIRECTIVE_042&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;, already present)&lt;/td&gt;&lt;td&gt;&lt;strong&gt;False → True after row 1 lands&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;strong&gt;wire (transitive)&lt;/strong&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;7&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:common-docs-write&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;directive:DIRECTIVE_042&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;, already present)&lt;/td&gt;&lt;td&gt;&lt;strong&gt;False → True after row 1 lands&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;strong&gt;wire (transitive)&lt;/strong&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;8&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;paradigm:atomic-design&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:atomic-design-review-checklist&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;, already present from PR #3007)&lt;/td&gt;&lt;td&gt;&lt;strong&gt;False&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;strong&gt;defer&lt;/strong&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;9&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;styleguide:reasons-canvas-writing&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;paradigm:structured-prompt-driven-development&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;, already present from PR #3007)&lt;/td&gt;&lt;td&gt;&lt;strong&gt;False&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;strong&gt;defer&lt;/strong&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;10&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:occurrence-classification-workflow&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;directive:DIRECTIVE_035&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt;, already present from PR #3007)&lt;/td&gt;&lt;td&gt;&lt;strong&gt;False&lt;/strong&gt; (DIRECTIVE_035 has no reaching inbound edge)&lt;/td&gt;&lt;td&gt;&lt;strong&gt;defer&lt;/strong&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;Rows 8–10 are the re-adjudication of PR #3007’s three still-inert wirings: each
already carries an inbound edge, but its source is itself action-unreachable
(measured &lt;strong&gt;False&lt;/strong&gt;), so the target reaches nobody. That is precisely the
incidence-vs-reachability gap this mission exists to close — an inbound edge is
&lt;strong&gt;not&lt;/strong&gt; reachability (R-6). They are &lt;strong&gt;not&lt;/strong&gt; re-wired (that would repeat the #3007
error); they are recorded here and deferred.&lt;/p&gt;
&lt;h3 id=&quot;why-only-one-edge-is-authored&quot;&gt;Why only ONE edge is authored&lt;/h3&gt;
&lt;p&gt;Row 1 (&lt;code dir=&quot;auto&quot;&gt;action:documentation/generate --scope--&gt; directive:DIRECTIVE_042&lt;/code&gt;) is
the only &lt;strong&gt;new&lt;/strong&gt; edge. DIRECTIVE_042 already carries &lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; edges
to the asset, the styleguide and the four common-docs tactics; making 042 itself
action-reachable delivers all six transitively (rows 2–7). Measured after the
edge lands: &lt;code dir=&quot;auto&quot;&gt;d=1&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;d=2&lt;/code&gt; action-reachable each grow by exactly &lt;strong&gt;7&lt;/strong&gt;
(111→118, 118→125), the seven artefacts in rows 1–7. Minimal edge, maximal
delivery (avoid gold-plating / locality-of-change).&lt;/p&gt;
&lt;h2 id=&quot;the-common-docs-cluster-t050--wired&quot;&gt;The &lt;code dir=&quot;auto&quot;&gt;common-docs&lt;/code&gt; cluster (T050) — wired&lt;/h2&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;asset:common-docs-structural-lint&lt;/code&gt; is the first shipped doctrine ASSET
(WP10/WP11 of the delivery rail ship assets). It has four inbound &lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt;
edges, from DIRECTIVE_042, &lt;code dir=&quot;auto&quot;&gt;styleguide:common-docs&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic:common-docs-curation&lt;/code&gt;
and &lt;code dir=&quot;auto&quot;&gt;tactic:common-docs-scaffold&lt;/code&gt; — and &lt;strong&gt;all four sources were measured
unreachable&lt;/strong&gt;. The whole documentation-authoring family (042, the common-docs
styleguide, the common-docs &lt;code dir=&quot;auto&quot;&gt;find&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;write&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;curation&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;scaffold&lt;/code&gt; tactics, and the
docs styleguides &lt;code dir=&quot;auto&quot;&gt;divio-type-discipline&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;docs-accessibility&lt;/code&gt; /
&lt;code dir=&quot;auto&quot;&gt;docs-freshness-sla&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;plain-language&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;publication-authority&lt;/code&gt;) is a
strongly-connected &lt;strong&gt;island&lt;/strong&gt;: every edge pointing into it originates &lt;strong&gt;inside&lt;/strong&gt;
it, and &lt;strong&gt;no &lt;code dir=&quot;auto&quot;&gt;action&lt;/code&gt; node scopes any member&lt;/strong&gt; (measured — the documentation
step contracts scope DIRECTIVE_010/037/003/001/018 and a handful of tactics,
never 042 or common-docs).&lt;/p&gt;
&lt;p&gt;C-007(b) offers two ways in. Both were tested against the graph, not guessed:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Edge from an action-reachable source&lt;/strong&gt; — measured &lt;strong&gt;impossible&lt;/strong&gt;. Every
artefact that even &lt;em&gt;mentions&lt;/em&gt; common-docs / the structural lint / DIRECTIVE_042
in its own text is itself action-unreachable (the cluster members plus the
five docs styleguides). No reachable directive, tactic or procedure attests a
relationship into the cluster, so any such edge would be topic-adjacency — the
exact C-007(a) violation, and the #3007 failure mode.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A &lt;code dir=&quot;auto&quot;&gt;scope&lt;/code&gt; edge from an action node&lt;/strong&gt; — &lt;strong&gt;available and attested.&lt;/strong&gt;
DIRECTIVE_042’s own &lt;code dir=&quot;auto&quot;&gt;scope:&lt;/code&gt; text reads &lt;em&gt;“Applies whenever a documentation
file under the Common Docs root is created, moved, renamed…”&lt;/em&gt;. The
&lt;code dir=&quot;auto&quot;&gt;documentation/generate&lt;/code&gt; action’s &lt;code dir=&quot;auto&quot;&gt;write_docs&lt;/code&gt; step writes &lt;code dir=&quot;auto&quot;&gt;docs/**/*.md&lt;/code&gt;
under the mission — i.e. it &lt;strong&gt;creates documentation files&lt;/strong&gt;, exactly 042’s
stated trigger. The relationship is therefore attested in 042’s own text
(C-007a), and the source is an action node (C-007b clause 2). This is a
recorded relationship, &lt;strong&gt;not an invented one&lt;/strong&gt; — so the “defer instead of
invent” guard does not fire.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;Disposition: WIRE&lt;/strong&gt;, via row 1.&lt;/p&gt;
&lt;h2 id=&quot;b2-handoff--the-scope-edges-canonical-home&quot;&gt;B2 handoff — the scope edge’s canonical home&lt;/h2&gt;
&lt;p&gt;The edge lands in &lt;code dir=&quot;auto&quot;&gt;HAND_AUTHORED_EDGES&lt;/code&gt;
(&lt;code dir=&quot;auto&quot;&gt;src/doctrine/drg/migration/hand_authored_overlay.py&lt;/code&gt;), because that is where
WP09’s wiring edges land per the contract and the WP prompt. The &lt;strong&gt;canonical&lt;/strong&gt;
home for an action→artefact &lt;code dir=&quot;auto&quot;&gt;scope&lt;/code&gt; edge is the documentation mission &lt;strong&gt;step
contract action index&lt;/strong&gt; — &lt;code dir=&quot;auto&quot;&gt;src/doctrine/missions/built_in_step_contracts/documentation-generate.step-contract.yaml&lt;/code&gt;
would list &lt;code dir=&quot;auto&quot;&gt;042-common-docs&lt;/code&gt; as a &lt;code dir=&quot;auto&quot;&gt;delegates_to&lt;/code&gt; candidate, and the extractor
would mint the scope edge from it. That surface is &lt;strong&gt;outside WP09’s owned
files&lt;/strong&gt;, so WP09 authors the reaching edge in the overlay and records the
migration here.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Mission B2 (&lt;code dir=&quot;auto&quot;&gt;drg-edge-migration-extractor-retirement-01KYFV8C&lt;/code&gt;) retires the
overlay generator.&lt;/strong&gt; When it does, it must &lt;strong&gt;not&lt;/strong&gt; silently drop this edge: it
migrates &lt;code dir=&quot;auto&quot;&gt;action:documentation/generate --scope--&gt; directive:DIRECTIVE_042&lt;/code&gt; into
the documentation step-contract action index (and may, per 042’s full scope
text, additionally scope 042 in &lt;code dir=&quot;auto&quot;&gt;documentation/design&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;/publish&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;/validate&lt;/code&gt;
and &lt;code dir=&quot;auto&quot;&gt;/accept&lt;/code&gt; — WP09 authored only the single minimal edge needed for
reachability). This is a &lt;strong&gt;known&lt;/strong&gt; migration, inherited deliberately, not a
surprise.&lt;/p&gt;
&lt;h2 id=&quot;family-a-3063-ddd-family--operator-interview-outcome-wired&quot;&gt;Family A (#3063 DDD family) — operator interview outcome, WIRED&lt;/h2&gt;
&lt;p&gt;The #3063 operator interview ATTESTED the Domain-Driven Design family (C-007(a)
satisfied by operator ruling). Hub: &lt;code dir=&quot;auto&quot;&gt;paradigm:domain-driven-design&lt;/code&gt;. Fourteen
edges land in &lt;code dir=&quot;auto&quot;&gt;HAND_AUTHORED_EDGES&lt;/code&gt;:&lt;/p&gt;















































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;#&lt;/th&gt;&lt;th&gt;source&lt;/th&gt;&lt;th&gt;relation&lt;/th&gt;&lt;th&gt;target&lt;/th&gt;&lt;th&gt;delivers reachability?&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;A1&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;action:software-dev/specify&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;scope&lt;/code&gt;&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;paradigm:domain-driven-design&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;strong&gt;yes — the reaching edge&lt;/strong&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;A2–A11&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;paradigm:domain-driven-design&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt;&lt;/td&gt;&lt;td&gt;the 10 DDD members below&lt;/td&gt;&lt;td&gt;yes, transitively via A1&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;A12&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;agent_profile:architect-alphonso&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;paradigm:domain-driven-design&lt;/code&gt;&lt;/td&gt;&lt;td&gt;no — composition-only (inert)&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;A13&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;agent_profile:paula-patterns&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;paradigm:domain-driven-design&lt;/code&gt;&lt;/td&gt;&lt;td&gt;no — composition-only (inert)&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;A14&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;agent_profile:randy-reducer&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;paradigm:domain-driven-design&lt;/code&gt;&lt;/td&gt;&lt;td&gt;no — composition-only (inert)&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;The 10 &lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt; members (A2–A11), each attested as DDD in its &lt;strong&gt;own&lt;/strong&gt; text:
&lt;code dir=&quot;auto&quot;&gt;tactic:bounded-context-identification&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic:context-mapping-classification&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;tactic:context-boundary-inference&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic:bounded-context-canvas-fill&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;tactic:strategic-domain-classification&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic:aggregate-boundary-design&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;tactic:entity-value-object-classification&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic:domain-event-capture&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;tactic:anti-corruption-layer&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;styleguide:aggregate-design-rules&lt;/code&gt;.&lt;/p&gt;
&lt;h3 id=&quot;️-the-specify-edge-is-scope-not-suggests-relation-correction&quot;&gt;⚠️ The specify edge is &lt;code dir=&quot;auto&quot;&gt;scope&lt;/code&gt;, NOT &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; (relation correction)&lt;/h3&gt;
&lt;p&gt;The #3063 wiring instruction named the specify→paradigm edge &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; &lt;strong&gt;and&lt;/strong&gt;
required it to change action reachability + move the pinned unreachable sets.
Those two are contradictory, and the contradiction is resolved by &lt;strong&gt;measurement&lt;/strong&gt;
(WP08 helper, R-1): a &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; edge whose SOURCE is an &lt;code dir=&quot;auto&quot;&gt;action&lt;/code&gt; node is &lt;strong&gt;inert&lt;/strong&gt;
— &lt;code dir=&quot;auto&quot;&gt;resolve_context&lt;/code&gt; walks &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; only from scope-resolved artifacts, never
from the action node itself (&lt;code dir=&quot;auto&quot;&gt;query.resolve_context&lt;/code&gt; steps 2/3 seed from
&lt;code dir=&quot;auto&quot;&gt;scoped_artifacts&lt;/code&gt;). Measured: &lt;code dir=&quot;auto&quot;&gt;specify --suggests--&gt; ddd&lt;/code&gt; leaves &lt;code dir=&quot;auto&quot;&gt;d=1&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;d=2&lt;/code&gt;
unchanged (118/125); &lt;code dir=&quot;auto&quot;&gt;specify --scope--&gt; ddd&lt;/code&gt; grows both by 12. Only &lt;code dir=&quot;auto&quot;&gt;scope&lt;/code&gt;
delivers — exactly the WP09 precedent (&lt;code dir=&quot;auto&quot;&gt;documentation/generate --scope--&gt; 042&lt;/code&gt;).
The &lt;code dir=&quot;auto&quot;&gt;§3&lt;/code&gt; mandate (“this edge DOES change action reachability; update the pins”)
is satisfiable &lt;strong&gt;only&lt;/strong&gt; by &lt;code dir=&quot;auto&quot;&gt;scope&lt;/code&gt;, so the edge is authored as &lt;code dir=&quot;auto&quot;&gt;scope&lt;/code&gt; and the
&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; label is corrected here. C-007: (a) DDD’s own summary attests aligning
code with a deep domain model — what the software-dev specify step does; (b) the
source is an &lt;code dir=&quot;auto&quot;&gt;action&lt;/code&gt; node (C-007(b) clause 2).&lt;/p&gt;
&lt;h3 id=&quot;attestation-audit--what-was-excluded-as-non-attested&quot;&gt;Attestation audit — what was EXCLUDED as non-attested&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:reference-architectural-patterns&lt;/code&gt; — its own text is &lt;em&gt;general&lt;/em&gt; reference-
architecture selection by quality attributes (scalability/consistency/latency),
with no DDD content. NOT a DDD member; the &lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt; edge is &lt;strong&gt;not&lt;/strong&gt; authored.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:compositional-stream-boundaries&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic:cross-cutting-state-via-store&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;tactic:atomic-state-ownership&lt;/code&gt; — state/UI concerns, not DDD strategic/tactical
design. Left out (per the #3063 ambiguity guard).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;deferred--the-ddddocumentation-mutual-reinforcement-edge-b1&quot;&gt;DEFERRED — the DDD↔documentation mutual-reinforcement edge (B1)&lt;/h3&gt;
&lt;p&gt;Not authored: the DDD↔documentation mutual-reinforcement relationship is &lt;strong&gt;gated
on the upcoming value-based edge properties (B1)&lt;/strong&gt; and is left &lt;strong&gt;pending&lt;/strong&gt; until
that lands. Recorded here, not wired.&lt;/p&gt;
&lt;h3 id=&quot;measured-reachability-delta-wp08-helper-r-1&quot;&gt;Measured reachability delta (WP08 helper, R-1)&lt;/h3&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;d=1&lt;/code&gt; action-reachable 118→130; &lt;code dir=&quot;auto&quot;&gt;d=2&lt;/code&gt; 125→137 (each +12). The twelve that become
action-reachable and leave BOTH &lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_D1&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;D2&lt;/code&gt;:
&lt;code dir=&quot;auto&quot;&gt;paradigm:domain-driven-design&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;directive:DIRECTIVE_031&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;directive:DIRECTIVE_032&lt;/code&gt;
(the paradigm’s pre-existing &lt;code dir=&quot;auto&quot;&gt;directive_refs&lt;/code&gt;, delivered once it is scoped),
&lt;code dir=&quot;auto&quot;&gt;styleguide:aggregate-design-rules&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic:aggregate-boundary-design&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;tactic:anti-corruption-layer&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic:bounded-context-canvas-fill&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;tactic:bounded-context-identification&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic:context-boundary-inference&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;tactic:context-mapping-classification&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic:domain-event-capture&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;tactic:entity-value-object-classification&lt;/code&gt;.
&lt;code dir=&quot;auto&quot;&gt;tactic:strategic-domain-classification&lt;/code&gt; was already action-reachable, so it is
delivered but moves no pin. The profile channel is unchanged (measured 39→39): the
three &lt;code dir=&quot;auto&quot;&gt;agent_profile --suggests--&gt; ddd&lt;/code&gt; edges are inert, and the DDD paradigm stays
profile-unreachable so its new &lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt; edges deliver nothing there.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;SUPERSEDED (WP03, mission &lt;code dir=&quot;auto&quot;&gt;doctrine-delivery-activation-01KYQVQK&lt;/code&gt;, D19):&lt;/strong&gt; the
“profile channel is unchanged (measured 39→39)” claim above describes the
pre-WP01 profile channel ({requires, specializes_from} only). WP01 added
&lt;code dir=&quot;auto&quot;&gt;SUGGESTS&lt;/code&gt;, so the live profile channel reaches far more
(&lt;code dir=&quot;auto&quot;&gt;_PROFILE_UNREACHABLE&lt;/code&gt; 153 → 60). See “Composition ledger (NFR-002) —
profile-channel walk-activation” below for the current record. Left in situ as
the historical Family-A record.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id=&quot;the-deferred-set-t052--the-operators-decision-surface&quot;&gt;The deferred set (T052) — the operator’s decision surface&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;WP03 reconciliation (mission &lt;code dir=&quot;auto&quot;&gt;doctrine-delivery-activation-01KYQVQK&lt;/code&gt;, D19):&lt;/strong&gt;
This “&lt;strong&gt;50&lt;/strong&gt;” is the &lt;strong&gt;action-channel&lt;/strong&gt; deferred set (&lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_D2&lt;/code&gt;),
re-measured and &lt;strong&gt;confirmed still 50&lt;/strong&gt; — WP02’s Family A/B/C topology is
action-inert. The “&lt;strong&gt;60&lt;/strong&gt;” that appears in the Family B/C ledgers below
(“Deferred set unchanged at 60”) is a &lt;em&gt;pre-Family-D snapshot&lt;/em&gt;, not a live
baseline (this same section records Family D delivering 10, 60 → 50). The plan’s
D19 asked to reset 50 → 60; re-measurement shows 50 is the correct current
action figure, so it is left at 50. What this mission &lt;em&gt;does&lt;/em&gt; lower is the
&lt;strong&gt;neither-channel&lt;/strong&gt; deferred set (delivered by no channel): 48 → 20, via WP01’s
profile-channel &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; walk. See “Composition ledger (NFR-002) —
profile-channel walk-activation” for the 30 rescued members and the 20 that
remain.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;These &lt;strong&gt;50&lt;/strong&gt; activated artefacts remain action-unreachable at &lt;code dir=&quot;auto&quot;&gt;d=2&lt;/code&gt; after row 1
(WP09), Family A (#3063), and Family D (#3063, ACCEPT DELIVERY) land. Each fails C-007(b): no action-reachable source with a textually-attested
relationship, and no &lt;code dir=&quot;auto&quot;&gt;scope&lt;/code&gt;-from-action path whose relationship is attested
without invention. &lt;strong&gt;Family E (#3063) does not change this count&lt;/strong&gt;: it is
topology-only / INERT (every source is the architect profile or an action-
unreachable tactic/toolguide, and the reinforcement edges point into already-
reachable paradigms), so no artefact leaves the deferred set — delivery is the
fast-follow’s job per the operator. The set stays at &lt;strong&gt;50&lt;/strong&gt;. &lt;strong&gt;This is not a filed issue&lt;/strong&gt; — it is the surface the
after-mission operator interview rules on (C-007). Wiring any of these now would
mean either wiring to an unreachable source (#3007’s error) or inventing a
relationship (the guard T050 forbids).&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Family D (#3063) delivered 10 of the previous 60.&lt;/strong&gt; The operator ruled
ACCEPT DELIVERY for the TESTING/BDD/MUTATION family, so these left the deferred
set and are now action-reachable at implement/review (they are dropped from the
list below): &lt;code dir=&quot;auto&quot;&gt;paradigm:specification-by-example&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;procedure:example-mapping-workshop&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic:development-bdd&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;tactic:atdd-adversarial-acceptance&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic:formalized-constraint-testing&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;tactic:adversarial-qa-handoff&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic:work-package-completion-validation&lt;/code&gt;
(all seven reachable at d=1 and d=2), plus &lt;code dir=&quot;auto&quot;&gt;tactic:reverse-speccing&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;tactic:test-to-system-reconstruction&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;styleguide:mutation-aware-test-design&lt;/code&gt;
(reachable at d=2 only). See the Family D section below.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h3 id=&quot;note-4-of-the-50-are-edge-incident-from-a-reachable-source-depth-gated&quot;&gt;Note: 4 of the 50 are edge-incident from a reachable source, depth-gated&lt;/h3&gt;
&lt;p&gt;The following already carry an inbound edge &lt;strong&gt;from an action-reachable source&lt;/strong&gt;,
but the edge is &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; (or a &lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt; chain) that sits &lt;strong&gt;beyond the
traversal depth horizon&lt;/strong&gt;, so &lt;code dir=&quot;auto&quot;&gt;resolve_context&lt;/code&gt; does not reach them at &lt;code dir=&quot;auto&quot;&gt;d=2&lt;/code&gt;.
They are &lt;strong&gt;not orphans&lt;/strong&gt; and are &lt;strong&gt;not&lt;/strong&gt; wiring candidates: the relationship
already exists as an edge; “fixing” them would mean upgrading &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;→&lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt;
(claiming a hard dependency the text does not attest) or deepening the bootstrap
walk — both are traversal-policy decisions for the operator, not edge authoring.
(Five former rows — &lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_032&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;anti-corruption-layer&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;bounded-context-identification&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;context-mapping-classification&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;domain-event-capture&lt;/code&gt; — left this table when Family A (#3063) made them
action-reachable via the DDD paradigm.)&lt;/p&gt;

























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;artefact&lt;/th&gt;&lt;th&gt;reachable inbound source (relation)&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;tactic:ownership-map-leeway&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;styleguide:planning-and-tracking&lt;/code&gt; (suggests)&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:pr-agent-worktree-isolation&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;directive:DIRECTIVE_043&lt;/code&gt; (suggests)&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:zombies-tdd&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:delete-the-assertion-not-the-test&lt;/code&gt; (suggests)&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;toolguide:github-tracker&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;styleguide:planning-and-tracking&lt;/code&gt; (suggests)&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;(&lt;code dir=&quot;auto&quot;&gt;procedure:example-mapping-workshop&lt;/code&gt; left this table when Family D made it
action-reachable at implement/review via &lt;code dir=&quot;auto&quot;&gt;directive:DIRECTIVE_034&lt;/code&gt;.)&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Operator ruling (2026-07-29): ACCEPT all four as-is.&lt;/strong&gt; They are reachable in
principle — an agent following the &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; chain still reaches them — and
correctly sit &lt;em&gt;beyond the eager &lt;code dir=&quot;auto&quot;&gt;d=2&lt;/code&gt; bootstrap horizon&lt;/em&gt; by design. The two
alternatives were both rejected: upgrading &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;→&lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt; would falsely
claim a hard dependency none of the four texts attest (misrepresentation), and
deepening the bootstrap walk is a &lt;strong&gt;global&lt;/strong&gt; traversal-policy change whose blast
radius pulls in &lt;em&gt;every&lt;/em&gt; depth-3 artefact, not just these four. Delivery-depth
tuning (and the profile-channel &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;-follow that would animate the inert
Family B/C/E edges) is deferred to the &lt;strong&gt;fast-follow walk-update mission&lt;/strong&gt;. No
edge is upgraded and no walk is deepened here.&lt;/p&gt;
&lt;h3 id=&quot;full-deferred-set-50-by-kind--directive-4--paradigm-3--procedure-4--styleguide-3--tactic-28--toolguide-8&quot;&gt;Full deferred set (50), by kind — directive 4 · paradigm 3 · procedure 4 · styleguide 3 · tactic 28 · toolguide 8&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;directive:DIRECTIVE_035&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;directive:DIRECTIVE_038&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;directive:DIRECTIVE_039&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;directive:DIRECTIVE_044&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;paradigm:atomic-design&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;paradigm:c4-incremental-detail-modeling&lt;/code&gt; — Family C: topology authored, delivery pending&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;paradigm:structured-prompt-driven-development&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;procedure:documentation-gap-prioritization&lt;/code&gt; — Family C candidate EXCLUDED as non-attested (see Family C section)&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;procedure:drill-down-documentation&lt;/code&gt; — Family C: topology authored, delivery pending&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;procedure:event-storming-discovery&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;procedure:migrate-project-guidance-to-spec-kitty-charter&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;styleguide:java-conventions&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;styleguide:reasons-canvas-writing&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:analysis-extract-before-interpret&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:architecture-diagram-review-checklist&lt;/code&gt; — Family C: topology authored, delivery pending&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:atomic-design-review-checklist&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:atomic-state-ownership&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:c4-zoom-in-architecture-documentation&lt;/code&gt; — Family C: topology authored, delivery pending&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:canonical-source-unification&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:chain-of-responsibility-rule-pipeline&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:code-documentation-analysis&lt;/code&gt; — Family C: topology authored, delivery pending&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:compositional-stream-boundaries&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:cross-cutting-state-via-store&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:mutation-testing-workflow&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:occurrence-classification-workflow&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:ownership-map-leeway&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:pr-agent-worktree-isolation&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:reasons-canvas-fill&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:reasons-canvas-review&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:refactoring-encapsulate-record&lt;/code&gt; — Family B: topology authored, delivery pending&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:refactoring-encapsulate-variable&lt;/code&gt; — Family B: topology authored, delivery pending&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:refactoring-extract-first-order-concept&lt;/code&gt; — Family B: topology authored, delivery pending&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:refactoring-move-field&lt;/code&gt; — Family B: topology authored, delivery pending&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:refactoring-move-method&lt;/code&gt; — Family B: topology authored, delivery pending&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:refactoring-state-pattern-for-behavior&lt;/code&gt; — Family B: topology authored, delivery pending&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:refactoring-strangler-fig&lt;/code&gt; — Family B: topology authored, delivery pending&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:reference-architectural-patterns&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:secure-regex-catastrophic-backtracking&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:terminology-extraction-mapping&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:test-readability-clarity-check&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:zombies-tdd&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;toolguide:contextive&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;toolguide:github-tracker&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;toolguide:maven-review-checks&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;toolguide:mermaid-diagramming&lt;/code&gt; — Family C: topology authored, delivery pending&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;toolguide:plantuml-diagramming&lt;/code&gt; — Family C: topology authored, delivery pending&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;toolguide:python-mutation-tools&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;toolguide:terminology-guard&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;toolguide:typescript-mutation-tools&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;composition-ledger-nfr-002--profile-channel-walk-activation-mission-doctrine-delivery-activation-01kyqvqk-wp01--wp03&quot;&gt;Composition ledger (NFR-002) — profile-channel walk-activation (mission &lt;code dir=&quot;auto&quot;&gt;doctrine-delivery-activation-01KYQVQK&lt;/code&gt;, WP01 + WP03)&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;This section is the successor to the “fast-follow walk-update mission” the
prose above repeatedly defers to.&lt;/strong&gt; Mission &lt;code dir=&quot;auto&quot;&gt;doctrine-delivery-activation-01KYQVQK&lt;/code&gt;
IS that fast-follow. WP01 added &lt;code dir=&quot;auto&quot;&gt;Relation.SUGGESTS&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;PROFILE_CHANNEL_RELATIONS&lt;/code&gt;
(&lt;code dir=&quot;auto&quot;&gt;src/doctrine/drg/reachability.py&lt;/code&gt;, FR-001), so the profile channel’s unbounded
&lt;code dir=&quot;auto&quot;&gt;walk_edges&lt;/code&gt; closure now follows the soft-recommendation web out of every activated
agent profile — animating the previously-inert Family B/C/E &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; edges the
prior mission authored (lines above: &lt;em&gt;“the profile-channel &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;-follow that
would animate the inert Family B/C/E edges … is deferred to the fast-follow
walk-update mission”&lt;/em&gt;).&lt;/p&gt;
&lt;h3 id=&quot;pin-moves-measured-via-profile_channel_reachable--action_channel_reachable-only--c-001&quot;&gt;Pin moves (measured via &lt;code dir=&quot;auto&quot;&gt;profile_channel_reachable&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;action_channel_reachable&lt;/code&gt; only — C-001)&lt;/h3&gt;
&lt;p&gt;Every number below traces to a call through the canonical reachability helpers
(no hand-rolled walk). WP03 re-measured against the WP01+WP02 topology:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;_PROFILE_UNREACHABLE&lt;/code&gt; 153 → 60&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;tests/doctrine/drg/test_reachability.py&lt;/code&gt;).
93 activated artefacts became profile-reachable via a &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; chain from an
activated profile once WP01’s relation addition landed.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;_PROFILE_RESCUES&lt;/code&gt; 2 → 30&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_D2 − _PROFILE_UNREACHABLE&lt;/code&gt;).
These 30 are the mission’s actual &lt;em&gt;delivery&lt;/em&gt;: activated artefacts the action
channel misses at &lt;code dir=&quot;auto&quot;&gt;d=2&lt;/code&gt; but the profile channel now reaches. Enumerated below.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_D1&lt;/code&gt; (60) and &lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_D2&lt;/code&gt; (50) UNCHANGED&lt;/strong&gt; —
measured, not assumed. WP02’s Family-A &lt;code dir=&quot;auto&quot;&gt;when&lt;/code&gt; backfill, the C4
&lt;code dir=&quot;auto&quot;&gt;template:instantiates&lt;/code&gt; edge and the anti-pattern &lt;code dir=&quot;auto&quot;&gt;REJECTS&lt;/code&gt; edges are all
action-channel-inert (a &lt;code dir=&quot;auto&quot;&gt;when&lt;/code&gt; guard, an &lt;code dir=&quot;auto&quot;&gt;instantiates&lt;/code&gt; edge no channel walks,
and validation-tier &lt;code dir=&quot;auto&quot;&gt;REJECTS&lt;/code&gt; edges — D13/D14). So this mission moves &lt;strong&gt;no&lt;/strong&gt;
action-channel pin. &lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_D2&lt;/code&gt; staying at 50 is the load-bearing
confirmation that the “50 vs 60” contradiction below is a &lt;em&gt;timeline&lt;/em&gt; artefact,
not a live discrepancy (see the reconciliation note).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;the-30-rescued-artefacts-by-prior-mission-family-attribution&quot;&gt;The 30 rescued artefacts, by prior-mission family attribution&lt;/h3&gt;
&lt;p&gt;Each is now delivered through the &lt;strong&gt;profile&lt;/strong&gt; channel (the responsible change is
WP01’s &lt;code dir=&quot;auto&quot;&gt;PROFILE_CHANNEL_RELATIONS&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;SUGGESTS&lt;/code&gt; addition; the family grouping names
the &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; cluster the artefact sits in, most authored by the prior mission’s
Family B/C topology):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Family B (#3063 REFACTORING) — 7&lt;/strong&gt;, formerly “topology authored, delivery pending”:
&lt;code dir=&quot;auto&quot;&gt;tactic:refactoring-encapsulate-record&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic:refactoring-encapsulate-variable&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;tactic:refactoring-extract-first-order-concept&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic:refactoring-move-field&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;tactic:refactoring-move-method&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic:refactoring-state-pattern-for-behavior&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;tactic:refactoring-strangler-fig&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Family C (#3063 ARCHITECTURE-DOCS / DIAGRAMMING) — 7&lt;/strong&gt;, formerly “topology authored, delivery pending”:
&lt;code dir=&quot;auto&quot;&gt;paradigm:c4-incremental-detail-modeling&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;procedure:drill-down-documentation&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;tactic:architecture-diagram-review-checklist&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic:c4-zoom-in-architecture-documentation&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;tactic:code-documentation-analysis&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;toolguide:mermaid-diagramming&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;toolguide:plantuml-diagramming&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Depth-gated &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; (the “4 of the 50 edge-incident, depth-gated” table above) — 4&lt;/strong&gt;:
&lt;code dir=&quot;auto&quot;&gt;tactic:ownership-map-leeway&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic:pr-agent-worktree-isolation&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;tactic:zombies-tdd&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;toolguide:github-tracker&lt;/code&gt;. These carried an inbound
&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; from a reachable source but sat beyond the action-channel &lt;code dir=&quot;auto&quot;&gt;d=2&lt;/code&gt;
horizon; the profile channel’s unbounded closure now reaches them.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Other &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;-web artefacts — 10&lt;/strong&gt;:
&lt;code dir=&quot;auto&quot;&gt;procedure:event-storming-discovery&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;styleguide:reasons-canvas-writing&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;tactic:canonical-source-unification&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic:mutation-testing-workflow&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;tactic:occurrence-classification-workflow&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic:terminology-extraction-mapping&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;toolguide:contextive&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;toolguide:python-mutation-tools&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;toolguide:terminology-guard&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;toolguide:typescript-mutation-tools&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Already profile-reachable pre-mission (in the prior &lt;code dir=&quot;auto&quot;&gt;_PROFILE_RESCUES&lt;/code&gt;) — 2&lt;/strong&gt;:
&lt;code dir=&quot;auto&quot;&gt;directive:DIRECTIVE_044&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic:test-readability-clarity-check&lt;/code&gt; (reached via a
profile &lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; edge that pre-dates WP01; carried forward).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;deferred-set-neither-channel--48--20&quot;&gt;Deferred set (neither channel) — 48 → 20&lt;/h3&gt;
&lt;p&gt;The wiring table’s “deferred set” (the &lt;code dir=&quot;auto&quot;&gt;d=2&lt;/code&gt; action-unreachable list above) is a
&lt;strong&gt;single-channel&lt;/strong&gt; surface. The operator’s true decision surface is what &lt;strong&gt;no&lt;/strong&gt;
channel delivers — &lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_D2 ∩ _PROFILE_UNREACHABLE&lt;/code&gt;. Before this
mission the profile channel rescued only 2 of the 50, so the neither-channel set
was 48. After WP01 it rescues 30, so the neither-channel deferred set drops to
&lt;strong&gt;20&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;directive:DIRECTIVE_035&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;directive:DIRECTIVE_038&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;directive:DIRECTIVE_039&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;paradigm:atomic-design&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;paradigm:structured-prompt-driven-development&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;procedure:documentation-gap-prioritization&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;procedure:migrate-project-guidance-to-spec-kitty-charter&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;styleguide:java-conventions&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:analysis-extract-before-interpret&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:atomic-design-review-checklist&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:atomic-state-ownership&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:chain-of-responsibility-rule-pipeline&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:compositional-stream-boundaries&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:cross-cutting-state-via-store&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:reasons-canvas-fill&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:reasons-canvas-review&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:reference-architectural-patterns&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:secure-regex-catastrophic-backtracking&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;toolguide:maven-review-checks&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;reconciliation-note--the-50-vs-60--3939-stale-prose-wp03-d19&quot;&gt;Reconciliation note — the “50 vs 60” / “39→39” stale prose (WP03, D19)&lt;/h3&gt;
&lt;p&gt;The plan’s D19 asked WP03 to treat the main deferred-set section’s &lt;strong&gt;50&lt;/strong&gt; as
stale and reset it to &lt;strong&gt;60&lt;/strong&gt;. WP03’s re-measurement shows the opposite is true, so
this note records the correct reconciliation instead of a silent inversion
(NFR-002 forbids moving a golden number without a paired justification, and that
cuts both ways — including &lt;em&gt;not&lt;/em&gt; moving a correct one to match a stale premise):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_D2&lt;/code&gt; measures 50&lt;/strong&gt;, exactly matching the main
“Full deferred set (50)” section. The &lt;code dir=&quot;auto&quot;&gt;60 → 50&lt;/code&gt; transition is the same doc’s
own Family-D ledger (“Family D delivered 10 of the previous 60”). So &lt;strong&gt;50 is the
current, correct action-channel figure&lt;/strong&gt;; the &lt;strong&gt;60&lt;/strong&gt; in the Family B/C ledgers
(“Deferred set unchanged at 60”) is a &lt;em&gt;pre-Family-D snapshot&lt;/em&gt; written earlier in
the doc’s authoring, not a live baseline. The two numbers are a timeline
artefact of a multi-pass document, not a contradiction to resolve by picking 60.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The “profile channel … measured 39→39” claims (Family A section) ARE stale&lt;/strong&gt;
(D19 correct on this point): they describe the profile channel &lt;em&gt;before&lt;/em&gt; WP01
added &lt;code dir=&quot;auto&quot;&gt;SUGGESTS&lt;/code&gt;. Under the live topology the profile channel reaches far more
(&lt;code dir=&quot;auto&quot;&gt;_PROFILE_UNREACHABLE&lt;/code&gt; 153 → 60), so those “39→39” figures are superseded by
this ledger. They are left in place as the historical Family-A record and
explicitly superseded here rather than edited in situ, to keep the Family-A
diff legible.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Net&lt;/strong&gt;: this mission does not lower the &lt;em&gt;action-channel&lt;/em&gt; deferred count (it
stays 50, correctly). It lowers the &lt;em&gt;neither-channel&lt;/em&gt; deferred count 48 → 20 via
the profile channel — the genuine delivery this mission ships. Per D18 the
per-member ledger-vs-diff comparison above is the sole non-delegable correctness
gate for the pins; a reviewer should verify each of the 30 rescued members and
the 20 remaining against the measured diff.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;writing-commsdiagramming-activation-commit-9a99801f1-3009--profile-channel-rescues-6&quot;&gt;Writing-comms/diagramming activation (commit &lt;code dir=&quot;auto&quot;&gt;9a99801f1&lt;/code&gt;, #3009) — profile-channel rescues +6&lt;/h3&gt;
&lt;p&gt;The dogfooding activation of the writing-comms/diagramming doctrine set (commit
&lt;code dir=&quot;auto&quot;&gt;9a99801f1&lt;/code&gt;) added seventeen artefacts to the action-channel unreachable sets
(&lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_D1&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;D2&lt;/code&gt;). Seven of the seventeen are &lt;strong&gt;rescued by the
profile channel&lt;/strong&gt; — action-&lt;code dir=&quot;auto&quot;&gt;d=2&lt;/code&gt;-unreachable yet delivered by an activated
writing-comms profile — so &lt;code dir=&quot;auto&quot;&gt;_PROFILE_RESCUES&lt;/code&gt; moves &lt;strong&gt;30 → 37&lt;/strong&gt;. Each delivering
edge is traced from the built-in graph via &lt;code dir=&quot;auto&quot;&gt;profile_channel_reachable&lt;/code&gt; (C-001, no
hand-rolled walk):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;directive:DIRECTIVE_047&lt;/code&gt; — &lt;code dir=&quot;auto&quot;&gt;agent_profile:scribe-sally&lt;/code&gt; requires it directly.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;directive:DIRECTIVE_048&lt;/code&gt; — &lt;code dir=&quot;auto&quot;&gt;agent_profile:scribe-sally&lt;/code&gt; requires it directly.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;directive:DIRECTIVE_049&lt;/code&gt; — &lt;code dir=&quot;auto&quot;&gt;agent_profile:minutes-maker-mahad&lt;/code&gt; requires it directly.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;directive:DIRECTIVE_050&lt;/code&gt; — &lt;code dir=&quot;auto&quot;&gt;agent_profile:minutes-maker-mahad&lt;/code&gt; requires it directly.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;directive:USE_C4_MODEL_TECHNIQUES&lt;/code&gt; — &lt;code dir=&quot;auto&quot;&gt;agent_profile:diagram-daisy&lt;/code&gt; requires it
directly (the slug-hub directive; its store slug &lt;code dir=&quot;auto&quot;&gt;use-c4-model-techniques&lt;/code&gt; now
normalizes to this node URN via the &lt;code dir=&quot;auto&quot;&gt;id_normalizer&lt;/code&gt; hyphen→underscore fix).&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;styleguide:quadruple-a-test-format&lt;/code&gt; — via &lt;code dir=&quot;auto&quot;&gt;agent_profile:generic-agent&lt;/code&gt; →
&lt;code dir=&quot;auto&quot;&gt;directive:DIRECTIVE_041&lt;/code&gt; —&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;—&gt; the styleguide.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:writing-audience-catalog&lt;/code&gt; — &lt;code dir=&quot;auto&quot;&gt;agent_profile:comms-cleo&lt;/code&gt; reaches it directly.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The other ten of the seventeen are unreachable from &lt;strong&gt;both&lt;/strong&gt; channels and are
recorded as tracked #3009 debt (added to &lt;code dir=&quot;auto&quot;&gt;_PROFILE_UNREACHABLE&lt;/code&gt;), to be wired with
real inbound edges by the deferred orphan-wiring doctrine mission — they are NOT
rescues and carry no ledger row here. (&lt;code dir=&quot;auto&quot;&gt;directive:RECONCILE_CHANGE_SCOPE_TENSIONS&lt;/code&gt;
is one of the ten: it is wired only by hand-authored &lt;code dir=&quot;auto&quot;&gt;reconciles_tension&lt;/code&gt; overlay
edges the profile channel does not walk.)&lt;/p&gt;
&lt;h3 id=&quot;mission-drg-reachability-metric-wiring-01kzs5vr-wp01-3009-point-3--profile-channel-rescue-1---10&quot;&gt;Mission &lt;code dir=&quot;auto&quot;&gt;drg-reachability-metric-wiring-01KZS5VR&lt;/code&gt; (WP01, #3009 point 3) — profile-channel rescue +1 / -10&lt;/h3&gt;
&lt;p&gt;Six genuine traced edges land (&lt;code dir=&quot;auto&quot;&gt;_CURATED_ARTIFACT_EDGES&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;src/doctrine/drg/migration/extractor.py&lt;/code&gt;
— see the companion-metric section near the end of this document for the full
edge table). Two members move the profile-channel pins:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;_PROFILE_UNREACHABLE&lt;/code&gt; 62 → 60&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;-2&lt;/code&gt;). &lt;code dir=&quot;auto&quot;&gt;directive:RECONCILE_CHANGE_SCOPE_TENSIONS&lt;/code&gt;
becomes profile-reachable via &lt;code dir=&quot;auto&quot;&gt;directive:DIRECTIVE_024 --suggests--&gt; RECONCILE&lt;/code&gt;
and &lt;code dir=&quot;auto&quot;&gt;directive:DIRECTIVE_025 --suggests--&gt; RECONCILE&lt;/code&gt; (both 024/025 are
themselves profile-reachable, so the closure reaches RECONCILE). &lt;code dir=&quot;auto&quot;&gt;procedure: glossary-maintenance-workflow&lt;/code&gt; becomes profile-reachable via
&lt;code dir=&quot;auto&quot;&gt;agent_profile:lexical-larry --suggests--&gt; glossary-maintenance-workflow&lt;/code&gt;
(larry is a profile-channel seed).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;_PROFILE_RESCUES&lt;/code&gt; 37 → 28&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;-10&lt;/code&gt; leave, &lt;code dir=&quot;auto&quot;&gt;+1&lt;/code&gt; enters). TEN members leave:
&lt;code dir=&quot;auto&quot;&gt;tactic:mutation-testing-workflow&lt;/code&gt;, the seven &lt;code dir=&quot;auto&quot;&gt;refactoring-*&lt;/code&gt; Fowler tactics
(&lt;code dir=&quot;auto&quot;&gt;tactic:refactoring-encapsulate-record&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic:refactoring-encapsulate-variable&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;tactic:refactoring-extract-first-order-concept&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic:refactoring-move-field&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;tactic:refactoring-move-method&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic:refactoring-state-pattern-for-behavior&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;tactic:refactoring-strangler-fig&lt;/code&gt;) and &lt;code dir=&quot;auto&quot;&gt;toolguide:python-mutation-tools&lt;/code&gt; /
&lt;code dir=&quot;auto&quot;&gt;toolguide:typescript-mutation-tools&lt;/code&gt; all became action-&lt;code dir=&quot;auto&quot;&gt;d=2&lt;/code&gt;-reachable (the
new &lt;code dir=&quot;auto&quot;&gt;procedure:refactoring --suggests--&gt; directive:DISCIPLINED_REFACTORING&lt;/code&gt;
and &lt;code dir=&quot;auto&quot;&gt;directive:DIRECTIVE_030 --suggests--&gt; directive:USE_MUTATION_TESTING_TO_ VALIDATE_TEST_QUALITY&lt;/code&gt; edges cascade their tactic families into the action
channel at the bootstrap depth), so the action channel now covers them and
they leave the profile-only rescue set. ONE member enters:
&lt;code dir=&quot;auto&quot;&gt;procedure:glossary-maintenance-workflow&lt;/code&gt; (see above) — it stays
action-&lt;code dir=&quot;auto&quot;&gt;d=2&lt;/code&gt;-unreachable but is now profile-reachable, so it moves from
&lt;code dir=&quot;auto&quot;&gt;_PROFILE_UNREACHABLE&lt;/code&gt; into &lt;code dir=&quot;auto&quot;&gt;_PROFILE_RESCUES&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;directive:RECONCILE_CHANGE_SCOPE_TENSIONS&lt;/code&gt; leaves BOTH &lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_D2&lt;/code&gt;
and &lt;code dir=&quot;auto&quot;&gt;_PROFILE_UNREACHABLE&lt;/code&gt; (it is reachable at both depths via edges 2/3 — see
the companion-metric section), so it does &lt;strong&gt;not&lt;/strong&gt; enter &lt;code dir=&quot;auto&quot;&gt;_PROFILE_RESCUES&lt;/code&gt;
(defined as the set difference of the two).&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;composition-ledger-nfr-004--counts-this-wp-moves&quot;&gt;Composition ledger (NFR-004) — counts this WP moves&lt;/h2&gt;
&lt;p&gt;The single authored edge moves these counts. Each is recorded so no golden
number moves silently.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Shipped-graph edges 781 → 782&lt;/strong&gt; (+1). &lt;code dir=&quot;auto&quot;&gt;len(HAND_AUTHORED_EDGES)&lt;/code&gt; 17 → 18. The
pure-extraction golden counts (&lt;code dir=&quot;auto&quot;&gt;_EXPECTED_NODE_COUNT=304&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;_EXPECTED_EDGE_COUNT=764&lt;/code&gt;)
are &lt;strong&gt;unchanged&lt;/strong&gt; — the edge is overlay-authored, not extractor-derived — so
&lt;code dir=&quot;auto&quot;&gt;test_extractor_projection&lt;/code&gt;’s byte-identical assertion (&lt;code dir=&quot;auto&quot;&gt;… == _EXPECTED_EDGE_COUNT + len(HAND_AUTHORED_EDGES)&lt;/code&gt;)
stays green by construction once the fragments are regenerated. Ledger entry (8)
is added to that module’s composition ledger.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;scope&lt;/code&gt;-relation histogram 157 → 158.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;RELATION_DESCRIPTIONS[Relation.SCOPE]&lt;/code&gt;
(&lt;code dir=&quot;auto&quot;&gt;doctrine.drg.models&lt;/code&gt;) and its char-for-char mirror in
&lt;code dir=&quot;auto&quot;&gt;docs/architecture/doctrine-relationships.md&lt;/code&gt; state “(157 edges)”; both move to
“(158 edges)”. This count &lt;strong&gt;is&lt;/strong&gt; gated —
&lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_no_authored_applies_edge.py::TestPositiveCountClaimsAreTrue&lt;/code&gt;
parses the claim and asserts it against the live graph — so the prose is a
contract, updated here, not left to drift.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_D1&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_D2&lt;/code&gt;&lt;/strong&gt; (WP08,
&lt;code dir=&quot;auto&quot;&gt;tests/doctrine/drg/test_reachability.py&lt;/code&gt;) each &lt;strong&gt;lose the same 6 members&lt;/strong&gt;:
&lt;code dir=&quot;auto&quot;&gt;directive:DIRECTIVE_042&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;styleguide:common-docs&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;tactic:common-docs-curation&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic:common-docs-find&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;tactic:common-docs-scaffold&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic:common-docs-write&lt;/code&gt;. The &lt;code dir=&quot;auto&quot;&gt;d1↔d2&lt;/code&gt; spread
stays 7 (same members removed from both); &lt;code dir=&quot;auto&quot;&gt;_PROFILE_UNREACHABLE&lt;/code&gt; and
&lt;code dir=&quot;auto&quot;&gt;_PROFILE_RESCUES&lt;/code&gt; are unaffected (the profile channel is unchanged, and the 6
are profile-unreachable too). Orphan sets are unaffected (042 and the asset were
already edge-incident). Ledgered in that module’s docstring.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;composition-ledger-nfr-004--family-a-3063-ddd-family&quot;&gt;Composition ledger (NFR-004) — Family A (#3063 DDD family)&lt;/h2&gt;
&lt;p&gt;Fourteen authored edges. Each moved count is recorded so no golden number moves
silently.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Shipped-graph edges 782 → 796&lt;/strong&gt; (+14). &lt;code dir=&quot;auto&quot;&gt;len(HAND_AUTHORED_EDGES)&lt;/code&gt; 18 → 32. The
pure-extraction golden counts (&lt;code dir=&quot;auto&quot;&gt;_EXPECTED_NODE_COUNT=304&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;_EXPECTED_EDGE_COUNT=764&lt;/code&gt;)
are &lt;strong&gt;unchanged&lt;/strong&gt; — all fourteen are overlay-authored — so
&lt;code dir=&quot;auto&quot;&gt;test_extractor_projection&lt;/code&gt;’s byte-identical assertion stays green once the
fragments are regenerated (&lt;code dir=&quot;auto&quot;&gt;764 + 32 = 796&lt;/code&gt;). Ledger entry (9) is added to that
module’s composition ledger.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Relation histogram&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt; 262 → 272 (+10 paradigm→member edges),
&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; 337 → 340 (+3 profile→paradigm edges), &lt;code dir=&quot;auto&quot;&gt;scope&lt;/code&gt; 158 → 159 (+1 reaching
edge). All three are gated by
&lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_no_authored_applies_edge.py::TestPositiveCountClaimsAreTrue&lt;/code&gt;
and mirrored char-for-char in &lt;code dir=&quot;auto&quot;&gt;RELATION_DESCRIPTIONS&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;doctrine.drg.models&lt;/code&gt;) and
&lt;code dir=&quot;auto&quot;&gt;docs/architecture/doctrine-relationships.md&lt;/code&gt;; all updated.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_D1&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_D2&lt;/code&gt;&lt;/strong&gt; each &lt;strong&gt;lose the same 12
members&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;paradigm:domain-driven-design&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;directive:DIRECTIVE_031&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;directive:DIRECTIVE_032&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;styleguide:aggregate-design-rules&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;tactic:aggregate-boundary-design&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic:anti-corruption-layer&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;tactic:bounded-context-canvas-fill&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic:bounded-context-identification&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;tactic:context-boundary-inference&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic:context-mapping-classification&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;tactic:domain-event-capture&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic:entity-value-object-classification&lt;/code&gt;. The
&lt;code dir=&quot;auto&quot;&gt;d1↔d2&lt;/code&gt; spread stays 7 (same members removed from both).
&lt;code dir=&quot;auto&quot;&gt;tactic:strategic-domain-classification&lt;/code&gt; was already reachable, so it moves no
pin.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;_PROFILE_UNREACHABLE&lt;/code&gt; unchanged&lt;/strong&gt; (profile channel measured 39→39). &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;_PROFILE_RESCUES&lt;/code&gt;
loses 4&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;directive:DIRECTIVE_031&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;directive:DIRECTIVE_032&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;tactic:anti-corruption-layer&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic:domain-event-capture&lt;/code&gt;) — the action
channel now covers them, so they are no longer profile-only rescues.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Orphan sets unaffected&lt;/strong&gt; — every one of the 14 endpoints was already
edge-incident.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Deferred set 72 → 60&lt;/strong&gt; (directive 6→4, paradigm 5→4, styleguide 5→4, tactic
43→35; procedure 5 and toolguide 8 unchanged).&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;family-b-3063-refactoring-family--operator-interview-outcome-inert-composition-only&quot;&gt;Family B (#3063 REFACTORING family) — operator interview outcome, INERT (composition-only)&lt;/h2&gt;
&lt;p&gt;The #3063 operator interview ATTESTED a REFACTORING family (C-007(a) satisfied by
operator ruling). Its hub is a &lt;strong&gt;NEW built-in directive&lt;/strong&gt;,
&lt;code dir=&quot;auto&quot;&gt;directive:DISCIPLINED_REFACTORING&lt;/code&gt;
(&lt;code dir=&quot;auto&quot;&gt;src/doctrine/directives/built-in/disciplined-refactoring.directive.yaml&lt;/code&gt;):
disciplined, behaviour-preserving refactoring — refactor in small steps under
green tests, name the smell before the move, one transformation at a time,
structural moves kept separate from behaviour changes. No equivalent directive
existed (&lt;code dir=&quot;auto&quot;&gt;grep -ri refactor src/doctrine/directives/&lt;/code&gt; found only the
&lt;code dir=&quot;auto&quot;&gt;reconcile-change-scope-tensions&lt;/code&gt; tension directive, which is unrelated).&lt;/p&gt;
&lt;h3 id=&quot;️-urn-casing-relationid-correction&quot;&gt;⚠️ URN casing (relation/id correction)&lt;/h3&gt;
&lt;p&gt;The wiring instruction named the hub &lt;code dir=&quot;auto&quot;&gt;directive:disciplined-refactoring&lt;/code&gt;
(lower-kebab). A directive node’s URN is derived from its artifact &lt;code dir=&quot;auto&quot;&gt;id&lt;/code&gt;, and the
&lt;code dir=&quot;auto&quot;&gt;Directive&lt;/code&gt; model requires &lt;code dir=&quot;auto&quot;&gt;id&lt;/code&gt; to match &lt;code dir=&quot;auto&quot;&gt;^[A-Z][A-Z0-9_-]*$&lt;/code&gt; while
&lt;code dir=&quot;auto&quot;&gt;doctrine.drg.migration.id_normalizer.normalize_directive_id&lt;/code&gt; upper-cases any
non-numeric slug — so the only URN a real directive artifact can yield is
&lt;code dir=&quot;auto&quot;&gt;directive:DISCIPLINED_REFACTORING&lt;/code&gt;, exactly the
&lt;code dir=&quot;auto&quot;&gt;directive:RECONCILE_CHANGE_SCOPE_TENSIONS&lt;/code&gt; precedent. The lower-kebab form is
unreachable through the schema; the canonical URN is UPPER_SNAKE, corrected here.&lt;/p&gt;
&lt;h3 id=&quot;the-14-authored-edges-all-suggests-all-inert-under-todays-traversal&quot;&gt;The 14 authored edges (all &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;, all INERT under today’s traversal)&lt;/h3&gt;
&lt;p&gt;The 7 directive→tactic edges each carry a per-tactic &lt;code dir=&quot;auto&quot;&gt;when&lt;/code&gt; = the tactic’s own
attested applicability (the “problem” it solves), derived from the tactic’s own
&lt;code dir=&quot;auto&quot;&gt;purpose&lt;/code&gt;/first-step text — &lt;strong&gt;not invented&lt;/strong&gt;:&lt;/p&gt;





























































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;#&lt;/th&gt;&lt;th&gt;source&lt;/th&gt;&lt;th&gt;relation&lt;/th&gt;&lt;th&gt;target&lt;/th&gt;&lt;th&gt;&lt;code dir=&quot;auto&quot;&gt;when&lt;/code&gt; (grounded in the tactic’s own text)&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;B1&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;directive:DISCIPLINED_REFACTORING&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:refactoring-encapsulate-record&lt;/code&gt;&lt;/td&gt;&lt;td&gt;a raw data record (dict/plain object/mutable named tuple) is accessed by field name from many call sites, blocking validation, renames, or a change of representation&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;B2&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;directive:DISCIPLINED_REFACTORING&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:refactoring-encapsulate-variable&lt;/code&gt;&lt;/td&gt;&lt;td&gt;a widely-accessed module-level/global variable (or public attribute) is read and written from many locations and needs a single chokepoint for validation, monitoring, or a later type change&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;B3&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;directive:DISCIPLINED_REFACTORING&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:refactoring-extract-first-order-concept&lt;/code&gt;&lt;/td&gt;&lt;td&gt;an important concept is implicit, duplicated, or scattered with no explicit name or single home&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;B4&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;directive:DISCIPLINED_REFACTORING&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:refactoring-move-field&lt;/code&gt;&lt;/td&gt;&lt;td&gt;a field is read/modified more by another class than the one that declares it, so data ownership has drifted&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;B5&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;directive:DISCIPLINED_REFACTORING&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:refactoring-move-method&lt;/code&gt;&lt;/td&gt;&lt;td&gt;a method uses more of another class’s data and behaviour than its own host’s (feature envy)&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;B6&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;directive:DISCIPLINED_REFACTORING&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:refactoring-state-pattern-for-behavior&lt;/code&gt;&lt;/td&gt;&lt;td&gt;a class’s methods are full of conditionals branching on the same internal state variable, and behaviour is driven by lifecycle state transitions&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;B7&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;directive:DISCIPLINED_REFACTORING&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:refactoring-strangler-fig&lt;/code&gt;&lt;/td&gt;&lt;td&gt;a legacy component/path must be replaced incrementally — new alongside old, rerouting callers one at a time — because a single-step cutover is too risky&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;The 7 profile→directive edges all share &lt;code dir=&quot;auto&quot;&gt;when&lt;/code&gt; = &lt;em&gt;“when tidying code, encountering
long classes/methods, or discovering convoluted logic”&lt;/em&gt;. The &lt;strong&gt;implementer-role
profiles&lt;/strong&gt; are every built-in profile whose role is &lt;code dir=&quot;auto&quot;&gt;implementer&lt;/code&gt; (resolved via
&lt;code dir=&quot;auto&quot;&gt;spec-kitty agent profile list&lt;/code&gt;; python-pedro is the primary):&lt;/p&gt;





















































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;#&lt;/th&gt;&lt;th&gt;source (role: implementer)&lt;/th&gt;&lt;th&gt;relation&lt;/th&gt;&lt;th&gt;target&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;B8&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;agent_profile:frontend-freddy&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;directive:DISCIPLINED_REFACTORING&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;B9&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;agent_profile:generic-agent&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;directive:DISCIPLINED_REFACTORING&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;B10&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;agent_profile:implementer-ivan&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;directive:DISCIPLINED_REFACTORING&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;B11&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;agent_profile:java-jenny&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;directive:DISCIPLINED_REFACTORING&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;B12&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;agent_profile:node-norris&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;directive:DISCIPLINED_REFACTORING&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;B13&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;agent_profile:python-pedro&lt;/code&gt; (primary)&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;directive:DISCIPLINED_REFACTORING&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;B14&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;agent_profile:randy-reducer&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;directive:DISCIPLINED_REFACTORING&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;h3 id=&quot;why-family-b-is-inert--measured-not-assumed-wp08-helper-r-1&quot;&gt;Why Family B is INERT — measured, not assumed (WP08 helper, R-1)&lt;/h3&gt;
&lt;p&gt;All 14 edges are inert under today’s traversal:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The &lt;strong&gt;directive is not charter-activated&lt;/strong&gt; in this project, so it never enters
the &lt;code dir=&quot;auto&quot;&gt;_activated()&lt;/code&gt; universe the reachability pins subtract from — a new
unactivated built-in directive cannot join &lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_*&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;The &lt;strong&gt;profile→directive&lt;/strong&gt; edges are &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;; the profile channel walks
&lt;code dir=&quot;auto&quot;&gt;{requires, specializes_from}&lt;/code&gt; only, so it never follows them.&lt;/li&gt;
&lt;li&gt;The &lt;strong&gt;directive→tactic&lt;/strong&gt; edges are only reachable if the directive is
action-reachable, which it is &lt;strong&gt;not&lt;/strong&gt; (no action scopes it; it is reached only
via the inert profile edges). &lt;code dir=&quot;auto&quot;&gt;resolve_context&lt;/code&gt; walks &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; only &lt;em&gt;from&lt;/em&gt;
scope-resolved artifacts.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Measured before/after the edges landed with &lt;code dir=&quot;auto&quot;&gt;resolve_context&lt;/code&gt; via the WP08 helper:
&lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_D1&lt;/code&gt; (67), &lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_D2&lt;/code&gt; (60), &lt;code dir=&quot;auto&quot;&gt;_PROFILE_UNREACHABLE&lt;/code&gt;
(153) and &lt;code dir=&quot;auto&quot;&gt;_PROFILE_RESCUES&lt;/code&gt; (the same 4) are &lt;strong&gt;UNCHANGED&lt;/strong&gt;. Family B moves &lt;strong&gt;no&lt;/strong&gt;
reachability pin — only composition counts.&lt;/p&gt;
&lt;p&gt;The seven refactoring tactics therefore &lt;strong&gt;remain in the DEFERRED set above&lt;/strong&gt; —
&lt;em&gt;topology authored, delivery pending fast-follow&lt;/em&gt;. Their delivery needs the
profile-channel walk to follow &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; (or the directive to be
action-scoped); that is a traversal-policy decision for the operator, not edge
authoring, so they are not action-reachable yet.&lt;/p&gt;
&lt;h3 id=&quot;pending-anti-pattern-authoring-companion-not-authored-here&quot;&gt;Pending anti-pattern-authoring companion (NOT authored here)&lt;/h3&gt;
&lt;p&gt;The operator flagged that the &lt;code dir=&quot;auto&quot;&gt;anti_pattern&lt;/code&gt; kind — the code smells that are the
“problem” each refactor solves — is sensible to author for this family (smell →
refactor, i.e. &lt;code dir=&quot;auto&quot;&gt;anti_pattern --…--&gt; tactic:refactoring-*&lt;/code&gt;). That is
doctrine-CONTENT authoring, &lt;strong&gt;deferred to the fast-follow decision&lt;/strong&gt; and &lt;strong&gt;not
authored in this pass&lt;/strong&gt;. Recorded here as a known companion so it is not lost.&lt;/p&gt;
&lt;h2 id=&quot;composition-ledger-nfr-004--family-b-3063-refactoring-family&quot;&gt;Composition ledger (NFR-004) — Family B (#3063 REFACTORING family)&lt;/h2&gt;
&lt;p&gt;One new directive node (via extraction) + fourteen &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; overlay edges. Each
moved count is recorded so no golden number moves silently.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Shipped-graph nodes 310 → 311&lt;/strong&gt; (+1). The directive is a real
&lt;code dir=&quot;auto&quot;&gt;*.directive.yaml&lt;/code&gt;, so the extractor mints its node: pure golden
&lt;code dir=&quot;auto&quot;&gt;_EXPECTED_NODE_COUNT&lt;/code&gt; &lt;strong&gt;304 → 305&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;test_extractor_projection&lt;/code&gt;). It carries
&lt;strong&gt;no inline references&lt;/strong&gt; (relationships are edges), so it mints &lt;strong&gt;zero&lt;/strong&gt;
extractor edges — &lt;code dir=&quot;auto&quot;&gt;_EXPECTED_EDGE_COUNT&lt;/code&gt; stays &lt;strong&gt;764&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Shipped-graph edges 796 → 810&lt;/strong&gt; (+14). &lt;code dir=&quot;auto&quot;&gt;len(HAND_AUTHORED_EDGES)&lt;/code&gt; &lt;strong&gt;32 → 46&lt;/strong&gt;.
&lt;code dir=&quot;auto&quot;&gt;test_shipped_graph_is_fresh_and_byte_identical&lt;/code&gt; stays green by construction
(&lt;code dir=&quot;auto&quot;&gt;764 + 46 = 810&lt;/code&gt;) once the fragments are regenerated. Ledger entry (10) is added
to that module’s composition ledger.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; relation histogram 340 → 354&lt;/strong&gt; (+14; all 14 edges are &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;).
&lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt; (272) and &lt;code dir=&quot;auto&quot;&gt;scope&lt;/code&gt; (159) are &lt;strong&gt;unchanged&lt;/strong&gt;. Gated by
&lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_no_authored_applies_edge.py::TestPositiveCountClaimsAreTrue&lt;/code&gt;
and mirrored char-for-char in &lt;code dir=&quot;auto&quot;&gt;RELATION_DESCRIPTIONS&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;doctrine.drg.models&lt;/code&gt;) and
&lt;code dir=&quot;auto&quot;&gt;docs/architecture/doctrine-relationships.md&lt;/code&gt;; both updated.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Orphan sets:&lt;/strong&gt; in a &lt;strong&gt;pure&lt;/strong&gt; regeneration the directive is an orphan (its only
edges are overlay-authored), so pure orphans &lt;strong&gt;23 → 24&lt;/strong&gt; — it joins
&lt;code dir=&quot;auto&quot;&gt;_AWAITING_REFERENCES&lt;/code&gt; (4 → 5) and &lt;code dir=&quot;auto&quot;&gt;_ORPHANS_RESOLVED_BY_OVERLAY&lt;/code&gt; (2 → 3). Shipped
orphans stay &lt;strong&gt;21&lt;/strong&gt; (the overlay wires it as both an edge source and target).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_D1&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;D2&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;_PROFILE_UNREACHABLE&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;_PROFILE_RESCUES&lt;/code&gt;
UNCHANGED&lt;/strong&gt; — Family B is inert (measured). No pin moves.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Deferred set unchanged at 60&lt;/strong&gt; — the seven refactoring tactics stay deferred
(topology authored, delivery pending); no artefact leaves the set.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;family-c-3063-architecture-docs--diagramming-family--operator-interview-outcome-inert-composition-only&quot;&gt;Family C (#3063 ARCHITECTURE-DOCS / DIAGRAMMING family) — operator interview outcome, INERT (composition-only)&lt;/h2&gt;
&lt;p&gt;The #3063 operator interview ATTESTED an ARCHITECTURE-DOCS / DIAGRAMMING family
(C-007(a) satisfied by operator ruling). Its hub is a &lt;strong&gt;NEW built-in directive&lt;/strong&gt;,
&lt;code dir=&quot;auto&quot;&gt;directive:USE_C4_MODEL_TECHNIQUES&lt;/code&gt;
(&lt;code dir=&quot;auto&quot;&gt;src/doctrine/directives/built-in/use-c4-model-techniques.directive.yaml&lt;/code&gt;): use
the C4 model’s progressive zoom (System Context → Container → Component → Code) to
document and reason about architecture at the right level of detail; keep diagrams
as text-based, version-controlled diagram-as-code; drawn as an &lt;strong&gt;extensible hub&lt;/strong&gt;
for architecture-documentation techniques (further techniques wired in as they are
supplied). No equivalent directive existed (&lt;code dir=&quot;auto&quot;&gt;grep -ri &quot;c4\|architecture.*model\|diagram&quot; src/doctrine/directives/&lt;/code&gt;
found none).&lt;/p&gt;
&lt;h3 id=&quot;️-urn-casing-relationid-correction-same-rule-as-family-b&quot;&gt;⚠️ URN casing (relation/id correction, same rule as Family B)&lt;/h3&gt;
&lt;p&gt;The wiring named the hub &lt;code dir=&quot;auto&quot;&gt;directive:use-c4-model-techniques&lt;/code&gt; (lower-kebab). A
directive node’s URN is derived from its artifact &lt;code dir=&quot;auto&quot;&gt;id&lt;/code&gt;, and the &lt;code dir=&quot;auto&quot;&gt;Directive&lt;/code&gt; model
requires &lt;code dir=&quot;auto&quot;&gt;id&lt;/code&gt; to match &lt;code dir=&quot;auto&quot;&gt;^[A-Z][A-Z0-9_-]*$&lt;/code&gt; while
&lt;code dir=&quot;auto&quot;&gt;id_normalizer.normalize_directive_id&lt;/code&gt; upper-cases any non-numeric slug — so the
only URN a real directive artifact can yield is &lt;code dir=&quot;auto&quot;&gt;directive:USE_C4_MODEL_TECHNIQUES&lt;/code&gt;
(the &lt;code dir=&quot;auto&quot;&gt;DISCIPLINED_REFACTORING&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;RECONCILE_CHANGE_SCOPE_TENSIONS&lt;/code&gt; precedent). The
lower-kebab form is unreachable through the schema; the canonical URN is UPPER_SNAKE.&lt;/p&gt;
&lt;h3 id=&quot;the-9-authored-edges-all-suggests-all-inert-under-todays-traversal&quot;&gt;The 9 authored edges (all &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;, all INERT under today’s traversal)&lt;/h3&gt;
&lt;p&gt;The 7 directive→member edges each carry a per-member &lt;code dir=&quot;auto&quot;&gt;when&lt;/code&gt; = the member’s own
attested applicability, derived from the member’s own &lt;code dir=&quot;auto&quot;&gt;purpose&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;scope&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;summary&lt;/code&gt;
text — &lt;strong&gt;not invented&lt;/strong&gt;:&lt;/p&gt;





























































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;#&lt;/th&gt;&lt;th&gt;source&lt;/th&gt;&lt;th&gt;relation&lt;/th&gt;&lt;th&gt;target&lt;/th&gt;&lt;th&gt;&lt;code dir=&quot;auto&quot;&gt;when&lt;/code&gt; (grounded in the member’s own text)&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;C1&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;directive:USE_C4_MODEL_TECHNIQUES&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;paradigm:c4-incremental-detail-modeling&lt;/code&gt;&lt;/td&gt;&lt;td&gt;communicating architecture to more than one audience at more than one level of detail, so it must be broken into progressive zoom levels rather than a single all-in-one diagram&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;C2&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;directive:USE_C4_MODEL_TECHNIQUES&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:c4-zoom-in-architecture-documentation&lt;/code&gt;&lt;/td&gt;&lt;td&gt;actually drawing the diagrams — starting from the System Context and zooming in to Container and Component levels only where detail adds value&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;C3&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;directive:USE_C4_MODEL_TECHNIQUES&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:architecture-diagram-review-checklist&lt;/code&gt;&lt;/td&gt;&lt;td&gt;an architecture diagram is about to be shared/committed and must be understandable without a verbal walkthrough&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;C4&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;directive:USE_C4_MODEL_TECHNIQUES&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;toolguide:mermaid-diagramming&lt;/code&gt;&lt;/td&gt;&lt;td&gt;rendering the diagrams as text-based, version-controlled diagram-as-code in Mermaid&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;C5&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;directive:USE_C4_MODEL_TECHNIQUES&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;toolguide:plantuml-diagramming&lt;/code&gt;&lt;/td&gt;&lt;td&gt;rendering the diagrams as text-based, version-controlled diagram-as-code in PlantUML&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;C6&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;directive:USE_C4_MODEL_TECHNIQUES&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;procedure:drill-down-documentation&lt;/code&gt;&lt;/td&gt;&lt;td&gt;capturing decisions/architecture at a consistent abstraction level (org → arch → design → code) with upward/downward traceability, rather than mixing levels in one artifact&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;C7&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;directive:USE_C4_MODEL_TECHNIQUES&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:code-documentation-analysis&lt;/code&gt;&lt;/td&gt;&lt;td&gt;reverse-engineering or reviewing an existing system’s architecture — extracting terminology from code and docs to surface implicit context boundaries before documenting them&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;The reinforcement (“supporting”) bridge and the profile edge:&lt;/p&gt;


























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;#&lt;/th&gt;&lt;th&gt;source&lt;/th&gt;&lt;th&gt;relation&lt;/th&gt;&lt;th&gt;target&lt;/th&gt;&lt;th&gt;&lt;code dir=&quot;auto&quot;&gt;when&lt;/code&gt; / note&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;C8&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;directive:USE_C4_MODEL_TECHNIQUES&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;paradigm:domain-driven-design&lt;/code&gt;&lt;/td&gt;&lt;td&gt;the architecture is organised around a domain model, so its container/component boundaries should reflect bounded contexts and the ubiquitous language — the attested DDD-reinforcement leg&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;C9&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;agent_profile:architect-alphonso&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;directive:USE_C4_MODEL_TECHNIQUES&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;when&lt;/code&gt; = “documenting or reviewing system architecture” (alphonso’s attested scope)&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;h3 id=&quot;the-supporting-relation-and-the-documentation-paradigm--what-was-found&quot;&gt;The “supporting” relation and “the documentation paradigm” — what was found&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Relation for “supporting/reinforces”:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;Relation&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;src/doctrine/drg/models.py&lt;/code&gt;)
offers no dedicated support/reinforce member. The closest &lt;strong&gt;attested&lt;/strong&gt; relation is
&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; (a directional, soft, non-mandatory pointer) — used for C8. &lt;strong&gt;No new
relation kind was invented&lt;/strong&gt; (the “defer/report instead of invent” guard).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;“The documentation paradigm”:&lt;/strong&gt; there is &lt;strong&gt;no distinct documentation paradigm
node&lt;/strong&gt;. &lt;code dir=&quot;auto&quot;&gt;paradigm:c4-incremental-detail-modeling&lt;/code&gt; &lt;strong&gt;IS&lt;/strong&gt; the documentation /
architecture-modelling paradigm, and it is already a hub member (edge C1). So the
“documentation” leg of “supporting the documentation and DDD paradigms” is covered
by C1, and &lt;strong&gt;only the DDD-bridge leg (C8) is added&lt;/strong&gt; as a separate edge. This is
what was found and done.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;attestation-audit--what-was-excluded-as-non-attested-1&quot;&gt;Attestation audit — what was EXCLUDED as non-attested&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;procedure:documentation-gap-prioritization&lt;/code&gt; — a #3063 candidate member, but its
own text triages documentation &lt;strong&gt;gaps&lt;/strong&gt; by user impact across ALL doc types
(tutorials, how-to, reference, explanation). That is a documentation-project-
management technique, &lt;strong&gt;not&lt;/strong&gt; a C4 / architecture-documentation / diagramming one.
No member edge is authored for it; it stays in the DEFERRED set (plain, not
“topology authored”).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;why-family-c-is-inert--measured-not-assumed-wp08-helper-r-1&quot;&gt;Why Family C is INERT — measured, not assumed (WP08 helper, R-1)&lt;/h3&gt;
&lt;p&gt;All 9 edges are inert under today’s traversal:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The &lt;strong&gt;directive is not charter-activated&lt;/strong&gt; in this project, so it never enters the
&lt;code dir=&quot;auto&quot;&gt;_activated()&lt;/code&gt; universe the reachability pins subtract from — a new unactivated
built-in directive cannot join &lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_*&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;The &lt;strong&gt;directive→member&lt;/strong&gt; and &lt;strong&gt;directive→DDD&lt;/strong&gt; edges are &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;, and the
directive is scoped by no action, so &lt;code dir=&quot;auto&quot;&gt;resolve_context&lt;/code&gt; never reaches it and never
walks its outbound &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;. The seven members stay action-unreachable (they
already were).&lt;/li&gt;
&lt;li&gt;The &lt;strong&gt;C8 DDD-bridge&lt;/strong&gt; edge is INBOUND to &lt;code dir=&quot;auto&quot;&gt;paradigm:domain-driven-design&lt;/code&gt;, which
Family A already made action-reachable; a directive→paradigm edge does not make
the SOURCE reachable, so it delivers nothing new and moves no DDD pin either.&lt;/li&gt;
&lt;li&gt;The &lt;strong&gt;profile→directive (C9)&lt;/strong&gt; edge is &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;; the profile channel walks
&lt;code dir=&quot;auto&quot;&gt;{requires, specializes_from}&lt;/code&gt; only, so it never follows it.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Measured before/after with the WP08 helper: &lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_D1&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_D2&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;_PROFILE_UNREACHABLE&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;_PROFILE_RESCUES&lt;/code&gt; are
&lt;strong&gt;UNCHANGED&lt;/strong&gt;. Family C moves &lt;strong&gt;no&lt;/strong&gt; reachability pin — only composition counts.&lt;/p&gt;
&lt;p&gt;The seven architecture-doc technique members therefore &lt;strong&gt;remain in the DEFERRED set
above&lt;/strong&gt; — &lt;em&gt;topology authored, delivery pending fast-follow&lt;/em&gt;. Their delivery needs
the directive to be action-scoped (the canonical home would be a mission
step-contract action index), or the profile-channel walk to follow &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;; that
is a traversal-policy / scoping decision for the operator, not edge authoring.&lt;/p&gt;
&lt;h3 id=&quot;asset--template-assessment-operator-asked-specifically&quot;&gt;Asset / template assessment (operator asked specifically)&lt;/h3&gt;
&lt;p&gt;The mission’s asset surface (&lt;code dir=&quot;auto&quot;&gt;AssetRepository&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;doctrine asset&lt;/code&gt; commands,
&lt;code dir=&quot;auto&quot;&gt;*.asset.yaml&lt;/code&gt; manifests) was assessed for shippable architecture-doc
exemplars/templates. &lt;strong&gt;Finding: the exemplars already ship — as &lt;code dir=&quot;auto&quot;&gt;template&lt;/code&gt; artefacts,
not assets.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;src/doctrine/templates/architecture/&lt;/code&gt; already contains
&lt;code dir=&quot;auto&quot;&gt;c4-context-mermaid-template.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;c4-container-mermaid-template.md&lt;/code&gt; and
&lt;code dir=&quot;auto&quot;&gt;c4-component-mermaid-template.md&lt;/code&gt; (plus a broad &lt;code dir=&quot;auto&quot;&gt;templates/diagrams/{mermaid,plantuml}/&lt;/code&gt;
library), and the C4 zoom-in tactic already references them by id
(&lt;code dir=&quot;auto&quot;&gt;c4-context-mermaid-template&lt;/code&gt;, etc.). A text-based C4 context+container template is
therefore &lt;strong&gt;already self-contained and shipped in the correct kind&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;template&lt;/code&gt;, the
fill-in-the-blanks companion), so authoring a NEW &lt;code dir=&quot;auto&quot;&gt;*.asset.yaml&lt;/code&gt; would duplicate
existing canonical content in the wrong kind. &lt;strong&gt;Decision: author NO new asset.&lt;/strong&gt; The
asset kind is reserved for a loaded policy blob like &lt;code dir=&quot;auto&quot;&gt;common-docs-structural-lint&lt;/code&gt;
(a lint config the structural-lint gate loads), which is a different concern from a
fill-in exemplar. &lt;strong&gt;Recommendation for the fast-follow:&lt;/strong&gt; if the operator wants these
C4 templates &lt;em&gt;delivered&lt;/em&gt; to an agent’s context, wire the existing template nodes via
the C4 zoom-in tactic’s already-authored &lt;code dir=&quot;auto&quot;&gt;references:&lt;/code&gt; (a template &lt;code dir=&quot;auto&quot;&gt;instantiates&lt;/code&gt;
edge from the &lt;code dir=&quot;auto&quot;&gt;documentation/design&lt;/code&gt; action is the canonical delivery path) rather
than re-homing them as assets.&lt;/p&gt;
&lt;h2 id=&quot;composition-ledger-nfr-004--family-c-3063-architecture-docs-family&quot;&gt;Composition ledger (NFR-004) — Family C (#3063 ARCHITECTURE-DOCS family)&lt;/h2&gt;
&lt;p&gt;One new directive node (via extraction) + nine &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; overlay edges. Each moved
count is recorded so no golden number moves silently.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Shipped-graph nodes 311 → 312&lt;/strong&gt; (+1). The directive is a real &lt;code dir=&quot;auto&quot;&gt;*.directive.yaml&lt;/code&gt;,
so the extractor mints its node: pure golden &lt;code dir=&quot;auto&quot;&gt;_EXPECTED_NODE_COUNT&lt;/code&gt; &lt;strong&gt;305 → 306&lt;/strong&gt;
(&lt;code dir=&quot;auto&quot;&gt;test_extractor_projection&lt;/code&gt;). It carries &lt;strong&gt;no inline references&lt;/strong&gt;, so it mints
&lt;strong&gt;zero&lt;/strong&gt; extractor edges — &lt;code dir=&quot;auto&quot;&gt;_EXPECTED_EDGE_COUNT&lt;/code&gt; stays &lt;strong&gt;764&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Shipped-graph edges 810 → 819&lt;/strong&gt; (+9). &lt;code dir=&quot;auto&quot;&gt;len(HAND_AUTHORED_EDGES)&lt;/code&gt; &lt;strong&gt;46 → 55&lt;/strong&gt;.
&lt;code dir=&quot;auto&quot;&gt;test_shipped_graph_is_fresh_and_byte_identical&lt;/code&gt; stays green by construction
(&lt;code dir=&quot;auto&quot;&gt;764 + 55 = 819&lt;/code&gt;) once the fragments are regenerated. Ledger entry (11) is added to
that module’s composition ledger.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; relation histogram 354 → 363&lt;/strong&gt; (+9; all 9 edges are &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;).
&lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt; (272) and &lt;code dir=&quot;auto&quot;&gt;scope&lt;/code&gt; (159) are &lt;strong&gt;unchanged&lt;/strong&gt;. Gated by
&lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_no_authored_applies_edge.py::TestPositiveCountClaimsAreTrue&lt;/code&gt;
and mirrored char-for-char in &lt;code dir=&quot;auto&quot;&gt;RELATION_DESCRIPTIONS&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;doctrine.drg.models&lt;/code&gt;) and
&lt;code dir=&quot;auto&quot;&gt;docs/architecture/doctrine-relationships.md&lt;/code&gt;; both updated.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Orphan sets:&lt;/strong&gt; in a &lt;strong&gt;pure&lt;/strong&gt; regeneration the directive is an orphan (its only
edges are overlay-authored), so pure orphans &lt;strong&gt;24 → 25&lt;/strong&gt; — it joins
&lt;code dir=&quot;auto&quot;&gt;_AWAITING_REFERENCES&lt;/code&gt; (5 → 6) and &lt;code dir=&quot;auto&quot;&gt;_ORPHANS_RESOLVED_BY_OVERLAY&lt;/code&gt; (3 → 4). Shipped
orphans stay &lt;strong&gt;21&lt;/strong&gt; (the overlay wires it as both an edge source and target).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_D1&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;D2&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;_PROFILE_UNREACHABLE&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;_PROFILE_RESCUES&lt;/code&gt;
UNCHANGED&lt;/strong&gt; — Family C is inert (measured). No pin moves.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Deferred set unchanged at 60&lt;/strong&gt; — the seven architecture-doc members stay deferred
(topology authored, delivery pending); &lt;code dir=&quot;auto&quot;&gt;documentation-gap-prioritization&lt;/code&gt; stays
deferred (excluded as non-attested); no artefact leaves the set.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;family-d-3063-testing--bdd--mutation-family--operator-interview-outcome-accept-delivery&quot;&gt;Family D (#3063 TESTING / BDD / MUTATION family) — operator interview outcome, ACCEPT DELIVERY&lt;/h2&gt;
&lt;p&gt;Unlike Families B and C (inert, composition-only), the operator ruled &lt;strong&gt;ACCEPT
DELIVERY&lt;/strong&gt; for Family D (2026-07-29). Family D is &lt;strong&gt;reachability-affecting&lt;/strong&gt;: it
delivers the BDD + test-quality members at implement/review, and the pins move —
exactly as Family A did for DDD-at-specify.&lt;/p&gt;
&lt;h3 id=&quot;why-family-d-delivers-measured-not-assumed--wp08-helper-r-1&quot;&gt;Why Family D delivers (measured, not assumed — WP08 helper, R-1)&lt;/h3&gt;
&lt;p&gt;Two of the four hubs are &lt;strong&gt;existing directives already &lt;code dir=&quot;auto&quot;&gt;scope&lt;/code&gt;-linked from
actions&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;directive:DIRECTIVE_034&lt;/code&gt; (test-first-development) and
&lt;code dir=&quot;auto&quot;&gt;directive:DIRECTIVE_030&lt;/code&gt; (test-and-typecheck-quality-gate) are both scoped from
&lt;code dir=&quot;auto&quot;&gt;action:software-dev/implement&lt;/code&gt; &lt;strong&gt;and&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;action:software-dev/review&lt;/code&gt;.
&lt;code dir=&quot;auto&quot;&gt;resolve_context&lt;/code&gt; step 3 walks &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; &lt;strong&gt;from scope-resolved artifacts&lt;/strong&gt;, so a
&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; edge sourced at 034/030 &lt;strong&gt;is&lt;/strong&gt; followed and delivers its target. This
is the opposite of the Family-B/C pattern, where the hub was a &lt;strong&gt;new, non-scoped&lt;/strong&gt;
directive whose outbound &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; were never walked.&lt;/p&gt;
&lt;h3 id=&quot;the-five-new-artefacts&quot;&gt;The five new artefacts&lt;/h3&gt;



































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;artefact&lt;/th&gt;&lt;th&gt;kind&lt;/th&gt;&lt;th&gt;body&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;directive:USE_MUTATION_TESTING_TO_VALIDATE_TEST_QUALITY&lt;/code&gt;&lt;/td&gt;&lt;td&gt;directive (&lt;code dir=&quot;auto&quot;&gt;lenient-adherence&lt;/code&gt;)&lt;/td&gt;&lt;td&gt;mutation testing validates that tests constrain behaviour; a surviving mutant reveals a hollow assertion; score is a quality signal, not a target; run on the changed scope in review&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;styleguide:quadruple-a-test-format&lt;/code&gt;&lt;/td&gt;&lt;td&gt;styleguide (&lt;code dir=&quot;auto&quot;&gt;testing&lt;/code&gt;)&lt;/td&gt;&lt;td&gt;Arrange / Assumption-check / Act / Assert; the assumption check MAY precede Arrange when the default state already is the precondition&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;styleguide:given-when-then-authoring&lt;/code&gt;&lt;/td&gt;&lt;td&gt;styleguide (&lt;code dir=&quot;auto&quot;&gt;testing&lt;/code&gt;)&lt;/td&gt;&lt;td&gt;Given=precondition, When=single trigger, Then=observable outcome; one behaviour per scenario; domain language, declarative, runner-agnostic&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;toolguide:sonar&lt;/code&gt; (+ SONAR.md)&lt;/td&gt;&lt;td&gt;toolguide&lt;/td&gt;&lt;td&gt;SonarQube static analysis + quality gate; gate on NEW-code metrics; loopback-safe URLs (no forced HTTPS on 127.0.0.1)&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;toolguide:gherkin&lt;/code&gt; (+ GHERKIN.md)&lt;/td&gt;&lt;td&gt;toolguide&lt;/td&gt;&lt;td&gt;the Gherkin DSL only (Feature/Background/Scenario/Outline/Given-When-Then-And-But/Examples); explicitly NOT stack runners&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;h3 id=&quot;the-54-authored-edges-all-suggests&quot;&gt;The 54 authored edges (all &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;)&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;BDD/ATDD hub &lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_034&lt;/code&gt; → 7&lt;/strong&gt; (DELIVERS at implement/review): &lt;code dir=&quot;auto&quot;&gt;tactic:development-bdd&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic:atdd-adversarial-acceptance&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;paradigm:specification-by-example&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic:formalized-constraint-testing&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;procedure:example-mapping-workshop&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;styleguide:given-when-then-authoring&lt;/code&gt; (new), &lt;code dir=&quot;auto&quot;&gt;toolguide:gherkin&lt;/code&gt; (new).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Brownfield &lt;code dir=&quot;auto&quot;&gt;paradigm:brownfield-onboarding&lt;/code&gt; → 2&lt;/strong&gt; (DELIVERS at d=2 only, via a ≤2-hop suggests chain; &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; matches how brownfield already links its non-mandatory members): &lt;code dir=&quot;auto&quot;&gt;tactic:reverse-speccing&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic:test-to-system-reconstruction&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Mutation hub &lt;code dir=&quot;auto&quot;&gt;USE_MUTATION_TESTING_TO_VALIDATE_TEST_QUALITY&lt;/code&gt; → 4&lt;/strong&gt; (INERT — new non-scoped hub): &lt;code dir=&quot;auto&quot;&gt;tactic:mutation-testing-workflow&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;styleguide:mutation-aware-test-design&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;toolguide:python-mutation-tools&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;toolguide:typescript-mutation-tools&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Test-quality hub &lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_030&lt;/code&gt; → 5&lt;/strong&gt; (DELIVERS; the quality-BAR the gate enforces): &lt;code dir=&quot;auto&quot;&gt;tactic:adversarial-qa-handoff&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic:work-package-completion-validation&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;styleguide:testing-principles&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;styleguide:test-desiderata-and-boundaries&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;toolguide:sonar&lt;/code&gt; (new).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Test-quality hub &lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_041&lt;/code&gt; → 3&lt;/strong&gt; (INERT — 041 is NOT scope-linked from any action; the clarity/authoring side): &lt;code dir=&quot;auto&quot;&gt;tactic:test-readability-clarity-check&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic:zombies-tdd&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;styleguide:quadruple-a-test-format&lt;/code&gt; (new).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Profile → hub → 32&lt;/strong&gt; (INERT in the profile channel): 7 implementer-role profiles (frontend-freddy, generic-agent, implementer-ivan, java-jenny, node-norris, python-pedro, randy-reducer) each → {034, mutation, 030, 041}; reviewer-renata → {030, 041, mutation}; debugger-debbie → {mutation}.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Event-storming → 1&lt;/strong&gt; (INERT): &lt;code dir=&quot;auto&quot;&gt;agent_profile:architect-alphonso --suggests--&gt; procedure:event-storming-discovery&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;030-vs-041 split rationale:&lt;/strong&gt; 030 (the quality gate) heads the members that
define the &lt;em&gt;bar&lt;/em&gt; a suite must clear (QA handoff, WP-completion gates, the FIRST
testing principles, test desiderata/boundaries, Sonar). 041 (tests-as-scaffold)
heads the &lt;em&gt;clarity/authoring&lt;/em&gt; members (readability check, ZOMBIES increments, the
Quad-A single-behaviour skeleton). Because 030 is action-scoped and 041 is not,
the 030-headed members deliver and the 041-headed members stay deferred.&lt;/p&gt;
&lt;h3 id=&quot;event-storming--inert-by-design-ddd-cluster-member&quot;&gt;Event-storming — inert by design, DDD-cluster member&lt;/h3&gt;
&lt;p&gt;Event Storming is a DDD-cluster discovery procedure (Family A). The operator’s
earlier explicit guard keeps it &lt;strong&gt;out of the eager specify delivery&lt;/strong&gt; (context-
overload concern). Measured: &lt;code dir=&quot;auto&quot;&gt;paradigm:domain-driven-design --suggests--&gt; event-storming&lt;/code&gt; would deliver it at specify (DDD is scope-resolved since Family A
— reachable at d=1 and d=2), so it is attached instead via
&lt;code dir=&quot;auto&quot;&gt;agent_profile:architect-alphonso --suggests--&gt; procedure:event-storming-discovery&lt;/code&gt;,
which is &lt;strong&gt;INERT&lt;/strong&gt; (measured: not reachable at d=1 or d=2; the profile channel
walks requires/specializes_from only). It can be switched to paradigm-delivered
later if the operator wants it eager at specify.&lt;/p&gt;
&lt;h2 id=&quot;composition-ledger-nfr-004--family-d-3063-testing--bdd--mutation-family&quot;&gt;Composition ledger (NFR-004) — Family D (#3063 TESTING / BDD / MUTATION family)&lt;/h2&gt;
&lt;p&gt;Five new artefact nodes (via extraction) + 54 &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; overlay edges. Each moved
count is recorded so no golden number moves silently.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Shipped-graph nodes 312 → 317&lt;/strong&gt; (+5). All five are real &lt;code dir=&quot;auto&quot;&gt;*.directive.yaml&lt;/code&gt; /
&lt;code dir=&quot;auto&quot;&gt;*.styleguide.yaml&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;*.toolguide.yaml&lt;/code&gt;, so the extractor mints their nodes:
pure golden &lt;code dir=&quot;auto&quot;&gt;_EXPECTED_NODE_COUNT&lt;/code&gt; &lt;strong&gt;306 → 311&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;test_extractor_projection&lt;/code&gt;).
None carries inline references, so they mint &lt;strong&gt;zero&lt;/strong&gt; extractor edges —
&lt;code dir=&quot;auto&quot;&gt;_EXPECTED_EDGE_COUNT&lt;/code&gt; stays &lt;strong&gt;764&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Shipped-graph edges 819 → 873&lt;/strong&gt; (+54). &lt;code dir=&quot;auto&quot;&gt;len(HAND_AUTHORED_EDGES)&lt;/code&gt; &lt;strong&gt;55 → 109&lt;/strong&gt;.
&lt;code dir=&quot;auto&quot;&gt;test_shipped_graph_is_fresh_and_byte_identical&lt;/code&gt; stays green by construction
(&lt;code dir=&quot;auto&quot;&gt;764 + 109 = 873&lt;/code&gt;) once the fragments are regenerated. Ledger entry (12) is added
to that module’s composition ledger.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; relation histogram 363 → 417&lt;/strong&gt; (+54; all 54 edges are &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;).
&lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt; (272) and &lt;code dir=&quot;auto&quot;&gt;scope&lt;/code&gt; (159) are &lt;strong&gt;unchanged&lt;/strong&gt;. Gated by
&lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_no_authored_applies_edge.py::TestPositiveCountClaimsAreTrue&lt;/code&gt;
and mirrored char-for-char in &lt;code dir=&quot;auto&quot;&gt;RELATION_DESCRIPTIONS&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;doctrine.drg.models&lt;/code&gt;) and
&lt;code dir=&quot;auto&quot;&gt;docs/architecture/doctrine-relationships.md&lt;/code&gt;; both updated.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Orphan sets:&lt;/strong&gt; in a &lt;strong&gt;pure&lt;/strong&gt; regeneration all five new artefacts are orphans
(their only edges are overlay-authored), so pure orphans &lt;strong&gt;25 → 30&lt;/strong&gt; — they join
&lt;code dir=&quot;auto&quot;&gt;_AWAITING_REFERENCES&lt;/code&gt; (6 → 11) and &lt;code dir=&quot;auto&quot;&gt;_ORPHANS_RESOLVED_BY_OVERLAY&lt;/code&gt; (4 → 9). Shipped
orphans stay &lt;strong&gt;21&lt;/strong&gt; (the overlay wires every one of them).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_D1&lt;/code&gt; 67 → 60&lt;/strong&gt; (−7) and &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_D2&lt;/code&gt; 60 → 50&lt;/strong&gt;
(−10). D1 loses the seven delivered at the compact depth (from 034:
development-bdd, atdd-adversarial-acceptance, specification-by-example,
formalized-constraint-testing, example-mapping-workshop; from 030:
adversarial-qa-handoff, work-package-completion-validation). D2 loses those seven
&lt;strong&gt;plus&lt;/strong&gt; reverse-speccing, test-to-system-reconstruction (brownfield chain) and
mutation-aware-test-design (2-hop out of 030). &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;_ACTION_D1_D2_SPREAD&lt;/code&gt; 7 → 10&lt;/strong&gt;
(the three d=2-only members move into &lt;code dir=&quot;auto&quot;&gt;D1 − D2&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;_PROFILE_UNREACHABLE&lt;/code&gt; UNCHANGED at 153&lt;/strong&gt; (every family-D profile edge is
&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;, which the profile channel does not follow). &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;_PROFILE_RESCUES&lt;/code&gt; 4 → 2&lt;/strong&gt;
(development-bdd and reverse-speccing entered the action channel, so they are no
longer profile-only rescues; &lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_044&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;test-readability-clarity-check&lt;/code&gt;
remain). Ledgered in &lt;code dir=&quot;auto&quot;&gt;tests/doctrine/drg/test_reachability.py&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Deferred set 60 → 50&lt;/strong&gt; — ten members leave (the delivered artefacts, listed
above and dropped from the deferred list). The mutation-hub members
(mutation-testing-workflow, python/typescript-mutation-tools) and the 041 fan-out
(test-readability-clarity-check, zombies-tdd) stay deferred (topology authored,
delivery inert); &lt;code dir=&quot;auto&quot;&gt;documentation-gap-prioritization&lt;/code&gt; unaffected.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;family-e-3063-analysis--terminology--reasons-canvas-family--operator-interview-outcome-inert-topology-only&quot;&gt;Family E (#3063 ANALYSIS / TERMINOLOGY / REASONS-CANVAS family) — operator interview outcome, INERT (topology-only)&lt;/h2&gt;
&lt;p&gt;Like Families B and C (and unlike A and D), Family E is &lt;strong&gt;inert&lt;/strong&gt; — it moves no
reachability pin. The operator ATTESTED the relationships (C-007(a) satisfied by
operator ruling); each &lt;code dir=&quot;auto&quot;&gt;when&lt;/code&gt; is additionally grounded in the &lt;strong&gt;source
artefact’s own text&lt;/strong&gt; so a reviewer can verify it is not a topic-adjacency
invention. Family E authors &lt;strong&gt;no new artefact files&lt;/strong&gt; — every endpoint already
exists — so node count / &lt;code dir=&quot;auto&quot;&gt;_EXPECTED_NODE_COUNT&lt;/code&gt; stay unchanged and all nine edges
are overlay-authored &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;.&lt;/p&gt;
&lt;h3 id=&quot;the-9-authored-edges-all-suggests&quot;&gt;The 9 authored edges (all &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;)&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;E1 — reasons-canvas / SPDD&lt;/strong&gt; (1 edge). Operator ruling: link only the canvas
&lt;em&gt;writing&lt;/em&gt; to alphonso, for now.&lt;/p&gt;



















&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;#&lt;/th&gt;&lt;th&gt;source&lt;/th&gt;&lt;th&gt;relation&lt;/th&gt;&lt;th&gt;target&lt;/th&gt;&lt;th&gt;&lt;code dir=&quot;auto&quot;&gt;when&lt;/code&gt; (grounded in both source texts)&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;E1&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;agent_profile:architect-alphonso&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;styleguide:reasons-canvas-writing&lt;/code&gt;&lt;/td&gt;&lt;td&gt;capturing the change-intent, decision boundaries and safeguards of a mission or significant architectural change as a REASONS Canvas — recording decisions with rationale, not mirroring code&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;Grounded in BOTH alphonso’s attested scope (architectural decisions documented
with rationale — DIRECTIVE_003, ADR/design outputs) AND the styleguide’s own
purpose (capture intent as Safeguard/Norm/Approach for a mission or change, not
mirror code). &lt;code dir=&quot;auto&quot;&gt;tactic:reasons-canvas-fill&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic:reasons-canvas-review&lt;/code&gt; and
&lt;code dir=&quot;auto&quot;&gt;paradigm:structured-prompt-driven-development&lt;/code&gt; are &lt;strong&gt;untouched&lt;/strong&gt; — they stay in
the deferred set per the operator.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;E2 group 1 — reinforcement into paradigms&lt;/strong&gt; (2 edges; member→paradigm, the
family-C “C8 DDD-bridge” precedent, so inert). Authored ONLY where the tactic’s
own text attests.&lt;/p&gt;


























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;#&lt;/th&gt;&lt;th&gt;source&lt;/th&gt;&lt;th&gt;relation&lt;/th&gt;&lt;th&gt;target&lt;/th&gt;&lt;th&gt;&lt;code dir=&quot;auto&quot;&gt;when&lt;/code&gt; (grounded in the tactic’s own text)&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;E2&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:terminology-extraction-mapping&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;paradigm:domain-driven-design&lt;/code&gt;&lt;/td&gt;&lt;td&gt;the extracted terms must be owned by a bounded context and cross-context uses translated at the boundary — the tactic’s own strategic-DDD ubiquitous-language / ACL text&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;E3&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:terminology-extraction-mapping&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;paradigm:brownfield-onboarding&lt;/code&gt;&lt;/td&gt;&lt;td&gt;recovering a shared vocabulary from an existing system’s code and documentation (follow-up to code-documentation-analysis) — brownfield’s own “terminology aliases inferred from the code” durable artefact&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;&lt;strong&gt;E2 group 2 — glossary / language links&lt;/strong&gt; (3 edges). The fourth implied edge is
a pre-existing extractor edge (see the exclusion audit) and is &lt;strong&gt;omitted&lt;/strong&gt;.&lt;/p&gt;

































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;#&lt;/th&gt;&lt;th&gt;source&lt;/th&gt;&lt;th&gt;relation&lt;/th&gt;&lt;th&gt;target&lt;/th&gt;&lt;th&gt;&lt;code dir=&quot;auto&quot;&gt;when&lt;/code&gt; (grounded in the source’s own text)&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;E4&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;toolguide:contextive&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:glossary-curation-interview&lt;/code&gt;&lt;/td&gt;&lt;td&gt;capturing a curation round’s terms in an enforceable, IDE-surfaced ubiquitous-language glossary (contextive’s own “manage ubiquitous language … alignment with glossary curation workflows”)&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;E5&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;toolguide:contextive&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:language-driven-design&lt;/code&gt;&lt;/td&gt;&lt;td&gt;treating terminology drift as an architectural signal — an IDE-surfaced glossary makes same-term/different-meaning conflicts visible&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;E6&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:terminology-extraction-mapping&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:glossary-curation-interview&lt;/code&gt;&lt;/td&gt;&lt;td&gt;feeding the extracted, validated terms into the HiC-led curation rounds (the tactic’s own purpose: build “the authoritative source for the project ubiquitous language”)&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;&lt;strong&gt;E2 group 3 — tools-support-tactics&lt;/strong&gt; (3 edges; toolguide→tactic).&lt;/p&gt;

































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;#&lt;/th&gt;&lt;th&gt;source&lt;/th&gt;&lt;th&gt;relation&lt;/th&gt;&lt;th&gt;target&lt;/th&gt;&lt;th&gt;&lt;code dir=&quot;auto&quot;&gt;when&lt;/code&gt; (grounded in the source’s own text)&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;E7&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;toolguide:terminology-guard&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:canonical-source-unification&lt;/code&gt;&lt;/td&gt;&lt;td&gt;enforcing single-canonical-authority at the commit level — the terminology instance of the tactic’s step-4 “add a gate to enforce the canonical route”; both cite DIRECTIVE_044&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;E8&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;toolguide:terminology-guard&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:occurrence-classification-workflow&lt;/code&gt;&lt;/td&gt;&lt;td&gt;verifying a classified bulk terminology change (a rename) is complete and stays complete — the guard fails CI if a superseded term reappears&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;E9&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;toolguide:contextive&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:terminology-extraction-mapping&lt;/code&gt;&lt;/td&gt;&lt;td&gt;capturing the extracted, bounded-context-owned terms in an enforceable Contextive glossary surfaced in the IDE&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;h3 id=&quot;attestation-audit--what-was-excluded-and-why&quot;&gt;Attestation audit — what was EXCLUDED and why&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:terminology-extraction-mapping --suggests--&gt; tactic:language-driven-design&lt;/code&gt; (group 2, the implied 4th edge) — OMITTED as a DUPLICATE.&lt;/strong&gt; It already
exists as an &lt;strong&gt;extractor-minted&lt;/strong&gt; edge, derived from terminology-extraction-mapping’s
own &lt;code dir=&quot;auto&quot;&gt;references:&lt;/code&gt; block (&lt;code dir=&quot;auto&quot;&gt;Language-Driven Design … Apply after the glossary is validated&lt;/code&gt;). Re-authoring it in the overlay would be a duplicate &lt;code dir=&quot;auto&quot;&gt;(source, relation, target)&lt;/code&gt;; the operator’s “avoid duplicate edges” rule applies.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Group 1 — &lt;code dir=&quot;auto&quot;&gt;canonical-source-unification&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;analysis-extract-before-interpret&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;occurrence-classification-workflow&lt;/code&gt; — NO paradigm edge.&lt;/strong&gt; None attests DDD or
brownfield in its &lt;strong&gt;own&lt;/strong&gt; text: canonical-source-unification is about split-brain
code/config surfaces (refs only DIRECTIVE_044); analysis-extract-before-interpret
is a domain-agnostic reasoning discipline (extract facts before interpreting —
applies equally to log analysis and requirement gathering); occurrence-classification-workflow
is a bulk-edit guardrail. Authoring a paradigm edge for any of them would be
topic-adjacency (the C-007(a) violation). Only terminology-extraction-mapping’s
own text carries the bounded-context / ubiquitous-language / ACL vocabulary.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Group 3 — &lt;code dir=&quot;auto&quot;&gt;contextive → canonical-source-unification&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;→ occurrence-classification-workflow&lt;/code&gt; — EXCLUDED.&lt;/strong&gt; Contextive is a ubiquitous-language &lt;em&gt;glossary&lt;/em&gt;
tool; canonical-source-unification (code/config surface consolidation) and
occurrence-classification-workflow (generic string bulk-edit classification) are
not glossary/terminology work, so contextive does not support them.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Group 3 — &lt;code dir=&quot;auto&quot;&gt;terminology-guard → terminology-extraction-mapping&lt;/code&gt; — EXCLUDED.&lt;/strong&gt;
The guard enforces a canon of &lt;em&gt;superseded/forbidden&lt;/em&gt; terms (catching reappearances
in active source), which supports maintaining a &lt;strong&gt;canonical route&lt;/strong&gt; (E7) and a
&lt;strong&gt;completed rename&lt;/strong&gt; (E8); it does not support &lt;em&gt;building a project glossary&lt;/em&gt;, which
is contextive’s job (E9). Excluded to avoid stretching the support relation.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;analysis-extract-before-interpret&lt;/code&gt; — NO Family E edge at all.&lt;/strong&gt; Its own text
attests neither a paradigm link (group 1) nor a terminology-tool support relation
(group 3): it is a general extract-before-interpret reasoning tactic, not a
terminology/glossary technique. It stays in the deferred set, untouched.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;why-family-e-is-inert--measured-not-assumed-wp08-helper-r-1&quot;&gt;Why Family E is INERT — measured, not assumed (WP08 helper, R-1)&lt;/h3&gt;
&lt;p&gt;All nine edges are inert under today’s traversal:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Every source is either &lt;code dir=&quot;auto&quot;&gt;agent_profile:architect-alphonso&lt;/code&gt; (a &lt;strong&gt;profile&lt;/strong&gt;: the
profile channel walks &lt;code dir=&quot;auto&quot;&gt;{requires, specializes_from}&lt;/code&gt; only, never &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;) or
an &lt;strong&gt;action-UNREACHABLE&lt;/strong&gt; tactic/toolguide — &lt;code dir=&quot;auto&quot;&gt;terminology-extraction-mapping&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;contextive&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;terminology-guard&lt;/code&gt; are all pinned in &lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_D1&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;D2&lt;/code&gt;,
and &lt;code dir=&quot;auto&quot;&gt;resolve_context&lt;/code&gt; walks &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; only &lt;strong&gt;from&lt;/strong&gt; scope-resolved artifacts, so
an unreachable source’s outbound &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; are never followed.&lt;/li&gt;
&lt;li&gt;The two reinforcement edges (E2/E3) point &lt;strong&gt;into&lt;/strong&gt; the already-action-reachable
DDD / brownfield paradigms; an edge into a reachable node does not make its
&lt;strong&gt;source&lt;/strong&gt; reachable.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Measured before/after with the WP08 helper: &lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_D1&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_D2&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;_PROFILE_UNREACHABLE&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;_PROFILE_RESCUES&lt;/code&gt; are
&lt;strong&gt;UNCHANGED&lt;/strong&gt;. Family E moves &lt;strong&gt;no&lt;/strong&gt; reachability pin — only composition counts.&lt;/p&gt;
&lt;h2 id=&quot;composition-ledger-nfr-004--family-e-3063-analysis--terminology--reasons-canvas-family&quot;&gt;Composition ledger (NFR-004) — Family E (#3063 ANALYSIS / TERMINOLOGY / REASONS-CANVAS family)&lt;/h2&gt;
&lt;p&gt;Nine &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; overlay edges, zero new artefacts. Each moved count is recorded
so no golden number moves silently.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Shipped-graph edges 873 → 882&lt;/strong&gt; (+9). &lt;code dir=&quot;auto&quot;&gt;len(HAND_AUTHORED_EDGES)&lt;/code&gt; &lt;strong&gt;109 → 118&lt;/strong&gt;.
Zero new artefacts, so the pure-extraction golden counts (&lt;code dir=&quot;auto&quot;&gt;_EXPECTED_NODE_COUNT=311&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;_EXPECTED_EDGE_COUNT=764&lt;/code&gt;) are &lt;strong&gt;unchanged&lt;/strong&gt; — every edge is overlay-authored —
and &lt;code dir=&quot;auto&quot;&gt;test_shipped_graph_is_fresh_and_byte_identical&lt;/code&gt; stays green by construction
(&lt;code dir=&quot;auto&quot;&gt;764 + 118 = 882&lt;/code&gt;) once the fragments are regenerated. Ledger entry (13) is added
to &lt;code dir=&quot;auto&quot;&gt;test_extractor_projection&lt;/code&gt;’s composition ledger.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; relation histogram 417 → 426&lt;/strong&gt; (+9; all nine edges are &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;).
&lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt; (272) and &lt;code dir=&quot;auto&quot;&gt;scope&lt;/code&gt; (159) are &lt;strong&gt;unchanged&lt;/strong&gt;. Gated by
&lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_no_authored_applies_edge.py::TestPositiveCountClaimsAreTrue&lt;/code&gt;
and mirrored char-for-char in &lt;code dir=&quot;auto&quot;&gt;RELATION_DESCRIPTIONS&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;doctrine.drg.models&lt;/code&gt;) and
&lt;code dir=&quot;auto&quot;&gt;docs/architecture/doctrine-relationships.md&lt;/code&gt;; both updated.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Orphan sets UNCHANGED&lt;/strong&gt; — every one of the nine endpoints was already
edge-incident, so nothing enters or leaves &lt;code dir=&quot;auto&quot;&gt;_AWAITING_REFERENCES&lt;/code&gt; /
&lt;code dir=&quot;auto&quot;&gt;_ORPHANS_RESOLVED_BY_OVERLAY&lt;/code&gt;; pure orphans stay 30, shipped orphans stay 21.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_D1&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;D2&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;_PROFILE_UNREACHABLE&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;_PROFILE_RESCUES&lt;/code&gt;
UNCHANGED&lt;/strong&gt; — Family E is inert (measured). No pin moves. Ledgered in
&lt;code dir=&quot;auto&quot;&gt;tests/doctrine/drg/test_reachability.py&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Deferred set unchanged at 50&lt;/strong&gt; — no artefact leaves (topology-only; delivery
is the fast-follow’s job per the operator).&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;family-f-3063-orphan-governance-directives--operator-interview-outcome-accept-no-edges-authored&quot;&gt;Family F (#3063 ORPHAN GOVERNANCE DIRECTIVES) — operator interview outcome, ACCEPT (no edges authored)&lt;/h2&gt;
&lt;p&gt;The four remaining deferred directives (&lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_035&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_038&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_039&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_044&lt;/code&gt;) are &lt;strong&gt;hub directives that reach no action&lt;/strong&gt; —
but three of the four are unreachable &lt;em&gt;by design&lt;/em&gt;, not by defect. Unlike the
tactic/toolguide families, a directive is a hub, not a leaf, so “fixing” it means
changing its &lt;strong&gt;activation model&lt;/strong&gt; (scope it from an action, or make it always-on),
not authoring member edges. The operator ruled &lt;strong&gt;ACCEPT&lt;/strong&gt; — author &lt;strong&gt;no edges&lt;/strong&gt;;
record the disposition here (2026-07-29):&lt;/p&gt;



































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;directive&lt;/th&gt;&lt;th&gt;activation archetype&lt;/th&gt;&lt;th&gt;why unreachable-by-default is CORRECT&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;DIRECTIVE_038&lt;/code&gt; structured-prompt-boundary&lt;/td&gt;&lt;td&gt;&lt;strong&gt;charter-opt-in by design&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;its own &lt;code dir=&quot;auto&quot;&gt;scope&lt;/code&gt; states &lt;em&gt;“Does not apply to projects that have not opted in via charter”&lt;/em&gt; (SPDD paradigm / reasons-canvas tactics / 038)&lt;/td&gt;&lt;td&gt;&lt;strong&gt;ACCEPT&lt;/strong&gt; — intentionally charter-gated; forcing it reachable would violate its own scope contract. Ties to Family E1 (SPDD/reasons-canvas).&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_039&lt;/code&gt; lynn-cole-engineering-culture&lt;/td&gt;&lt;td&gt;&lt;strong&gt;user-selected persona by design&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;its own &lt;code dir=&quot;auto&quot;&gt;intent&lt;/code&gt; states &lt;em&gt;“Select this directive when the user names Lynn Cole’s rules…”&lt;/em&gt;&lt;/td&gt;&lt;td&gt;&lt;strong&gt;ACCEPT&lt;/strong&gt; — intentionally opt-in; not an orphan to wire.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_035&lt;/code&gt; bulk-edit-occurrence-classification&lt;/td&gt;&lt;td&gt;&lt;strong&gt;conditional-on-mission-property&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;scope&lt;/code&gt; = &lt;em&gt;“any mission marked &lt;code dir=&quot;auto&quot;&gt;change_mode: bulk_edit&lt;/code&gt;”&lt;/em&gt; — a mission property, not an action; scoping it from &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;review&lt;/code&gt; would over-deliver it to &lt;em&gt;every&lt;/em&gt; mission (context bloat)&lt;/td&gt;&lt;td&gt;&lt;strong&gt;ACCEPT&lt;/strong&gt; — carried by the bulk-edit mission-type / charter selection, not a broad action scope.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_044&lt;/code&gt; canonical-sources-and-unification&lt;/td&gt;&lt;td&gt;&lt;strong&gt;genuinely universal → always-on candidate&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;applies to &lt;em&gt;“whenever an agent selects a template/skill/command… whenever a split-brain is discovered”&lt;/em&gt; — i.e. ~all agent work — yet no action scopes it&lt;/td&gt;&lt;td&gt;&lt;strong&gt;DEFER to #3064&lt;/strong&gt; — the universal engineering-hygiene rule belongs in the default &lt;code dir=&quot;auto&quot;&gt;charter.yml&lt;/code&gt; / empty-charter always-on set; the always-on &lt;strong&gt;activation-model&lt;/strong&gt; decision is #3064’s, not edge-authoring.&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;&lt;strong&gt;No graph change.&lt;/strong&gt; Family F authors zero edges and moves zero counts; the four
directives stay in the deferred set (now understood as intentionally-gated / #3064-owned,
not defects). This closes the #3063 operator interview: Families A–E
authored, F accepted, and the four depth-gated artefacts accepted (see the
depth-gated note above). All residual delivery/activation work is owned by the
fast-follow walk-update mission and #3064.&lt;/p&gt;
&lt;h2 id=&quot;composition-ledger-nfr-004--mission-rehome-writing-comms-doctrine-01kz9v0s-wp04&quot;&gt;Composition ledger (NFR-004) — mission &lt;code dir=&quot;auto&quot;&gt;rehome-writing-comms-doctrine-01KZ9V0S&lt;/code&gt; (WP04)&lt;/h2&gt;
&lt;p&gt;The writing/comms rehome ships 7 new agent profiles, directives 047–050, two
styleguides, two procedures, one tactic and five audience assets. Regenerating the
DRG off that final frontmatter (&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctrine regenerate-graph&lt;/code&gt;) moved the
following counts — each measured via &lt;code dir=&quot;auto&quot;&gt;load_built_in_graph()&lt;/code&gt; /
&lt;code dir=&quot;auto&quot;&gt;profile_channel_reachable&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;action_channel_reachable&lt;/code&gt;, never estimated:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Shipped built-in graph &lt;code dir=&quot;auto&quot;&gt;nodes 324 → 345&lt;/code&gt; (+21), &lt;code dir=&quot;auto&quot;&gt;edges 892 → 930&lt;/code&gt; (+38).&lt;/strong&gt; The
+21 nodes are exactly the shipped artefacts (7 profiles + 4 directives + 2
styleguides + 2 procedures + 1 tactic + 5 assets); pinned in
&lt;code dir=&quot;auto&quot;&gt;tests/doctrine/test_pack_relocation_doctor_gate.py&lt;/code&gt; as &lt;code dir=&quot;auto&quot;&gt;(345, 930)&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;_PROFILE_UNREACHABLE&lt;/code&gt; 60 → 59&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;tests/doctrine/drg/test_reachability.py&lt;/code&gt;).
One member left the set: &lt;code dir=&quot;auto&quot;&gt;tactic:secure-design-checklist&lt;/code&gt; became
profile-reachable via the authored chain
&lt;code dir=&quot;auto&quot;&gt;agent_profile:minutes-maker-mahad&lt;/code&gt; —&lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt;—&gt; &lt;code dir=&quot;auto&quot;&gt;directive:DIRECTIVE_050&lt;/code&gt;
(&lt;code dir=&quot;auto&quot;&gt;050-credential-handling-discipline&lt;/code&gt;, whose &lt;code dir=&quot;auto&quot;&gt;references&lt;/code&gt; list carries
&lt;code dir=&quot;auto&quot;&gt;type: tactic, id: secure-design-checklist&lt;/code&gt;, minted as a &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; edge)
—&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;—&gt; &lt;code dir=&quot;auto&quot;&gt;tactic:secure-design-checklist&lt;/code&gt;. Both edges are authored
frontmatter shipped by this mission (WP01/WP02); the profile channel seeds every
agent profile, so the new profile’s &lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt; edge animates the pre-existing
&lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_050 -&gt; secure-design-checklist&lt;/code&gt; reference.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;_PROFILE_RESCUES&lt;/code&gt; UNCHANGED (30).&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;secure-design-checklist&lt;/code&gt; is
action-reachable at &lt;code dir=&quot;auto&quot;&gt;d=2&lt;/code&gt; (absent from &lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_D2&lt;/code&gt;), so it was never
in &lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_D2 − _PROFILE_UNREACHABLE&lt;/code&gt;; removing it from
&lt;code dir=&quot;auto&quot;&gt;_PROFILE_UNREACHABLE&lt;/code&gt; does not change the rescues set. The ledger-coverage
cross-check (&lt;code dir=&quot;auto&quot;&gt;TestProfileRescuesHaveLedgerCoverage&lt;/code&gt;) is therefore unaffected.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_D1&lt;/code&gt; (60) and &lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_D2&lt;/code&gt; (50) UNCHANGED&lt;/strong&gt; —
measured, not assumed. The new artefacts are not charter-activated in the
dogfood &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/charter.yaml&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;agent_profile&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;asset&lt;/code&gt; are not
activation kinds, so the action-channel activated-unreachable pins do not move.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Glossary term count UNCHANGED (108)&lt;/strong&gt; — no glossary edits.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;composition-ledger-nfr-002nfr-004--reachability-companion-metric-mission-drg-reachability-metric-wiring-01kzs5vr-wp01-3009-point-3&quot;&gt;Composition ledger (NFR-002/NFR-004) — reachability companion metric (mission &lt;code dir=&quot;auto&quot;&gt;drg-reachability-metric-wiring-01KZS5VR&lt;/code&gt;, WP01, #3009 point 3)&lt;/h2&gt;
&lt;p&gt;This mission adds the &lt;strong&gt;action-only whole-graph reachability companion guard&lt;/strong&gt;
(&lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_SHIPPED&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tests/doctrine/drg/test_reachability.py&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;test_shipped_graph_action_reachability_is_the_pinned_membership&lt;/code&gt;) — the #3009
point-3 deliverable — and wires the six genuine, traced inbound edges that make
its residual orphans reachable. Every number below is measured against the
regenerated &lt;code dir=&quot;auto&quot;&gt;packs/built-in&lt;/code&gt; graph via the canonical
&lt;code dir=&quot;auto&quot;&gt;action_channel_reachable&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;profile_channel_reachable&lt;/code&gt; helpers (C-001; no
hand-rolled walk).&lt;/p&gt;
&lt;h3 id=&quot;the-six-curated-edges-_curated_artifact_edges-srcdoctrinedrgmigrationextractorpy&quot;&gt;The six curated edges (&lt;code dir=&quot;auto&quot;&gt;_CURATED_ARTIFACT_EDGES&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;src/doctrine/drg/migration/extractor.py&lt;/code&gt;)&lt;/h3&gt;





















































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;#&lt;/th&gt;&lt;th&gt;Edge&lt;/th&gt;&lt;th&gt;Relation&lt;/th&gt;&lt;th&gt;Trace (artifact text)&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;1&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;procedure:refactoring&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;directive:DISCIPLINED_REFACTORING&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;refactoring.procedure.yaml&lt;/code&gt; step 2 (“Select the relevant refactoring tactics”) already cites 9 Fowler tactics; the directive holds 7 disjoint ones plus the “name the smell first” discipline.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;2&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;directive:DIRECTIVE_024&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;directive:RECONCILE_CHANGE_SCOPE_TENSIONS&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;&lt;/td&gt;&lt;td&gt;The reconciler’s own &lt;code dir=&quot;auto&quot;&gt;scope&lt;/code&gt; names DIRECTIVE_024 as a trigger.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;3&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;directive:DIRECTIVE_025&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;directive:RECONCILE_CHANGE_SCOPE_TENSIONS&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Same scope sentence, names DIRECTIVE_025.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;4&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;directive:DIRECTIVE_030&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;directive:USE_MUTATION_TESTING_TO_VALIDATE_TEST_QUALITY&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;&lt;/td&gt;&lt;td&gt;DIRECTIVE_030 governs the coverage gate; the mutation-testing directive critiques coverage-as-proxy, deepening the same gate.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;5&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;agent_profile:researcher-robbie&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;procedure:spike-timebox-policy&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Robbie’s structured &lt;code dir=&quot;auto&quot;&gt;operating-procedures&lt;/code&gt; field lists &lt;code dir=&quot;auto&quot;&gt;spike-timebox-policy&lt;/code&gt; directly.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;6a&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;agent_profile:lexical-larry&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;procedure:glossary-maintenance-workflow&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Larry is the diagnostic “feeder into” the workflow; &lt;code dir=&quot;auto&quot;&gt;curator-carla&lt;/code&gt; owns its acceptance — &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;, not &lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt; (larry feeds, does not own).&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;6b&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;agent_profile:minutes-maker-mahad&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;procedure:meeting-minutes-pipeline&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Mahad’s own text: “the primary agent for the meeting-minutes-pipeline procedure.”&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;Zero new nodes; zero new orphans (C-003). &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctrine regenerate-graph --check&lt;/code&gt; confirms determinism (byte-identical fragments across two runs).&lt;/p&gt;
&lt;h3 id=&quot;the-companion-metric-moves-_action_unreachable_shipped-88--75&quot;&gt;The companion metric moves: &lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_SHIPPED&lt;/code&gt; 88 → 75&lt;/h3&gt;
&lt;p&gt;Primary definition (action-only, whole-graph, excludes &lt;code dir=&quot;auto&quot;&gt;_BY_DESIGN_UNREACHABLE_KINDS&lt;/code&gt;
and the action/profile traversal-root seeds — see the guard contract,
&lt;code dir=&quot;auto&quot;&gt;kitty-specs/drg-reachability-metric-wiring-01KZS5VR/contracts/reachability-companion-guard.md&lt;/code&gt;):
&lt;strong&gt;88 → 75&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;-13&lt;/code&gt;), asserted total &amp;#x26; disjoint into &lt;code dir=&quot;auto&quot;&gt;_DEAD_DOCTRINE_SHIPPED&lt;/code&gt;
(&lt;strong&gt;38 → 34&lt;/strong&gt;, &lt;code dir=&quot;auto&quot;&gt;-4&lt;/code&gt;) and &lt;code dir=&quot;auto&quot;&gt;_PROFILE_DELIVERED_SHIPPED&lt;/code&gt; (&lt;strong&gt;50 → 41&lt;/strong&gt;, &lt;code dir=&quot;auto&quot;&gt;-9&lt;/code&gt;).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;_WIRED_THIS_MISSION&lt;/code&gt; — the thirteen URNs this mission makes action-reachable&lt;/strong&gt;
(pinned in &lt;code dir=&quot;auto&quot;&gt;test_reachability.py&lt;/code&gt;; each asserted action-reachable AND named
here — the anti-null-delta forcing mechanism, Debbie Item 1):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;directive:DISCIPLINED_REFACTORING&lt;/code&gt; — reachable via edge 1 (the already
action-scoped &lt;code dir=&quot;auto&quot;&gt;procedure:refactoring&lt;/code&gt;). Was profile-channel reachable
already, so it leaves &lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_SHIPPED&lt;/code&gt; but was never a member of
&lt;code dir=&quot;auto&quot;&gt;_DEAD_DOCTRINE_SHIPPED&lt;/code&gt; (it moves from &lt;code dir=&quot;auto&quot;&gt;_PROFILE_DELIVERED_SHIPPED&lt;/code&gt;, not
&lt;code dir=&quot;auto&quot;&gt;_DEAD_DOCTRINE_SHIPPED&lt;/code&gt;, into full action-reachability).&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;directive:RECONCILE_CHANGE_SCOPE_TENSIONS&lt;/code&gt; — reachable via edges 2/3. Was
reachable from &lt;strong&gt;neither&lt;/strong&gt; channel pre-wiring, so it leaves
&lt;code dir=&quot;auto&quot;&gt;_DEAD_DOCTRINE_SHIPPED&lt;/code&gt; (one of the four &lt;code dir=&quot;auto&quot;&gt;_DEAD_DOCTRINE_SHIPPED&lt;/code&gt; departures).&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;directive:USE_MUTATION_TESTING_TO_VALIDATE_TEST_QUALITY&lt;/code&gt; — reachable via
edge 4 (the already action-scoped &lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_030&lt;/code&gt;). Was profile-channel
reachable already (same shape as DISCIPLINED_REFACTORING above); moves from
&lt;code dir=&quot;auto&quot;&gt;_PROFILE_DELIVERED_SHIPPED&lt;/code&gt; into full action-reachability.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:refactoring-encapsulate-record&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic:refactoring-encapsulate-variable&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;tactic:refactoring-extract-first-order-concept&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic:refactoring-move-field&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;tactic:refactoring-move-method&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic:refactoring-state-pattern-for-behavior&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;tactic:refactoring-strangler-fig&lt;/code&gt; — the seven Fowler tactics cascaded into
action context by &lt;code dir=&quot;auto&quot;&gt;directive:DISCIPLINED_REFACTORING&lt;/code&gt;’s pre-existing
&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; edges (family-B overlay, ledger entry 10) once edge 1 makes the
directive itself action-reachable. All seven were &lt;code dir=&quot;auto&quot;&gt;_PROFILE_DELIVERED_SHIPPED&lt;/code&gt;
members (reachable via the profile channel already); they move into full
action-reachability, not out of &lt;code dir=&quot;auto&quot;&gt;_DEAD_DOCTRINE_SHIPPED&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tactic:mutation-testing-workflow&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;toolguide:python-mutation-tools&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;toolguide:typescript-mutation-tools&lt;/code&gt; — cascaded into action context by
&lt;code dir=&quot;auto&quot;&gt;directive:USE_MUTATION_TESTING_TO_VALIDATE_TEST_QUALITY&lt;/code&gt;’s pre-existing
&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; edges (family-D overlay, ledger entry 12) once edge 4 makes the
directive action-reachable. All three were &lt;code dir=&quot;auto&quot;&gt;_PROFILE_DELIVERED_SHIPPED&lt;/code&gt;
members; same move as the refactoring family.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Net: &lt;strong&gt;four&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;_DEAD_DOCTRINE_SHIPPED&lt;/code&gt; departures — &lt;code dir=&quot;auto&quot;&gt;directive:RECONCILE_CHANGE_ SCOPE_TENSIONS&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;procedure:spike-timebox-policy&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;procedure:glossary- maintenance-workflow&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;procedure:meeting-minutes-pipeline&lt;/code&gt; — the four members
reachable from &lt;strong&gt;neither&lt;/strong&gt; channel pre-wiring that a curated edge now delivers.
The other &lt;strong&gt;nine&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_SHIPPED&lt;/code&gt; departures (the &lt;code dir=&quot;auto&quot;&gt;_WIRED_THIS_ MISSION&lt;/code&gt; tactics/toolguides plus the two remaining directives) were already
&lt;code dir=&quot;auto&quot;&gt;_PROFILE_DELIVERED_SHIPPED&lt;/code&gt; — genuinely unreachable from actions, but never
“dead doctrine” (a profile already surfaces them) — so wiring them shrinks the
&lt;strong&gt;action-only primary pin&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_SHIPPED&lt;/code&gt;) without moving
&lt;code dir=&quot;auto&quot;&gt;_DEAD_DOCTRINE_SHIPPED&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;procedure:spike-timebox-policy&lt;/code&gt; (edge 5) and &lt;code dir=&quot;auto&quot;&gt;procedure:meeting-minutes-pipeline&lt;/code&gt;
(edge 6b) are &lt;strong&gt;not&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;_WIRED_THIS_MISSION&lt;/code&gt; members — they leave
&lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_SHIPPED&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;_DEAD_DOCTRINE_SHIPPED&lt;/code&gt; partition (now
profile-reachable) but stay action-unreachable, so they are not among the
thirteen the action channel newly reaches; they are, however, part of the
&lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_SHIPPED&lt;/code&gt; measured 88→75 delta’s dead-doctrine subset move
and are named here for that reason.&lt;/p&gt;
&lt;h3 id=&quot;c-003-verification--no-new-residualdefect-member&quot;&gt;C-003 verification — no new residual/defect member&lt;/h3&gt;
&lt;p&gt;Diffing the before/after &lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_SHIPPED&lt;/code&gt; sets (measured, not
assumed): the &lt;code dir=&quot;auto&quot;&gt;entered&lt;/code&gt; set is &lt;strong&gt;empty&lt;/strong&gt; — no node newly joins the whole-graph
unreachable measure. The &lt;code dir=&quot;auto&quot;&gt;left&lt;/code&gt; set is exactly the thirteen &lt;code dir=&quot;auto&quot;&gt;_WIRED_THIS_MISSION&lt;/code&gt;
URNs above. Same verification for the incidence orphan sets
(&lt;code dir=&quot;auto&quot;&gt;_INTENTIONAL_ORPHANS&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;_ACTIVATED_BUT_ORPHANED&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;_AWAITING_REFERENCES&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;tests/doctrine/drg/migration/test_extractor_projection.py&lt;/code&gt;): &lt;code dir=&quot;auto&quot;&gt;directive: RECONCILE_CHANGE_SCOPE_TENSIONS&lt;/code&gt; leaves &lt;code dir=&quot;auto&quot;&gt;_ACTIVATED_BUT_ORPHANED&lt;/code&gt; (29 → 26 pure
orphans); &lt;code dir=&quot;auto&quot;&gt;directive:DISCIPLINED_REFACTORING&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;directive:USE_MUTATION_ TESTING_TO_VALIDATE_TEST_QUALITY&lt;/code&gt; leave &lt;code dir=&quot;auto&quot;&gt;_AWAITING_REFERENCES&lt;/code&gt;. All three were
already resolved by the hand-authored overlay in the &lt;em&gt;shipped&lt;/em&gt; graph (ledger
entries 10/12), so &lt;code dir=&quot;auto&quot;&gt;_SHIPPED_ORPHANS&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;DOCUMENTED_ORPHAN_RESIDUAL&lt;/code&gt; are
UNCHANGED at 21 — already tight (no slack) before this wiring, and still tight
after.&lt;/p&gt;
&lt;h3 id=&quot;activated-only-action-pins-_action_unreachable_d1_d2-_action_d1_d2_spread&quot;&gt;Activated-only action pins (&lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_D1&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;_D2&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;_ACTION_D1_D2_SPREAD&lt;/code&gt;)&lt;/h3&gt;
&lt;p&gt;The whole-graph companion metric above is one measure; the pre-existing
&lt;strong&gt;activated-only&lt;/strong&gt; pins in &lt;code dir=&quot;auto&quot;&gt;tests/doctrine/drg/test_reachability.py&lt;/code&gt; are a
different, narrower one (this project’s &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt; activation set
intersected with unreachability). They move too, and by a DIFFERENT count than
the whole-graph companion — activation is a subset, so only the activated
members of &lt;code dir=&quot;auto&quot;&gt;_WIRED_THIS_MISSION&lt;/code&gt; count here:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_D1&lt;/code&gt; 77 → 76&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;-1&lt;/code&gt;). Only &lt;code dir=&quot;auto&quot;&gt;directive:RECONCILE_ CHANGE_SCOPE_TENSIONS&lt;/code&gt; leaves — it is the sole &lt;code dir=&quot;auto&quot;&gt;_WIRED_THIS_MISSION&lt;/code&gt; member
that is BOTH charter-activated AND reachable at the compact depth (&lt;code dir=&quot;auto&quot;&gt;d=1&lt;/code&gt;),
because &lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_024&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_025&lt;/code&gt; (edges 2/3’s sources) are themselves
&lt;code dir=&quot;auto&quot;&gt;d=1&lt;/code&gt;-reachable.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_D2&lt;/code&gt; 67 → 56&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;-11&lt;/code&gt;). RECONCILE plus TEN activated
cascaded members leave at the bootstrap depth: the seven &lt;code dir=&quot;auto&quot;&gt;refactoring-*&lt;/code&gt;
Fowler tactics, &lt;code dir=&quot;auto&quot;&gt;tactic:mutation-testing-workflow&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;toolguide:python- mutation-tools&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;toolguide:typescript-mutation-tools&lt;/code&gt; (edges 1/4 cascade
their pre-existing family-B/family-D &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; edges into &lt;code dir=&quot;auto&quot;&gt;d=2&lt;/code&gt; reach once
the two new directives become action-reachable). &lt;code dir=&quot;auto&quot;&gt;directive:DISCIPLINED_ REFACTORING&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;directive:USE_MUTATION_TESTING_TO_VALIDATE_TEST_QUALITY&lt;/code&gt;
are NOT charter-activated in this project, so the two directives themselves
never entered this activated-only pin — only their cascaded activated
members move it.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;_ACTION_D1_D2_SPREAD&lt;/code&gt; 10 → 20&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;+10&lt;/code&gt;). The ten activated members that
leave &lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_D2&lt;/code&gt; but NOT &lt;code dir=&quot;auto&quot;&gt;_ACTION_UNREACHABLE_D1&lt;/code&gt; (they are
reachable only at the bootstrap depth) join the pre-existing d1↔d2 spread
instead of leaving D1 too.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;All three moves are measured against the regenerated graph via
&lt;code dir=&quot;auto&quot;&gt;action_channel_reachable&lt;/code&gt; (no hand-rolled walk); see the constant docstrings
in &lt;code dir=&quot;auto&quot;&gt;test_reachability.py&lt;/code&gt; for the full per-member derivation.&lt;/p&gt;</content>
</entry>
