Section 08: Migration Pass — Backfill subsumes: on Candidate Plans

Goal: Bring existing plans into the subsumption framework so the routing rule has populated examples from day one. Without this, §01-§07 ship as empty infrastructure and the framework’s value is invisible until new plans land.

Success Criteria: see frontmatter.

Implementation Sketch

The migration follows the standard three-step pattern:

1. Enumerate candidates via subsystem-overlap heuristic. For each non-completed plan, compute plan.touches: ∩ bug.subsystem for every open bug. Plans with non-trivial overlap are candidates.
2. Apply 3-signal test per candidate. Subsumption is asserted, not inferred (§01 banned pattern); the migration surfaces each candidate’s bug-list for the plan’s author or a reviewer to confirm/reject claims via batched AskUserQuestion.
3. Backfill claims + verify. Each confirmed claim writes through §02’s classifier path (which guarantees bidirectional pointers + status flip + HISTORY entries); §07’s completion-gate verification runs ONCE per claim at migration time to ensure claim well-formedness.

aims-burden-tracking is the canonical first migration target — its 00-overview.md §Motivation lists exactly the bug pattern (BUG-04-104, 106, 107, 111, 118 — bugs that the plan’s re-architecture is intended to dissolve). Other candidates are speculative until the migration script enumerates them.

Implementation Items

• §08.1 Author scripts/plan_corpus/migrate_subsumption_claims.py (or extend existing migrations/003_subsumption_fields.py from §05). Algorithm:
  • Pass 1: enumerate non-completed plans with touches: populated.
  • Pass 2: for each, query bugs-for <subsystem> (intel graph) for each path in touches:. Collect candidate bug-set.
  • Pass 3: surface candidates via AskUserQuestion (batched per plan, per §02 batching discipline). Recommended option per ask-user-question.md.
  • Pass 4: write classifications per §02 protocol (bidirectional, status flip, HISTORY).
  • Pass 5: invoke §07 completion-gate verification once per claim; record verification outcome.
• §08.2 Run migration against plans/aims-burden-tracking/. Pre-flight check: aims-burden-tracking.status != complete (else PLAN_BOUNDARY, abort with error). Read aims-burden-tracking/00-overview.md §Motivation for the explicit bug list (BUG-04-104, 106, 107, 111, 118). For each, apply 3-signal test:
  • re-architecture: aims-burden-tracking replaces AIMS realization-time predicate stack with two-layer Perceus architecture. YES, re-architects the subsystem.
  • non-reproduction: the proposal’s success criteria include “16 BUG-04-118 originally-failing tests pass”. YES.
  • symptom-of-replaced-architecture: bugs are explicitly traced to predicate-stack-defects (PIN-1..6 stack, SSA-alias-class graph). YES.
  • All three signals fire → subsumption claim valid. Backfill subsumes: [BUG-04-104, ...] on aims-burden-tracking overview; cross-write subsumed_by: plans/aims-burden-tracking/ on each bug.
• §08.3 Apply migration to other surfaced candidates. Run script’s enumeration; surface results for review. Plans likely surfaced (verify during execution): typeck-inference-completeness, repr-opt, perf-engineering, enum-layout-ssot, iterator-element-ownership. Some may have ZERO matching bugs; some may have N. Apply 3-signal test per candidate; commit only confirmed claims.
• §08.4 Run §07’s completion-gate verification across every authored claim (pre-completion mode — bugs are still in their fresh subsumed state; verification confirms the failing-test reference is well-formed). Cases failing verification: surfaced as MIGRATION_VERIFICATION_FAIL findings (do NOT auto-revert; require human review per §01 banned pattern on mechanical inference).
• §08.5 Author migration audit log. This plan’s HISTORY block gains entries per migrated plan: “YYYY-MM-DD — Migrated plans/<name>/. Subsumption claims authored: [BUG-list]. Verification outcomes: [pass-list, fail-list, unverifiable-list].” Each migrated plan’s 00-overview.md HISTORY also gets a per-migration entry citing this plan as source.

Test Strategy

Test matrix:

Semantic pins:

• Positive: aims-burden-tracking migration produces subsumes: [BUG-04-104, BUG-04-106, BUG-04-107, BUG-04-111, BUG-04-118] (or subset matching 3-signal-confirmed claims); each bug’s subsumed_by: points back. Reverting the migration unmakes both sides.
• Negative: skill-ecosystem-coherence is enumerated as a candidate (it has touches:) but the migration MUST skip it (fork hard constraint — ecosystem is the SSOT host of the rule itself, not a subsumption candidate). Test that this guard fires.
• Idempotency: re-running migration on already-migrated plan reads existing subsumes:, skips already-confirmed claims, surfaces only newly-eligible bugs (filed since last migration run).

Intelligence Reconnaissance

(2026-05-09) Section authors scripts/plan_corpus/migrate_subsumption_claims.py (or extension to §05’s 003_subsumption_fields.py). Targets are existing plans (plans/aims-burden-tracking/, plans/typeck-inference-completeness/, plans/repr-opt/, plans/perf-engineering/, etc.) and bugs in bug-tracker/plans/. Pre-migration query: scripts/intel-query.sh plan-status aims-burden-tracking (verify status != complete; abort if completed); scripts/intel-query.sh bugs-for aims-burden-tracking (enumerate currently-blocking bugs). At migration time per compose-intel-summary.md Step D, full bugs-for <plan> queries MUST run for each candidate plan to surface fresh bug-state. Recording recon-deferred until §08 implementation. Cross-references verified by direct Read: plans/aims-burden-tracking/00-overview.md §Motivation (BUG-04-104, 106, 107, 111, 118 explicit list verified), plans/aims-burden-tracking/index.md (status: not-started verified — eligible for migration per §08 PLAN_BOUNDARY guard). Migration MUST NOT touch plans/skill-ecosystem-coherence/ (fork hard-constraint per §08 success criterion).

Cross-References

• §01 — routing rule + 3-signal test the migration applies.
• §02 — classifier protocol the migration invokes per claim.
• §05 — schema fields the migration reads/writes.
• §06 — intel-graph edges the migration triggers (via :Plan SUBSUMES :Bug edge synthesis on next refresh).
• §07 — verification gate the migration invokes once per claim.
• plans/aims-burden-tracking/00-overview.md §Motivation — explicit bug-list for the canonical first migration.
• feedback_auto_fix_cleanup.md — does NOT apply to subsumption claims (claims are asserted, not auto-cleaned per §01 banned pattern); applies only to dead-pointer cleanup per §03.

08.1

Author migration script (subsystem-overlap candidate enumeration)

• (placeholder — replace with concrete work that closes subsection 08.1)

08.2

Apply migration to plans/aims-burden-tracking/ (canonical first candidate)

• (placeholder — replace with concrete work that closes subsection 08.2)

08.3

Apply migration to other surfaced candidates (typeck-inference-completeness, repr-opt, perf-engineering, etc.)

• (placeholder — replace with concrete work that closes subsection 08.3)

08.4

Run §07 verification on every authored claim; record outcomes

• (placeholder — replace with concrete work that closes subsection 08.4)

08.5

Author migration audit log (HISTORY entries on this plan + each migrated plan)

• (placeholder — replace with concrete work that closes subsection 08.5)

08.R

Third Party Review Findings

• (placeholder — replace with concrete work that closes subsection 08.R)

08.N

Completion Checklist

• (placeholder — replace with concrete work that closes subsection 08.N)

HISTORY

(Empty at plan creation; populated per-migration during §08.5 execution.)