<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/adr/3.x/2026-05-11-1-defer-391-structural-extraction-from-3-2-x/">
  <id>https://docs.spec-kitty.ai/adr/3.x/2026-05-11-1-defer-391-structural-extraction-from-3-2-x/</id>
  <title>Defer #391 still-open structural extraction sub-tickets from the 3.2.x stabilization scope</title>
  <updated>2026-05-11T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/adr/3.x/2026-05-11-1-defer-391-structural-extraction-from-3-2-x/"/>
  <summary>Keeps three open structural-extraction tickets out of the 3.2.x stabilization scope, since refactors with no release-blocking symptom inflate regression risk.</summary>
  <content type="html">&lt;ul&gt;
&lt;li&gt;Epic &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/822&quot;&gt;#822&lt;/a&gt; — 3.2.0 stabilization and release readiness&lt;/li&gt;
&lt;li&gt;Epic &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/992&quot;&gt;#992&lt;/a&gt; — drain the bug queue by repairing domain boundaries&lt;/li&gt;
&lt;li&gt;Epic &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/391&quot;&gt;#391&lt;/a&gt; — Tech/Functional Debt Remediation&lt;/li&gt;
&lt;li&gt;Still-open #391 sub-tickets: #612, #613, #614&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;h2 id=&quot;context-and-problem-statement&quot;&gt;Context and Problem Statement&lt;/h2&gt;
&lt;p&gt;The 3.2.x stabilization mission (canonical: &lt;code dir=&quot;auto&quot;&gt;kitty-specs/review-merge-gate-hardening-3-2-x-01KRC57C/&lt;/code&gt;) was scoped during planner intake to cover the remaining P1 bugs that have no active PR (#985, #987, #986, #983, #984), plus a narrowed slice of the encoding chokepoint work (#644). The original &lt;code dir=&quot;auto&quot;&gt;kitty-specs/_drafts/&lt;/code&gt; scratch was removed after the canonical mission absorbed all its content.&lt;/p&gt;
&lt;p&gt;During scope review, the question arose whether the still-open sub-tickets of #391 — namely #612 (extract runtime/mission decisioning boundary), #613 (glossary as a functional module), and #614 (separate integration boundaries inside &lt;code dir=&quot;auto&quot;&gt;src/specify_cli&lt;/code&gt;) — should also be folded into the same mission.&lt;/p&gt;
&lt;p&gt;This decision matters because epic #822 explicitly defines anti-scope for the 3.2.x stable release:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;“This epic is scoped to release blockers, workflow correctness, and low-risk stabilization. It should not absorb speculative product expansion.”&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;And:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;“No silent state-transition loss, no contaminated review prompts, no misleading success/failure output after local state changes, no merge result that is locally ‘done’ but not shippable …”&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;The still-open #391 children are &lt;strong&gt;structural module-extraction refactors&lt;/strong&gt;, not bug fixes for any of those release-blocking symptoms.&lt;/p&gt;
&lt;h2 id=&quot;decision-drivers&quot;&gt;Decision Drivers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Release-scope discipline.&lt;/strong&gt; #822 anti-scope is explicit: stabilization missions must not absorb structural work without a current release-blocking repro tying the refactor to a symptom on the blocker list.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Regression-confidence isolation.&lt;/strong&gt; Co-resident P1 bug fixes and large module moves inflate the diff surface and weaken bisection / review confidence for the bug fixes specifically.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Precedent.&lt;/strong&gt; The shared-package-boundary cutover mission (&lt;code dir=&quot;auto&quot;&gt;shared-package-boundary-cutover-01KQ22DS&lt;/code&gt;, 2026-04-25) established the pattern of doing module-boundary work as a discrete mission with its own architectural-enforcement tests — not as a side WP of a bug-fix mission.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Partial supersession.&lt;/strong&gt; The shared-package-boundary cutover already enforces the runtime/events/tracker boundary architecturally (see &lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_shared_package_boundary.py&lt;/code&gt;), which means #612 is at minimum partially superseded; its remaining scope needs re-evaluation before it can be planned, not bundled.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;No current repro on the bug queue.&lt;/strong&gt; None of #612 / #613 / #614 appears on any current open &lt;code dir=&quot;auto&quot;&gt;bug&lt;/code&gt; issue’s repro chain as a contributing cause.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;considered-options&quot;&gt;Considered Options&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;(A) Defer all three&lt;/strong&gt; to a post-3.2 boundary-cleanup mission.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;(B) Accept a narrowed subset&lt;/strong&gt; with a current repro tying it to a release blocker — that subset would still need its own mission, not co-resident WPs.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;(C) Fold all three into the 3.2.x review/merge gate-hardening mission as additional WPs.&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;decision-outcome&quot;&gt;Decision Outcome&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Chosen option: (A) Defer all three&lt;/strong&gt;, because the still-open #391 sub-tickets are structural refactors without a current release-blocking symptom, and folding them into a stabilization mission would directly violate #822’s anti-scope while inflating regression risk on the P1 bug fixes the mission is meant to ship.&lt;/p&gt;
&lt;h3 id=&quot;consequences&quot;&gt;Consequences&lt;/h3&gt;
&lt;h4 id=&quot;positive&quot;&gt;Positive&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;The 3.2.x mission keeps a tight bug-fix surface (WP01–WP06) with clean per-WP regression isolation.&lt;/li&gt;
&lt;li&gt;Mission review can attest to release-blocker closure without entangled module-move review.&lt;/li&gt;
&lt;li&gt;#612 in particular gets re-scoped &lt;em&gt;after&lt;/em&gt; the shared-package-boundary cutover’s enforcement tests, which is a cleaner planning input than the original 2026-04 framing.&lt;/li&gt;
&lt;li&gt;Future operators reading #391 see an explicit deferral record rather than silent omission.&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&quot;negative&quot;&gt;Negative&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;The #391 epic remains formally open and continues to accrue staleness signal until the post-3.2 boundary-cleanup mission is scheduled.&lt;/li&gt;
&lt;li&gt;Operators expecting “just one more cleanup pass” will see the deferral and may push to revisit — owner needs a short answer ready (“post-3.2, separate mission, see ADR 2026-05-11-1”).&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&quot;neutral&quot;&gt;Neutral&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;No code is modified by this decision.&lt;/li&gt;
&lt;li&gt;The deferred tickets remain in the GitHub backlog with their existing labels.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;confirmation&quot;&gt;Confirmation&lt;/h3&gt;
&lt;p&gt;This decision is correct if, after the 3.2.x review/merge gate-hardening mission lands:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;No P1 bug closed by the mission relies on logic the deferred refactors would have moved.&lt;/li&gt;
&lt;li&gt;The 3.2.x mission’s review report (per WP03’s new contract) does not record any structural-extraction findings as deferred risk.&lt;/li&gt;
&lt;li&gt;A follow-up planning pass against #391 can re-scope #612/#613/#614 on top of the now-enforced shared-package boundary without rework against this mission’s diff.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If those signals hold, the deferral preserved release velocity without losing the underlying debt.&lt;/p&gt;
&lt;h2 id=&quot;pros-and-cons-of-the-options&quot;&gt;Pros and Cons of the Options&lt;/h2&gt;
&lt;h3 id=&quot;a-defer-all-three&quot;&gt;(A) Defer all three&lt;/h3&gt;
&lt;p&gt;Push #612, #613, #614 to a post-3.2 boundary-cleanup mission with its own decomposition pass.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Aligns with #822 anti-scope literally.&lt;/li&gt;
&lt;li&gt;Preserves bisection confidence on the P1 bug fixes.&lt;/li&gt;
&lt;li&gt;Allows #612 to be re-framed after the already-enforced shared-package boundary.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Leaves #391 open for at least one more release cycle.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;b-accept-narrowed-subset&quot;&gt;(B) Accept narrowed subset&lt;/h3&gt;
&lt;p&gt;Pull only the sub-ticket(s) with a current release-blocking repro into a &lt;em&gt;separate&lt;/em&gt; mission running alongside (not inside) the 3.2.x bug-fix mission.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Honors the “if it blocks the release, ship the cleanup” principle.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;No current repro qualifies any of #612/#613/#614 today; the option is hypothetical at best.&lt;/li&gt;
&lt;li&gt;Running two missions in parallel adds coordination cost (worktree contention, merge ordering) for no observed benefit.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;c-fold-all-three-into-the-32x-mission&quot;&gt;(C) Fold all three into the 3.2.x mission&lt;/h3&gt;
&lt;p&gt;Add #612/#613/#614 as additional WPs on the current branch.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;One mission closes one more epic.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Directly violates #822 anti-scope.&lt;/li&gt;
&lt;li&gt;Inflates diff surface; weakens regression confidence on WP01–WP06.&lt;/li&gt;
&lt;li&gt;Mixes two reviewer skill sets (bug-fix review vs. structural-extraction review) in one approval gate.&lt;/li&gt;
&lt;li&gt;Increases merge-conflict risk in &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;more-information&quot;&gt;More Information&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Canonical mission this ADR is attached to: &lt;code dir=&quot;auto&quot;&gt;kitty-specs/review-merge-gate-hardening-3-2-x-01KRC57C/spec.md&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Precedent for discrete module-boundary missions: &lt;a href=&quot;/adr/3.x/2026-04-25-1-shared-package-boundary/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;docs/adr/3.x/2026-04-25-1-shared-package-boundary.md&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Architectural enforcement tests that partially supersede #612: &lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_shared_package_boundary.py&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
