<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/plans/charter-resolution/seeds/seed-m3-operating-procedures/">
  <id>https://docs.spec-kitty.ai/plans/charter-resolution/seeds/seed-m3-operating-procedures/</id>
  <title>Mission Seed M3 - Operating-Procedures Validate, Triage, Data-Drive</title>
  <updated>2026-08-19T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/plans/charter-resolution/seeds/seed-m3-operating-procedures/"/>
  <summary>Specify-intake seed for the mission closing #2994/#3352: validate operating-procedures references, triage fictional entries, then data-drive profile-to-procedure edges.</summary>
  <content type="html">&lt;h2 id=&quot;mission-seed--m3-operating-procedures-validate--triage--data-drive&quot;&gt;Mission Seed — M3: Operating-Procedures Validate → Triage → Data-Drive&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Status:&lt;/strong&gt; seed (not yet a mission). Feed this to &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.specify&lt;/code&gt; in a fresh session.
&lt;strong&gt;Part of:&lt;/strong&gt; charter-resolution program (see &lt;code dir=&quot;auto&quot;&gt;../program-brief.md&lt;/code&gt;).
&lt;strong&gt;Closes:&lt;/strong&gt; #2994, #3352, and the operating-procedures channel of #3488.
&lt;strong&gt;Effort:&lt;/strong&gt; L. &lt;strong&gt;Depends on:&lt;/strong&gt; M1 (single-authority resolution parity) landed — needs the validated node universe. Independent of M2.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id=&quot;problem&quot;&gt;Problem&lt;/h2&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;collaboration.operating-procedures&lt;/code&gt; on an agent profile is a schema-validated &lt;code dir=&quot;auto&quot;&gt;list[str]&lt;/code&gt;, but its &lt;strong&gt;values are never checked against real doctrine nodes&lt;/strong&gt;: measured across 16 built-in profiles, &lt;strong&gt;36 of 50&lt;/strong&gt; declarations name no node (8 name a wrong-kind node; only 6 name a real procedure node). Because the edge-extractor ignores the field entirely, the real &lt;code dir=&quot;auto&quot;&gt;agent_profile → procedure&lt;/code&gt; edges are hand-pinned one profile at a time in &lt;code dir=&quot;auto&quot;&gt;_CURATED_ARTIFACT_EDGES&lt;/code&gt;. So authored procedure references are silently inert, and #3352 (data-drive those edges) cannot be done by blind emission because it would mint 36 dangling edges → &lt;code dir=&quot;auto&quot;&gt;assert_valid&lt;/code&gt; failure.&lt;/p&gt;
&lt;h2 id=&quot;fix-approach-hard-internal-order--do-not-reorder&quot;&gt;Fix approach (hard internal order — do NOT reorder)&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Validate loud (first).&lt;/strong&gt; Add a load-time validator: every &lt;code dir=&quot;auto&quot;&gt;operating-procedures&lt;/code&gt; entry must resolve to a real doctrine node. Converts the 36 silent fictional refs into loud failures. Cheap, high-value, independent. (Empty-allowlist gate precedent: WP09.)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Triage the 36.&lt;/strong&gt; Author / repoint / delete each fictional entry (per-artefact review). Decide the field’s direction (project into edges vs retire/rename).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Data-drive (last).&lt;/strong&gt; Teach the extractor to emit &lt;code dir=&quot;auto&quot;&gt;agent_profile --requires--&gt; procedure&lt;/code&gt; from the field, &lt;strong&gt;guarded to targets that resolve to an existing node&lt;/strong&gt;; retire the hand-pinned &lt;code dir=&quot;auto&quot;&gt;_CURATED_ARTIFACT_EDGES&lt;/code&gt; entries sourced from operating-procedures. Also complete the still-unwired RECONCILE third trigger edge (&lt;code dir=&quot;auto&quot;&gt;tactic:change-apply-smallest-viable-diff&lt;/code&gt;).&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;open-operator-decisions-resolve-at-this-missions-discovery&quot;&gt;Open operator decisions (resolve at this mission’s discovery)&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Wire vs deprecate:&lt;/strong&gt; should &lt;code dir=&quot;auto&quot;&gt;operating-procedures&lt;/code&gt; become a first-class edge source, or be deprecated/renamed in favour of DRG edges? (Either way, ship the dead-entry diagnostic.)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Triage dispositions:&lt;/strong&gt; the 36 fictional refs need per-entry author/repoint/delete calls — likely a review artifact, not a single decision.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;scope&quot;&gt;Scope&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;In:&lt;/strong&gt; the operating-procedures validator, the 36-entry triage, the data-driven extractor emission, retiring the related hand-pins.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Out:&lt;/strong&gt; the broader kind-complete cascade (#2829, that is M5); delivery/render of procedures to the agent (that is M4’s &lt;code dir=&quot;auto&quot;&gt;procedures[]&lt;/code&gt;/step-description work).&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;key-seams-from-the-investigation&quot;&gt;Key seams (from the investigation)&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;doctrine/agent_profiles/profile.py&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;CollaborationContract.operating_procedures&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;doctrine/drg/migration/extractor.py&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;extract_artifact_edges&lt;/code&gt;; the hand-pin at ~:463)&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;_CURATED_ARTIFACT_EDGES&lt;/code&gt; (the per-profile hand-pins to retire)&lt;/li&gt;
&lt;li&gt;validator precedent: the WP09 empty-allowlist gate&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;risk&quot;&gt;Risk&lt;/h2&gt;
&lt;p&gt;Data-driving before triage mints 36 dangling edges and fails &lt;code dir=&quot;auto&quot;&gt;assert_valid&lt;/code&gt;. The order above is load-bearing.&lt;/p&gt;</content>
</entry>
