Wave 1 (§13.21): add Authoritative-for headers to 11 shipped surfaces - #21
Merged
Conversation
Wave 1 of §13.21 closure — per .claude/rules/doc-authority-hierarchy.md §3. Prior-art: skipped — Wave 1 prose-only header insert, no new capability under packages/core/<dir>/, no new dependency.
Wave 1 of §13.21 closure — per .claude/rules/doc-authority-hierarchy.md §3. Prior-art: skipped — Wave 1 prose-only header insert, no new capability under packages/core/<dir>/, no new dependency.
Wave 1 of §13.21 closure — per .claude/rules/doc-authority-hierarchy.md §3. Prior-art: skipped — Wave 1 prose-only header insert, no new capability under packages/core/<dir>/, no new dependency.
Wave 1 of §13.21 closure — per .claude/rules/doc-authority-hierarchy.md §3. Prior-art: skipped — Wave 1 prose-only header insert, no new capability under packages/core/<dir>/, no new dependency.
Wave 1 of §13.21 closure — per .claude/rules/doc-authority-hierarchy.md §3. Prior-art: skipped — Wave 1 prose-only header insert, no new capability under packages/core/<dir>/, no new dependency.
Wave 1 of §13.21 closure — per .claude/rules/doc-authority-hierarchy.md §3. Prior-art: skipped — Wave 1 prose-only header insert, no new capability under packages/core/<dir>/, no new dependency.
Wave 1 of §13.21 closure — per .claude/rules/doc-authority-hierarchy.md §3. Prior-art: skipped — Wave 1 prose-only header insert, no new capability under packages/core/<dir>/, no new dependency.
Wave 1 of §13.21 closure — per .claude/rules/doc-authority-hierarchy.md §3. Prior-art: skipped — Wave 1 prose-only header insert, no new capability under packages/core/<dir>/, no new dependency.
Wave 1 of §13.21 closure — per .claude/rules/doc-authority-hierarchy.md §3. Prior-art: skipped — Wave 1 prose-only header insert, no new capability under packages/core/<dir>/, no new dependency.
Wave 1 of §13.21 closure — per .claude/rules/doc-authority-hierarchy.md §3. Prior-art: skipped — Wave 1 prose-only header insert, no new capability under packages/core/<dir>/, no new dependency.
Wave 1 of §13.21 closure — per .claude/rules/doc-authority-hierarchy.md §3. Prior-art: skipped — Wave 1 prose-only header insert, no new capability under packages/core/<dir>/, no new dependency.
Editorial sync with sister preset-next-15 files (RULES.react-next.md, ARCHITECTURE.react-next.md, ARCHITECTURE.ts-server.md) — closes reviewer MINOR-1 stylistic inconsistency before PR #21 merge. Prior-art: skipped — Wave 1 prose-only header refinement, no new capability under packages/core/<dir>/, no new dependency.
Editorial sync with sister templates/shared/ files (ARCHITECTURE.ts-server.md) — closes reviewer MINOR-1 stylistic inconsistency before PR #21 merge. Prior-art: skipped — Wave 1 prose-only header refinement, no new capability under packages/core/<dir>/, no new dependency.
This was referenced May 9, 2026
artyhoo
added a commit
that referenced
this pull request
May 10, 2026
Post-merge bookkeeping per revision plan §14 (atomic-closure-with-merge note). Status flipped from «deferred» to «closed» now that all four Wave PRs have landed on main: - Wave 1 PR #21 - Wave 2 PR #22 - Wave 3 PR #23 - Wave 4 PR #24 No code changes. Doc-only edit; not a capability commit — no Prior-art: trailer required per CLAUDE.md detection rules.
9 tasks
artyhoo
added a commit
that referenced
this pull request
May 10, 2026
…Tool Bootstrapping Single deliverable file per Wave 5 research prompt. 14 sections (Problem / Source / §0 / §0.1 / §1-§13). 557 lines. Key findings: - O0 verdict: STOP-end-to-end-match-found. AIF /aif command (already integrated dep) implements user rules 1-4 end-to-end. Build-vs-reuse honor: do not silently re-build. Rules 5-6 (incrementality + reject-memory) are the load-bearing additions if implementation proceeds. - O0.1 trigger sweep: §13.18 (AIF deep alignment) HIGH cascade; §13.19 + §13.22 MEDIUM cascade; §13.21 CLOSED; §13.24 H7 sample size advances 1/3 → 2/3. - 6 SSOT entries proposed (#16-#21); orchestrator session lands them in atomic commit. - 9 binary/multi-choice decisions for review session (§11), each with explicit options and recommendations. - Sub-wave 5.1/5.2/5.3 implementation outline (~150-250 LOC total; not capability commits per CLAUDE.md threshold). - §1.7 forward+backward checks applied; self-reflection skill invoked at session start. No implementation; no shipped-artefact edits beyond this patch file. Branch carries preparatory §13.25 registration commit (0ea9bea) per Wave 5 PRE-LAUNCH step 3. Prior-art: skipped — research-patch documents prior-art findings rather than introducing new capability; SSOT proposals (§10) land in orchestrator session per prior-art-evaluations.md §3 step 1.
artyhoo
added a commit
that referenced
this pull request
May 10, 2026
…r reviewer REVISE Closes 1 BLOCKER + 2 MAJOR + 1 MINOR from reviewer pass on 98ef3ba. P1 (B1) — §10 SSOT schema fixed to 8 columns matching prior-art-evaluations.md §4 precedent (entries #1-#15): ID | Candidate | Capability matched | First seen | Last reviewed | Verdict | Rationale | Trigger to revisit Velocity moved from 9th-pseudo-column into Rationale field opener per #6-#10. First seen / Last reviewed = 2026-05-10 for all #16-#21. P2 (M1) — context7 phrasings backfill: - §1 (O1): +2 new queries (`/modelcontextprotocol/servers`, `/vercel/platforms` resolve). Material correction: SECURITY.md states reference servers «not production-ready»; §1 maturity column downgraded from «Mature/Official» to «Reference». - §3 (O3): +1 new query (`/websites/windsurf`); other 7 documented as «derived from O0 sweep». - §4-§8: each section gets one-line motivation explaining why no new query was needed (analytical / cognitive-probe / pattern-comparison objectives). P3 (M2) — rule-5 counter-prompt added to §0 as item 3: 2 phrasings against `/renovatebot/renovate` + `/sverweij/dependency-cruiser` + `/tj-actions/changed-files`. NULL result. Confirms «incrementality is gap in every surveyed framework» negative-existence claim. §13.3 `#negative-existence-claim` raised LOW → MEDIUM with explicit residual-risk acknowledgement. P4 (m1) — Windsurf gap closed AND classification raised: - §3 row revised: Windsurf Cascade detect-and-install + MCP Marketplace one-click deeplink + `pre_mcp_tool_use` hook surfaced. Second partial-end-to-end candidate alongside AIF. - §3 conclusion updated: «AIF and Windsurf Cascade» (not just AIF) carry the discover-env-→-propose/install shape. - §13.3 `#category-sweep-missed` LOW → MEDIUM. `#prompt-list-anchoring` description revised to acknowledge floor-as-ceiling failure caught at reviewer pass. - §13.4 self-reflexive checklist updated: 3 counter-prompts (was 2); §1.5 line acknowledges reviewer-driven gap closure. File: 486 lines (under 500 cap). 14 sections intact. Principle 09 doc-authority test green. Prior-art: skipped — follow-up edit closes reviewer findings on existing research-patch; no new capability per CLAUDE.md hook definition; SSOT proposals (§10) still land in orchestrator session per prior-art-evaluations.md §3 step 1.
8 tasks
artyhoo
added a commit
that referenced
this pull request
May 11, 2026
…#22 Cookiecutter/Copier (Wave 7 review) Two prior Wave 7 commits cite SSOT entries that did not yet exist: 80ef1d9 (sub-wave 7.1.a markdownlint, capability=YES) → #17 f528586 (sub-wave 7.3.a/b template-render harness, capability=YES) → #22 The kickoff (§Sub-wave 7.5.b) planned SSOT entries #17–#22 to land batch-style at Wave closeout, but CLAUDE.md's build-vs-reuse invariant mandates: «add a new SSOT entry … in the same commit as the capability artifact.» CLAUDE.md wins; the kickoff plan was wrong for #17 and #22 (which are positively cited from prior commits). For #18–#21 (lychee, vale, Claude-Code-hooks, cross-editor scripts), the corresponding sub-wave commits used `Prior-art: skipped — …` escape-hatch trailers rather than positive citations, so they are NOT in violation — the kickoff plan for those four remains intact and they land at 7.5.b alongside their verdict transitions. Resolution: forward-add (not amend / not force-push) — the cited trailers in 80ef1d9 and f528586 now point to existing rows. CLAUDE.md «prefer create new commit than amending» is honoured. The deviation was caught by Wave 7 Round 1 cold-start review (2026-05-11); prior round audit Domain 8 reported «PASS» by verifying trailer presence without checking SSOT existence — gap captured in reviewer-checklist amendment (Commit 3 of this batch). Prior-art: skipped — forward-fix M2 from Wave 7 Round 1 review (SSOT entries #17 + #22 added in same atomic commit per CLAUDE.md same-commit rule; supersedes the deferred-to-7.5.b plan in kickoff for these two entries only; entries #18-#21 land at 7.5.b as planned because their corresponding commits did not cite missing IDs); no new capability shipped.
artyhoo
added a commit
that referenced
this pull request
May 11, 2026
… verdict transitions) Append 4 SSOT entries to docs/meta-factory/prior-art-evaluations.md per Wave 7 closeout (§3 «Adding a new entry» step 1): #18 Vale — DEFER (Russian+EN mixed prose FP risk; promote when 2nd doc- prose incident markdownlint cannot catch) #19 lychee — ADOPT (transition from ADOPT WHEN TRIGGERED; shipped 7.1.b) #20 Claude Code hooks — ADOPT (UserPromptSubmit + PostToolUse; shipped 7.2.a/b/c; transition from ADOPT WHEN TRIGGERED) #21 Cursor/Cline/Continue.dev reference scripts — WATCHLIST (Claude Code only project-side per Decision 4; cross-editor parity deferred) NOTE on numbering (entries #16, #17, #22, #23-#26 landed in earlier commits per CLAUDE.md same-commit-as-capability rule): #16 2b0a505 (sub-wave 7.1.d D-3 BUILD verdict) #17, #22 Batch G «feat(prior-art): M2 …» (forward-fix from Round 1 cold-start review M2 finding) #23-#26 Batch F.c Commit 1 «feat(hooks): Wave 7 7.6.c — §1.7 trailer check + SSOT #23-#26» (atomic SSOT landing per CLAUDE.md; precedent 7.1.d #16; cited #23 + #26 positive trailer) The kickoff §«Sub-wave 7.5.b» plan originally targeted all #16-#22 at 7.5.b — corrected via Round 1 review M2 finding adjudication + Round 2/3 user patch confirming atomic #23-#26 landing in F.c Commit 1. Prior-art: skipped — appending parent-research SSOT entries at Wave 7 closeout per §3 «Adding a new entry» step 1; no new capability, no new packages/ subdirectory.
This was referenced May 11, 2026
Merged
5 tasks
5 tasks
artyhoo
added a commit
that referenced
this pull request
May 22, 2026
…l disposition (#162) Completes the DN-4 sweep: - CONTRIBUTING.md «Working in a git worktree» (#29 worktree_node_modules_symlink) - phase-research-coverage.md §1.13 — AI-doc research source priority (#30) - tracker: #29/#30 → CODIFIED; #18/#19 → DEFERRED (reference-facts); #21 → DEFERRED (thesis-level); #24 → OUT-OF-REPO (global orchestrator skill) DN-4 now fully swept: 11/15 codified, 4 dispositioned with reasons, zero bare-PENDING. §1.7 self-review at research-patches/2026-05-22-dn4-round3-tail-codification.md. Prior-art: skipped — prose discipline codification + tracker disposition of existing memory conventions, no new capability or dependency
5 tasks
artyhoo
added a commit
that referenced
this pull request
May 22, 2026
…erifies thesis (#167) Codifies the last "real" DN-4 gap (#21 no_human_verification_ai_self_verifies) as a proposal-of-record (not a rule-fold — it is thesis-level + touches invariant-owned surfaces). Names the convention, identifies the mutual-deferral deadlock as its load-bearing failure mode, connects it to §13.34 and the already-merged operational instances (§1.11, T19, §1.12), and SURFACES the §13.34-widen / CLAUDE-invariant-elevation as a maintainer DECISION-NEEDED (§5). Tracker: #21 DEFERRED → CODIFIED. DN-4 sweep complete (12 codified / 2 deferred ref-facts / 1 out-of-repo; zero bare-PENDING). Prior-art: skipped — thesis-level proposal-of-record codifying an existing memory convention, no new capability or dependency
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
Wave 1 of §13.21 closure plan — adds
Authoritative for:blockquote headers to the 11 consumer-shipped files enumerated in revision §7. Generic phrasing per.claude/rules/doc-authority-hierarchy.md§3.Wave 1 must merge before Wave 2 — Wave 2 extends
principle 09REQUIRED_HEADER_DOCSto include these 11 paths; without Wave 1 shipped first, principle 09 fails-load on the canonical-list extension.Files changed (11)
Templates copied to consumer
.ai-factory/and project root:packages/core/templates/shared/AGENTS.md.templatepackages/core/templates/shared/CLAUDE.md.templatepackages/core/templates/shared/DESCRIPTION.template.mdpackages/core/templates/shared/ARCHITECTURE.ts-server.mdpackages/core/templates/shared/integration-rules.mdPreset-next-15 rules + arch:
packages/preset-next-15-canonical/RULES.mdpackages/preset-next-15-canonical/RULES.react-next.mdpackages/preset-next-15-canonical/templates/ARCHITECTURE.react-next.mdSub-agent prompts copied via
install.sh:138-141:agents/best-practices-sidecar.mdagents/review-sidecar.mdagents/docs-auditor.mdAll carry
NOT authoritative for: project goal — see consumer's README.md— these are consumer-shipped; goal authority lives in the consumer's README, not this framework's.Acceptance criteria (revision §«Wave 1»)
^> \*\*Authoritative for:\*\*(verified pre-commit; 11/11)^> \*\*NOT authoritative for:\*\*(verified; 11/11)Prior-art:trailer per CLAUDE.md «What is a capability commit» (11/11 trailers — non-capability prose-only edits)Order constraint
This PR (Wave 1) must merge before Wave 2 PR opens. Wave 2 will:
REQUIRED_HEADER_DOCSatpackages/core/principles/09-doc-authority-hierarchy.test.ts:45-87EXEMPT_PATTERNSfor fixturesprior-art-evaluations.md§3)If Wave 2 lands first, principle 09 fails-load — that's the intended interlock per revision doc §«Wave 1-4 deliverables breakdown».
Test plan
^> \*\*Authoritative for:\*\*blockquote line (grep -lE '^> \*\*Authoritative for:\*\*' <11 paths>).claude/rules/doc-authority-hierarchy.md§3 «Scope statement style»)NOT authoritative for: project goal — see consumer's README.mdon all 11 — note consumer's README, not this framework'sagents/*.md+integration-rules.md(frontmatter must remain at very top — sub-agents won't load if it shifts)§1.7 Forward-check applied
Wave 1 PR проверен against existing project disciplines per
.claude/rules/phase-research-coverage.md§1.7:vitest run principles/(cold) 7/7 green for principle 09; full workspace suite 305/305 green; принцип 09 mutation tests + sentinel passing.Prior-art:trailer per CLAUDE.md «What is a capability commit») — все 13 коммитов несут escape-hatch trailer (skipped — Wave 1 prose-only header insert/refinement, no new capability under packages/core/<dir>/, no new dependency— 100+ chars rationale, well above 20-char floor). Non-capability classification verified: 0 LOC underpackages/core/<new-dir>/, 0 new dependencies inpackage.json, prose-only doc additions.prior-art-evaluations.md) — Wave 1 не вводит новых ADOPT/DEFER решений; SSOT entries feat(phase-8): acceptance gate Next 15->16 + canonical regen + GO verdict for Phase 9 #11-docs: Phase 9 implementation prompt draft (PHASE-9-PROMPT.md) #15 (ESLint extends, Tailwind presets, Cursor 4-tier, Continue Hub, AGENTS.override.md) deferred to Wave 2 commit per revision plan §«Wave 2 — extend principle 09» («SSOT entries feat(phase-8): acceptance gate Next 15->16 + canonical regen + GO verdict for Phase 9 #11-docs: Phase 9 implementation prompt draft (PHASE-9-PROMPT.md) #15 land in same commit as principle 09 extension»). Wave 1 не нарушает «add new entry in same commit as capability artifact» правило — нет capability artifact'а в Wave 1.doc-authority-hierarchy.md) — recursive self-application: Wave 1 ADDS Authoritative-for headers to 11 files which themselves are NOT canonical project docs (rule §2 «Required for» list), but the headers added comply with rule §3 format spec verbatim — verified by reviewer cycle per scope-statement-style check (specific, names artifact type, mentions canonical NOT-authoritative-for).<!-- begin: rules-table-generated -->marker).§1.7 Backward-check applied
Complete sweep of artefacts under Wave 1's scope — not §1.5 floor of «3-5 examples» but the complete 11-file set per revision §7:
packages/core/templates/shared/, 3 файла подpackages/preset-next-15-canonical/, 3 sub-agent prompts подagents/. Cross-checked againstinstall.sh:138-152shipping pipeline (per revision §1 unified paths): all 11 confirmed shipped (CLAUDE.md.template included for future-proofing per §7 line 83 — 6-month removal trigger if not shipped).git diff --name-only origin/main..HEADreturns exactly the 11 paths (sorted match = revision §7 add-list ordered match): 0 missing, 0 extra. Verified by reviewer cold check.packages/core/principles/09-doc-authority-hierarchy.test.ts:45-88: 0 matches → 0 duplicates. Revision §7 line 84 length sentinel verified: current 33 + 11 = 44, withinexpect(length).toBeLessThanOrEqual(60)at test line 156.EXEMPT_PATTERNSglob arraypackages/*/research/fixtures/**,packages/*/fixtures/**) with positive+mutation meta-test pair per revision §5. Wave 1 does not require exemptions because all 11 files are real shipped artefacts (no fixtures).2026-05-09-§13.21-l3-self-review.mdwhich walked the L3 plan через §1.1-§1.7 forward + §2.1-§2.5 backward, verifying that §1.7 catches the very gap that motivated its creation. Wave 1 is execution of that already-self-reviewed plan — recursive layer satisfied at Wave 0.5 plan-introduction step.c0fb461+c0ae284add(consumer-customisable)to RULES.md and integration-rules.md scope sentences).