<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/changelog/3.2.x/">
  <id>https://docs.spec-kitty.ai/changelog/3.2.x/</id>
  <title>3.2.x — Doctrine-runtime depth · core-domain strangling · DevEx</title>
  <updated>2026-09-30T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/changelog/3.2.x/"/>
  <summary>Declaration of intent for the 3.2.x release cycle: deepen doctrine/charter/DRG impact on runtime, strangle core domains onto single sources of truth, and improve DevEx.</summary>
  <content type="html">&lt;span id=&quot;32x--doctrine-runtime-depth--core-domain-strangling--devex&quot;&gt;&lt;/span&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Superseded.&lt;/strong&gt; The 3.x line is closed; 3.2.7 (2026-09-10) was the last 3.x release. The active cycle is 4.0.0 — see the &lt;a href=&quot;/plans/4-0-0-milestone-roadmap/&quot;&gt;4.0.0 roadmap&lt;/a&gt;. Kept as a record of the cycle’s intent.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;strong&gt;Milestone:&lt;/strong&gt; &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/milestone/4&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;3.2.x&lt;/code&gt;&lt;/a&gt; (closed) ·
&lt;strong&gt;Status:&lt;/strong&gt; closed (historical record) · &lt;strong&gt;Declared:&lt;/strong&gt; 2026-06-16 · &lt;strong&gt;Advances:&lt;/strong&gt; epics #1619 (runtime/state SSOT),
#1868 (canonical seams), #1878 (coordination strangler).&lt;/p&gt;
&lt;h2 id=&quot;theme&quot;&gt;Theme&lt;/h2&gt;
&lt;p&gt;A stabilization-and-depth cycle: make the &lt;strong&gt;governance layer actually shape runtime&lt;/strong&gt;, &lt;strong&gt;strangle our
core domains onto single sources of truth&lt;/strong&gt;, and &lt;strong&gt;lower the cost of doing both&lt;/strong&gt;. Shipped as emergent
patches (&lt;code dir=&quot;auto&quot;&gt;3.2.1&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;3.2.2&lt;/code&gt;, …) that each advance one of the three goals below; the cycle stays open
until they hold. &lt;strong&gt;No new shadow paths&lt;/strong&gt; — every change routes a duplicate onto an existing authority
or extracts a pure seam from an inline blob, never builds a parallel one.&lt;/p&gt;
&lt;h2 id=&quot;goals&quot;&gt;Goals&lt;/h2&gt;
&lt;h3 id=&quot;g1--deepen-doctrine--charter--drg-impact-on-runtime-execution&quot;&gt;G1 — Deepen Doctrine / Charter / DRG impact on runtime execution&lt;/h3&gt;
&lt;p&gt;Wire the charter + doctrine layer and the &lt;strong&gt;Doctrine Resolution Graph (DRG)&lt;/strong&gt; &lt;em&gt;into&lt;/em&gt; the runtime
execution loop, so directives, tactics, agent profiles, and mission-step contracts demonstrably shape
what &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt;/the commands do — not just sit as resolvable config. Close the gap between “doctrine
exists” and “doctrine governs execution.”&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Epic &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/2466&quot;&gt;#2466&lt;/a&gt; — Doctrine/Charter extensibility &amp;#x26;
the pack ecosystem.&lt;/strong&gt; Turn the doctrine substrate from &lt;em&gt;built-in behaviour&lt;/em&gt; into an &lt;em&gt;author-able pack
ecosystem&lt;/em&gt;, so customers define/refine their own doctrine (mission types, assets, shortcodes) against
the same activation/cascade/DRG machinery. Much of the core/workflow/topology/status work was the
enabler. &lt;strong&gt;The whole epic is in 3.2.x — the dependency order is sequencing, not phasing&lt;/strong&gt; (if items
slip to 3.3.x later, that’s a future call):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;#2467 (keystone · L)&lt;/strong&gt; — split the monolithic &lt;code dir=&quot;auto&quot;&gt;built-in&lt;/code&gt; doctrine into packs + &lt;strong&gt;compound packs&lt;/strong&gt;
(pack manifest &lt;code dir=&quot;auto&quot;&gt;depends_on&lt;/code&gt;, DAG resolution + cycle-detection in the activation engine). Land as a
pure refactor + compat shim first; everything below builds on it.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#2468 (L)&lt;/strong&gt; — promote &lt;code dir=&quot;auto&quot;&gt;mission-type&lt;/code&gt; to a first-class doctrine artifact kind (behaviour-as-config;
retires the deliberate &lt;code dir=&quot;auto&quot;&gt;MissionTypeNotAnArtifactKind&lt;/code&gt; side-channel — needs a decision record).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#2471 (M)&lt;/strong&gt; — extract the pack validator (&lt;code dir=&quot;auto&quot;&gt;validate_pack&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;DoctrineHealthReport&lt;/code&gt;) as a
dependency-light CI tester with no full-CLI import (mirrors the shared-package-boundary layering).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#2469 (S)&lt;/strong&gt; — loose-contract &lt;code dir=&quot;auto&quot;&gt;assets&lt;/code&gt; kind · &lt;strong&gt;#2470 (M)&lt;/strong&gt; — shortcodes / harness-command aliases
as doctrine (extends the &lt;code dir=&quot;auto&quot;&gt;command_renderer&lt;/code&gt;/manifest pipeline, not a fork).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#2472 (S)&lt;/strong&gt; — decide the &lt;code dir=&quot;auto&quot;&gt;procedure&lt;/code&gt; kind’s fate after #2468 · &lt;strong&gt;#2473 (M · orthogonal)&lt;/strong&gt; —
scheduled model-discipline currency pipeline (human-in-loop PR, never auto-merge).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Open decisions ride on the issues (#2469 kind-vs-&lt;code dir=&quot;auto&quot;&gt;template&lt;/code&gt; · #2472 procedure fate · #2473 fold-vs-track).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Epic &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/2519&quot;&gt;#2519&lt;/a&gt; — Charter authoring &amp;#x26; lifecycle
robustness.&lt;/strong&gt; The consume-and-govern paths for charter/doctrine are solid; the &lt;strong&gt;author, observe, and
reproduce&lt;/strong&gt; paths are thin. Surfaced while authoring the &lt;code dir=&quot;auto&quot;&gt;mission-wrap-up-sequence&lt;/code&gt; procedure +
&lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_046&lt;/code&gt; directly against &lt;code dir=&quot;auto&quot;&gt;src/doctrine/&lt;/code&gt;. Sibling to #2466 (extensibility/packs) — same G1
theme from the maintainer/first-party side. A pre-spec research squad (2026-07-10) found the three
original children collide on one un-owned defect — the activation surfaces (&lt;code dir=&quot;auto&quot;&gt;config.activated_*&lt;/code&gt; ↔
&lt;code dir=&quot;auto&quot;&gt;answers.selected_*&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;references.yaml&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;graph.yaml&lt;/code&gt;) are disjoint ledgers with no reconciler — so a
&lt;strong&gt;foundation slice (#2526)&lt;/strong&gt; is carved out as the prerequisite. Sequence &lt;strong&gt;#2526 → #2522 (C) → #2521
(B) → #2520 (A)&lt;/strong&gt; (shared seams: &lt;code dir=&quot;auto&quot;&gt;charter.activation_engine.commit_plan&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;_save_config&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;src/doctrine/graph.yaml&lt;/code&gt; generation, the charter-init/intake flow):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;#2526 (Slice 0 · foundation, prerequisite)&lt;/strong&gt; — unify the charter &lt;strong&gt;activation surfaces&lt;/strong&gt;: reconcile
&lt;code dir=&quot;auto&quot;&gt;config.activated_*&lt;/code&gt; ↔ &lt;code dir=&quot;auto&quot;&gt;answers.selected_*&lt;/code&gt;, make &lt;code dir=&quot;auto&quot;&gt;activate&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;deactivate&lt;/code&gt; write-through (or an explicit
&lt;code dir=&quot;auto&quot;&gt;--resynthesize&lt;/code&gt;), and extend &lt;code dir=&quot;auto&quot;&gt;consistency_check&lt;/code&gt; to assert config↔answers↔references parity (fail
closed). Unblocks and de-conflicts C and B (the divergence bit PR #2524).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#2520 (A)&lt;/strong&gt; — charter &lt;strong&gt;domain events&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;CharterCreated&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;CharterUpdated&lt;/code&gt;, open payload) through
the existing CLI sync/SaaS event path; no charter lifecycle event exists today, so SaaS cannot
observe activation/creation deltas or authorship. Spans repo-local emit wiring + external
&lt;code dir=&quot;auto&quot;&gt;spec_kitty_events&lt;/code&gt; contract + SaaS consumer; splittable.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#2521 (B)&lt;/strong&gt; — charter-init &lt;strong&gt;harness-freshness preflight&lt;/strong&gt; + deterministic intake inputs (stale/
missing tooling across agent harnesses; intake not deterministically loading its inputs). Notes a
future &lt;code dir=&quot;auto&quot;&gt;charter discovery/update&lt;/code&gt; &lt;strong&gt;custom mission type&lt;/strong&gt; as the long-term vehicle.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#2522 (C)&lt;/strong&gt; — &lt;strong&gt;doctrine-authoring surface + docs&lt;/strong&gt;: a &lt;code dir=&quot;auto&quot;&gt;charter author&lt;/code&gt; scaffold + maintainer how-to
for editing a built-in artefact → regenerating the generated &lt;code dir=&quot;auto&quot;&gt;graph.yaml&lt;/code&gt; → the freshness gate
(authoring is currently reverse-engineered).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;g2--strangle-out-our-core-domains&quot;&gt;G2 — Strangle out our core domains&lt;/h3&gt;
&lt;p&gt;Continue the #1619 runtime/state decomposition: take each &lt;strong&gt;core domain&lt;/strong&gt; (identity/naming,
path/read-path, coordination/topology, status, lanes, ownership) onto its &lt;strong&gt;canonical SSOT&lt;/strong&gt;, route
every consumer to &lt;em&gt;consume&lt;/em&gt; it, and ratchet the duplication class shut. Extract → route → enforce,
domain by domain, behind characterization tests.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;The full #1878 coord/primary write-side strangler is in-scope for G2 (operator decision,
supersedes the earlier 3.3.x split below).&lt;/strong&gt; Both slices land in 3.2.x: placement-routing (which
partition a write targets — coord vs primary, by kind) &lt;strong&gt;and&lt;/strong&gt; commit/protected-branch durability
(how a write actually lands once routed). The coord-primary-partition-lock mission delivers the
placement-routing slice under this cycle; the commit-durability slice is a 3.2.x fast-follow
mission, not deferred to 3.3.x.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;2026-08-01 scoping gap:&lt;/strong&gt; placement-routing and commit-durability both presuppose a write
already originates inside a &lt;em&gt;valid&lt;/em&gt; mission workspace — neither checks that the invoking
checkout is the one the mission actually declared. Design-spike
&lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/3129&quot;&gt;#3129&lt;/a&gt; names this precondition gap
(dialectic-squad corroborated; see
&lt;a href=&quot;/plans/3-2-x-milestone-roadmap/#addendum-2026-08-01--write-path-topology-scoping-gap-design-spike-3129&quot;&gt;3-2-x-milestone-roadmap.md § Addendum 2026-08-01&lt;/a&gt;).
The cheap fix — &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/3128&quot;&gt;#3128&lt;/a&gt;, a fail-closed
checkout-identity check — is recommended for folding into this G2 scope now. The larger
shadow-workspace redesign that #3129 itself proposes remains a separate, ungated design-spike
pending an operator decision on scope.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;First active slice — naming / identity routing rider&lt;/strong&gt; (the 3-squad investigation, 2026-06-16,
as narrowed by the neutral scoring panel). The static &lt;code dir=&quot;auto&quot;&gt;branch_naming&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;mid8()&lt;/code&gt; seam &lt;strong&gt;is&lt;/strong&gt; a sound
SSOT (built by the 3.2.0 work; ADR &lt;code dir=&quot;auto&quot;&gt;2026-03-09-1&lt;/code&gt; “Prompts do not discover context. Commands do”;
FR-009/FR-012) — that survived every adversarial pass. The wider &lt;code dir=&quot;auto&quot;&gt;ExecutionContext&lt;/code&gt;
compute-once-thread-through design is &lt;strong&gt;real but not yet load-bearing&lt;/strong&gt; (built-and-parked, mutable,
internally split-brained — see the evidence trail); &lt;em&gt;threading it&lt;/em&gt; is a later builder-hardening effort
(3.2.x parallel track), &lt;strong&gt;not&lt;/strong&gt; this rider. So the rider is the cheap, low-risk subset: &lt;strong&gt;route&lt;/strong&gt;
the ~20 bare &lt;code dir=&quot;auto&quot;&gt;mission_id[:8]&lt;/code&gt; sites through &lt;code dir=&quot;auto&quot;&gt;mid8()&lt;/code&gt; (bulk/standalone/dashboard — wrong cardinality
to thread), adopt the fragment only at the 2–3 sites that already hold a context, and extend the
literal-ban ratchet to bare &lt;code dir=&quot;auto&quot;&gt;…_id[:8]&lt;/code&gt; repo-wide &lt;strong&gt;as a tripwire&lt;/strong&gt;. The
static composes (#2000/#1899-tail/#1900), the &lt;code dir=&quot;auto&quot;&gt;resolve_lanes_dir&lt;/code&gt; seam (#1993, returns &lt;em&gt;both&lt;/em&gt;
surfaces), the &lt;code dir=&quot;auto&quot;&gt;locate_project_root&lt;/code&gt; collapse (#1971-tail), and the ownership existence-check
(#1888, verify-and-close) are the write/static end of the same superset. &lt;strong&gt;Guardrails:&lt;/strong&gt; keep
&lt;code dir=&quot;auto&quot;&gt;ExecutionContext&lt;/code&gt; action-scoped (no god-object); keep the three C-LANES-1 surfaces as three
fragments; tests pin &lt;em&gt;which fragment&lt;/em&gt; is consumed, not just the value (byte-identity masks
wrong-fragment conflation under flattened topology). Full research:
&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/tree/main/docs/archive/plans/engineering-notes/naming-identity-ssot-strangler&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;docs/archive/plans/engineering-notes/naming-identity-ssot-strangler/&lt;/code&gt;&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Other core domains (status, coordination write-side, lanes) follow as later 3.2.x slices or roll to
3.3.x as they emerge.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h3 id=&quot;g3--devex--enablers&quot;&gt;G3 — DevEx &amp;#x26; enablers&lt;/h3&gt;
&lt;p&gt;Lower the cost of the above and of contributing generally: pure-seam extractions for testability
(e.g. #1993 removes ~12 mocks), the regression-proof &lt;strong&gt;ratchets/guards&lt;/strong&gt; that make a strangled class
stay strangled, and the &lt;strong&gt;maintainer governance surface&lt;/strong&gt; (this &lt;code dir=&quot;auto&quot;&gt;docs/release-goals/&lt;/code&gt; convention +
&lt;a href=&quot;/operations/how-to-maintain/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;how-to-maintain.md&lt;/code&gt;&lt;/a&gt; — tracker structure, priorities, types, milestones).&lt;/p&gt;
&lt;h2 id=&quot;evidence-trail--dialectic--neutral-scoring-read-this-before-trusting-any-metric&quot;&gt;Evidence trail — dialectic + neutral scoring (read this before trusting any metric)&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Honesty note (supersedes the earlier “evidence-grounded” framing).&lt;/strong&gt; The first corroboration squad
was briefed to &lt;em&gt;corroborate the operator’s goals&lt;/em&gt;, which primed it toward agreement. A red-team squad
then refuted the &lt;strong&gt;framing, the metrics-as-proof, and the sequencing&lt;/strong&gt; (it did &lt;em&gt;not&lt;/em&gt; refute that the
engineering is real). A subsequent &lt;strong&gt;neutral scoring panel&lt;/strong&gt; (severity · ROI · architecture) scored
the candidate 3.2.1 leads with no predetermined answer. The honest, surviving statements:&lt;/p&gt;
&lt;/blockquote&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;The goals are legitimate operator &lt;em&gt;intent&lt;/em&gt;, not a “proven data-driven continuation.”&lt;/strong&gt; The
underlying epics (#1619/#1666/#1868/#1878) are real and pre-exist v3.1.10; the taxonomy mapping them
to G1/G2/G3 was authored after the fact. Treat the goals as direction, not as something the metrics
“prove.”&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The static &lt;code dir=&quot;auto&quot;&gt;branch_naming&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;mid8()&lt;/code&gt; seam is a genuine, sound SSOT&lt;/strong&gt; — this survived every
adversarial pass. The cheap routing of the bare &lt;code dir=&quot;auto&quot;&gt;mission_id[:8]&lt;/code&gt; sites through it is a real, low-risk
win.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Stop citing the confounded metrics as proof.&lt;/strong&gt; “−76% status bypass”, “authorities cooled”,
“+550% &lt;code dir=&quot;auto&quot;&gt;mission_id[:8]&lt;/code&gt;” measure &lt;em&gt;syntax / per-block complexity&lt;/em&gt;, not coupling quality; system-level
&lt;code dir=&quot;auto&quot;&gt;src/&lt;/code&gt; SLOC grew &lt;strong&gt;+115%&lt;/strong&gt; in range and &lt;strong&gt;no legacy path was retired&lt;/strong&gt; (extract-then-coexist). The
ratchet is a useful &lt;strong&gt;regression tripwire&lt;/strong&gt;, not a completeness oracle (it passes today with ~20 live
&lt;code dir=&quot;auto&quot;&gt;[:8]&lt;/code&gt; sites and is defeated by &lt;code dir=&quot;auto&quot;&gt;mid[:8]&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;[0:8]&lt;/code&gt;/helper shape-shifts).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;“Thread the &lt;code dir=&quot;auto&quot;&gt;ExecutionContext&lt;/code&gt; everywhere” is NOT the spine&lt;/strong&gt; — the composite is built-and-parked,
mutable, and internally split-brained (&lt;code dir=&quot;auto&quot;&gt;branch_name ≠ branch_ref.target_branch&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;resolution.py:793-801&lt;/code&gt;). Fixing &lt;em&gt;that&lt;/em&gt; is a separate, later builder-hardening effort, not this slice.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Neutral 3.2.1 scoring verdict:&lt;/strong&gt; all three scorers leaned &lt;strong&gt;impact-first&lt;/strong&gt; — open the
write-side/single-resolution authority surface (#1832 → #1716), demote naming to a parallel rider.
&lt;strong&gt;The operator chose safety-first&lt;/strong&gt; (the naming rider as the opener) as a deliberate low-risk-momentum
trade-off — explicitly a &lt;em&gt;values choice, not a data verdict&lt;/em&gt;. This declaration follows that choice:
naming-rider-first below, with the impact work sequenced as fast-following 3.2.x patches. Full evidence
and the decision record:
&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/tree/main/docs/archive/plans/engineering-notes/3-2-x-goal-corroboration&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;docs/archive/plans/engineering-notes/3-2-x-goal-corroboration/&lt;/code&gt;&lt;/a&gt;
(&lt;code dir=&quot;auto&quot;&gt;SCORING-SYNTHESIS.md&lt;/code&gt; · &lt;code dir=&quot;auto&quot;&gt;DIALECTIC-SYNTHESIS.md&lt;/code&gt;).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Operator bug evidence intake (#2007, 2026-06-16):&lt;/strong&gt; the “3.2.0 training bugs that Robert witnessed”
validate the same coord/read-path and mission-identity surface in this PR (&lt;code dir=&quot;auto&quot;&gt;STATUS_READ_PATH_NOT_FOUND&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;MISSION_NOT_FOUND&lt;/code&gt;, finalizer missing &lt;code dir=&quot;auto&quot;&gt;spec.md&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; in coord worktrees, and implement/finalize
re-reading a different surface than the one the prior step created). They also add important
&lt;strong&gt;non-overlap&lt;/strong&gt; evidence: command-contract drift (&lt;code dir=&quot;auto&quot;&gt;doctrine list&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;setup-plan&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;agent action implement --json&lt;/code&gt;), stale-charter preflight/status loops, submodule/gitfile root resolution, decision
command mission-path semantics, and raw Python template import failures. Treat #2007 as an expansion of
the 3.2.x evidence base: fold overlapping single-resolution bugs into the #1832/#1716/#1878 fast-follow,
and track the non-overlap items as separate DevEx/runtime repair work. The naming rider alone is not a
complete explanation or fix for the witnessed 3.2.0 training failures.&lt;/p&gt;
&lt;h2 id=&quot;non-goals--33x-or-later&quot;&gt;Non-goals (→ 3.3.x or later)&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;UX / dashboard look-and-feel, user flows, SaaS tie-in&lt;/strong&gt; — the 3.3.x focus.&lt;/li&gt;
&lt;li&gt;Extracting &lt;strong&gt;other emergent domains&lt;/strong&gt; beyond the core set — surfaced and split in 3.3.x.&lt;/li&gt;
&lt;/ul&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Superseded non-goal (operator decision):&lt;/strong&gt; the #1878 coord/primary write-side strangler
(placement-routing &lt;em&gt;and&lt;/em&gt; commit/protected-branch durability) was previously tracked to 3.3.x here.
It now sits entirely in 3.2.x/G2 above — see the coord-primary-partition-lock mission (placement
slice) and its 3.2.x fast-follow (durability slice).&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id=&quot;success-criteria-cycle-closes-when-these-hold&quot;&gt;Success criteria (cycle closes when these hold)&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;G1:&lt;/strong&gt; doctrine/DRG demonstrably gates a runtime decision path (with a test proving the
directive/contract changes behaviour), not just resolves.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;G2:&lt;/strong&gt; the naming/identity/read-path class produces &lt;strong&gt;zero new regressions&lt;/strong&gt; for a full cycle;
consumers route through the SSOT (no inline &lt;code dir=&quot;auto&quot;&gt;mission_id[:8]&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;kitty/mission-{…}&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;.worktrees/…&lt;/code&gt;/
&lt;code dir=&quot;auto&quot;&gt;parents[N]&lt;/code&gt; outside the seams); the ratchet covers the full recurrence shape &lt;strong&gt;repo-wide incl.
&lt;code dir=&quot;auto&quot;&gt;dashboard/scanner.py&lt;/code&gt;&lt;/strong&gt;, and its allow-list &lt;strong&gt;shrinks&lt;/strong&gt;; ≥1 additional core domain extracted.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;G3:&lt;/strong&gt; the DevEx enablers landed (seam extractions + ratchets + governance docs) are in use; no new
shadow path introduced cycle-wide.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;emergent-patches&quot;&gt;Emergent patches&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;3.2.1 — naming routing rider&lt;/strong&gt; (the deliberate low-risk opener; &lt;em&gt;chosen over&lt;/em&gt; the impact lead the
neutral panel preferred). Route the ~20 bare &lt;code dir=&quot;auto&quot;&gt;mission_id[:8]&lt;/code&gt; sites through &lt;code dir=&quot;auto&quot;&gt;resolve_mid8&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;mid8()&lt;/code&gt;,
extend the literal-ban ratchet &lt;strong&gt;as a tripwire&lt;/strong&gt; (scoped honestly — partial, syntax-level), land the
&lt;code dir=&quot;auto&quot;&gt;resolve_lanes_dir&lt;/code&gt; (#1993) / &lt;code dir=&quot;auto&quot;&gt;locate_project_root&lt;/code&gt; (#1971) seams, and verify-and-close #1888.
&lt;strong&gt;Sequencing constraint (binding):&lt;/strong&gt; #1993 must &lt;strong&gt;not&lt;/strong&gt; ship as a bare extraction — extracting
&lt;code dir=&quot;auto&quot;&gt;resolve_lanes_dir&lt;/code&gt; alone half-strangles the read path into a new shadow path (the &lt;code dir=&quot;auto&quot;&gt;_lanes_feature_dir&lt;/code&gt;
twin). Either carry a minimal read-side adoption of the new seam in the same WP, or defer #1993 to the
write-side patch with #1832.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;3.2.2 — write-side / single-resolution surface&lt;/strong&gt; (the impact work the panel ranked first, sequenced
to fast-follow). Open with &lt;strong&gt;#1832&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;agent action implement&lt;/code&gt; “no workspace resolved” — the safe,
verified P1 that proves “consume the resolved context, don’t re-derive”), drive to &lt;strong&gt;#1716&lt;/strong&gt; (P0
coord-topology authority root, keystone of #1619/#1878). Re-test &lt;strong&gt;#1827&lt;/strong&gt; first (it may be stale —
the neutral panel could not reproduce the circular failure); fast-follow if real, close-with-evidence
if not.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;3.2.x (parallel / emergent)&lt;/strong&gt; — the &lt;strong&gt;#1619 builder-hardening slice&lt;/strong&gt; (un-mutate the
&lt;code dir=&quot;auto&quot;&gt;ExecutionContext&lt;/code&gt; builder, close the internal &lt;code dir=&quot;auto&quot;&gt;branch_name ≠ branch_ref.target_branch&lt;/code&gt; invariant);
the &lt;strong&gt;#1891 residual&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;agent action implement --json&lt;/code&gt;, independent DevEx); G1 doctrine/DRG-into-
runtime depth; the next core-domain strangle. Shapes pinned as each is scoped.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Tracker hygiene (do regardless of lead):&lt;/strong&gt; milestone the currently-unmilestoned P0/P1 work
(#1716, #1827, #1832, #1891, #1619/#1666) onto 3.2.x/3.3.x — the milestone currently holds only the
(now-closed) naming issues, so the burndown understates the real cycle.&lt;/li&gt;
&lt;li&gt;Cycle stays &lt;strong&gt;open&lt;/strong&gt; until all three goals’ success criteria hold.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;links&quot;&gt;Links&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Milestone: &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/milestone/4&quot;&gt;https://github.com/Priivacy-ai/spec-kitty/milestone/4&lt;/a&gt; · Convention:
&lt;a href=&quot;/changelog/release-goals/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;README.md&lt;/code&gt;&lt;/a&gt; · Next cycle: &lt;a href=&quot;/changelog/3.3.x/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;3.3.x.md&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Research (G2 first slice): &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/blob/main/docs/archive/plans/engineering-notes/naming-identity-ssot-strangler/00-OVERVIEW.md&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;00-OVERVIEW.md&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Baseline shipped: &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/milestone/3&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;3.2.0&lt;/code&gt;&lt;/a&gt; (PR #2001)&lt;/li&gt;
&lt;li&gt;Tracker (G2 first slice): #2000 · #1971 · #1993 · #1888 · #1900&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
