fix: wave-5 readiness — second SSOT ID remap #27-#32 → #31-#36 (AIF Handoff overlap closure) - #32
Merged
Merged
Conversation
…nator DEFER (SSOT #28 update, #30 new) AIF primitives deep-dive follow-up (2026-05-11) — two primitives from the aif-handoff-overlap mandate that were DEFER'd or out-of-scope: Primitive A (paused:true/false, SSOT #28): - ADAPT (Variant B): `status:` frontmatter convention in wave kickoff files; grep-able state without a separate wave-status.md or CI gate - SSOT #28 trigger lowered: «>10 waves» → «≥3 simultaneous waiting states OR pipeline automation»; partial adopt noted inline - wave-5-tool-bootstrapping/orchestrator-kickoff.md: <!-- status: waiting-for-implementation --> Primitive B (implement-coordinator, SSOT #30 new): - DEFER: coordinator pattern solves autonomous-dispatch GAPs (dependency graph, worker status tracking, circular-dep detection) but all GAPs exist only in autonomous mode — project has no such use case - Mode B + human-orchestrated batches adequate at current scale - Trigger: autonomous batches ≥3 waves OR #mode-b-ordering-error in ≥2 patches Research patch delivered by Sonnet deep-dive session: docs/meta-factory/research-patches/2026-05-11-aif-primitives-deep-dive.md (257 lines, <!-- scope:aif-handoff-mandate -->, ≤500 ✅) Prior-art: skipped — research patch + SSOT updates only, no new capability artifact
…32 → #31-#36 (AIF Handoff collision fix) 2026-05-11 readiness review on `fix/wave-5-readiness-revise` identified BLOCKER B-1: the branch's own AIF Handoff overlap analysis (commits `5d8cf1c`, `0f7f572`) landed SSOT entries #27-#30 in `prior-art-evaluations.md` for HANDOFF_MODE / paused-semantic / handoff:task / implement-coordinator — re-occupying the range previously remap'd to in `d7a6c87` for Wave 5 §13.25 candidates. Remap §10 table + all cross-references in §4 (Continue permissions SSOT ref), §10 narrative (Next ID / entries #1-#N), §12 Implementation outline, §13.1 Forward-check anti-pattern row, See also block. Added explicit §10 footnote logging the second remap for future readers. Mapping: 27 AIF /aif → 31 28 AIF skills.sh → 32 29 Continue permissions → 33 30 Cline marketplace → 34 31 Codex MCP CLI → 35 32 Roo Code installer → 36 Operator-side kickoff (`.claude/orchestrator-prompts/wave-5-tool-bootstrapping/orchestrator-kickoff.md`, gitignored) updated in lockstep: m2 Windsurf ID #33 → #37 (next-free after new range); SCOPE block acknowledges «#27-#30 AIF Handoff occupied»; ATTN STOP rule baseline updated to existing entries #1-#30. Closes readiness-review M-1 (research §10 not yet edited for the new collision) and addresses root cause of BLOCKER B-1. Push + CI-green on HEAD is the remaining operator action before B-1 is fully closed. Non-touched: existing SSOT entries #1-#30 (Wave 7 #16-#26 + AIF Handoff #27-#30); AIF /aif row's «entry #8 cadence» reference unchanged. Doc errata only — not a capability commit per CLAUDE.md gate; not a §1.7 rule extension. Prior-art: skipped — doc errata only (second SSOT-ID remap parallel to d7a6c87 precedent), no new capability per CLAUDE.md gate; resolves readiness-review BLOCKER B-1 + MAJOR M-1 (2026-05-11) on `fix/wave-5-readiness-revise` umbrella.
4 tasks
This was referenced May 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes BLOCKER B-1 + MAJOR M-1 + MINOR m-1 from 2026-05-11 readiness review on
fix/wave-5-readiness-revise(post-PR #31 follow-up).5d8cf1c,0f7f572) re-occupied the previously-remap'd range with HANDOFF_MODE / paused-semantic / handoff:task / implement-coordinator entries.d7a6c87first remap pointer + new range + AIF Handoff commit refs).Why
PR #31's
d7a6c87remap'd Wave 5 IDs from original #16-#21 → #27-#32 to escape the Wave 7 collision. On the same branch the AIF Handoff overlap analysis (also part of PR #31's lineage) then landed SSOT entries #27-#30 — different content, same IDs — re-establishing the collision. Readiness review caught it before Wave 5.1 orchestrator launch could land §10 entries atomically.Mapping
Cross-references updated in §4 (Continue permissions SSOT ref), §10 (Next ID / entries #1-#N narrative + footnote), §12 Implementation outline, §13.1 Forward-check anti-pattern row, See also.
How to verify
grep -nE '^\| (27\|28\|29\|30\|31\|32) ' docs/meta-factory/research-patches/2026-05-10-§13.25-tool-bootstrapping-research.md→ no hits (all rows now 31-36)audit-self,framework-self-template-render,discipline-self-check,workflow-integrity)5d8cf1c+0f7f572§1.7 Forward-check applied
Recommendation = doc errata only (SSOT-ID remap to resolve collision); not a new rule/principle/discipline. Forward-check against currently active layers:
packages/core/<rules>/modified.packages/core/principles/*.test.ts):make self-auditlocal run → 10 files / 56 tests / 0 failures (pre-push hook output above). Principle 08 (Prior-art cited) unaffected — escape-hatch trailerPrior-art: skipped — doc errata only ...with rationale ≥20 chars (CLAUDE.md compliant). Principle 09 (doc-authority hierarchy) unaffected — research-patches file inherits folder authority fromresearch-patches/README.md; no new authority-bearing artefact created.What is a capability commit?): not capability — no newpackage.jsondep, no new ≥50 LOC file under newpackages/core/<new-dir>/, no new ≥80 LOC file anywhere underpackages/. Diff stat: 1 file, +18/-16 lines.prior-art-evaluations.md): not modified by this PR; existing entries feat: audit fixes Phase 1+2+3 (R2/R11 drift, manifest SSOT, depcruise integration) #1-docs(wave-5): readiness REVISE fixes — SSOT ID remap + §13.25 status #30 untouched. The remap is to research-side proposal IDs, not SSOT-landed rows.open-questions.md§13.x): §13.25 status unchanged («research merged → review GO → implementation pending»); §13.21 closure (Wave 1+2) intact; no new trigger introduced.doc-authority-hierarchy.md): research file's Authoritative-for header inherited from folder (research-patches/); not amended by this change.All six layers green; no recommendation-skips-own-discipline gap.
§1.7 Backward-check applied
This PR introduces no new rule/discipline whose scope sweep would apply. Nevertheless, completed exhaustive backward sweep of artefacts affected by the ID-remap itself:
grep -nE '#(27|28|29|30|31|32)'; all updated to the new fix: wave-5 readiness — AIF Handoff overlap analysis + scope annotations (SSOT #27-#29) #31-fix(install): wave-5 follow-up — SHIPPED_DOCS sync + N3 stat-fallback comment #36 range using staged replace_all (high→low to avoid forward-collision). Table rows docs(research-patches): Wave 6 AI-doc cold audit (§13.26) #27→fix(install): wave-5 follow-up — SHIPPED_DOCS sync + N3 stat-fallback comment #36 renumbered individually. Post-edit verify grep returned no stale Wave 5 docs(research-patches): Wave 6 AI-doc cold audit (§13.26) #27-docs(wave-5): readiness REVISE fixes — SSOT ID remap + §13.25 status #30 references. §10 footnote added perd7a6c87/kickoff:55 precedent logging the second remap.entry #27→entry #31), §13.1 (Forward-check anti-pattern rowentry #27→entry #31), §13.3 (entry #29cross-link →entry #33), See also (entries docs(research-patches): Wave 6 AI-doc cold audit (§13.26) #27-fix: wave-5 readiness — second SSOT ID remap #27-#32 → #31-#36 (AIF Handoff overlap closure) #32 → fix: wave-5 readiness — AIF Handoff overlap analysis + scope annotations (SSOT #27-#29) #31-fix(install): wave-5 follow-up — SHIPPED_DOCS sync + N3 stat-fallback comment #36, AIF /aif docs(research-patches): Wave 6 AI-doc cold audit (§13.26) #27 → fix: wave-5 readiness — AIF Handoff overlap analysis + scope annotations (SSOT #27-#29) #31)..claude/orchestrator-prompts/wave-5-tool-bootstrapping/orchestrator-kickoff.md, gitignored — outside this PR but swept locally): 5 sites updated — m2 entries docs(research-patches): Wave 6 AI-doc cold audit (§13.26) #27-fix: wave-5 readiness — second SSOT ID remap #27-#32 → #31-#36 (AIF Handoff overlap closure) #32 → fix: wave-5 readiness — AIF Handoff overlap analysis + scope annotations (SSOT #27-#29) #31-fix(install): wave-5 follow-up — SHIPPED_DOCS sync + N3 stat-fallback comment #36 + ID 33 → 37; Rationaleentry #27→entry #31; SCOPE block + ATTN STOP baseline + Prior-art trailer guidance.git diff origin/main..HEAD --name-onlyreturns only the single research-patches file.Self-reflexive trigger (§1.7 applies to itself): this PR is doc errata, not a discipline-bearing artefact, so it does not require its own self-review patch under
research-patches/. The remap itself is the second iteration of thed7a6c87pattern; structural fragility («SSOT ID pre-allocation breaks under interim landings») was already flagged in the readiness review §4 ATTN for future research-patch consideration if the pattern recurs once more.2026-05-12 retroactive Wave 8.5 note: This PR's §1.7 Forward-check section would not pass the Wave 8.1 substance gate (no file:line citations present). Pre-Wave-8 acceptance — kept as historical evidence of the
#discipline-theatregap that motivated §13.29.