wave-5: §13.25 Project-Aware Tool Bootstrapping research patch - #25
Merged
Conversation
…g as armed trigger Surfaced 2026-05-10 as alternative to push-based MCP delivery via install.sh. Six rules captured verbatim per H8 «meta-commentary lags primary content» mitigation; no design decisions inline. Anchors the dedicated Wave 5 research-session per phase-research-coverage.md §3 «one file per gap». Touches no shipped artefact. Research session that closes this entry will produce research-patches/2026-05-10-§13.25-tool-bootstrapping-research.md.
…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
force-pushed
the
wave-5/research-tool-bootstrapping
branch
from
May 10, 2026 16:20
7cce8a0 to
98ef3ba
Compare
8 tasks
artyhoo
added a commit
that referenced
this pull request
May 11, 2026
…yer pre-push enforcement) Adds §1.7 discipline trailer check as section 9 of .husky/pre-push, closing §13.23 4th-layer enforcement per Wave 7 sub-wave 7.6 research (research patch 2026-05-11-§13.23-4th-layer-research.md) and review verdict GO Path F1 (2026-05-11-§13.23-4th-layer-review-verdicts.md). Atomically lands SSOT entries #23-#26 in prior-art-evaluations.md per CLAUDE.md «add a new SSOT entry … in the same commit as the capability artifact». Precedent: sub-wave 7.1.d landed #16 atomically with D-3 BUILD shipment; Round 1 cold-start review (2026-05-11) §3 adjudication confirmed 7.1.d as exemplary same-commit pattern. - #23 commitlint — ADOPT VOCABULARY (push-time vs commit-time gap; grep-pattern borrowed by s17_check_trailer()) - #24 semantic-release — DEFER (release automation, orthogonal) - #25 commitizen — DEFER (Python dep + FORMAT gap) - #26 git interpret-trailers — ADOPT VOCABULARY (bash case-match parallel; two-parser inconsistency avoided) Synthesis (from §11 Decision 1): - C4 scope predicate: file-glob (.claude/rules/, packages/core/principles/, .claude/skills/) ∧ content-marker (## § heading or top-level export const) ∧ NOT in D3 allow-list (docs(research-patches): / chore(snapshot-regen): / chore(prior-art-update):) - B1 bootstrap exemption: §1.7 Bootstrap: <≥20-char rationale> satisfies §1.7 at introduction-time commits (resolves chicken-and-egg) - T1 trailer format: separate stanza after Prior-art, ≥40-char payload, same placeholder-detection as pa_check_trailer() - D1 warn-only default: S17_WARN_ONLY=true for 30 days post-ship (TODO flip 2026-06-10); operator can flip locally for testing - UTF-8 locale guard: LC_ALL=en_US.UTF-8 wraps every grep matching § (fixup #3 from 7.6.b §4) Adversarial test: 50-commit sweep against main HEAD pre-push. FP count: 0/50 (0%) — below threshold → 30-day calibration default retained. Predicate verified fires on branch commit 4ec69e5 (reviewer skill section add — confirmed true positive: touches .claude/skills/reviewer/SKILL.md + adds new ## § heading content). Predicate is sound. Bootstrap: this commit introduces the §1.7 check; the rule cannot apply to its own introduction without circular dependence. Prior-art: prior-art-evaluations.md#23 (commitlint, ADOPT VOCABULARY — push-time-vs-commit-time framing borrowed; grep-pattern reused in s17_check_trailer()); prior-art-evaluations.md#26 (git interpret-trailers, ADOPT VOCABULARY — RFC 822 trailer convention, bash case-match parallel). Entries #24 (semantic-release DEFER) + #25 (commitizen DEFER) land in this commit per CLAUDE.md same-commit rule but are not positively cited — they document candidates considered + rejected. §1.7 Bootstrap: introducing §1.7 pre-push enforcement section in .husky/pre-push — self-application would be circular at introduction time (the rule cannot apply to its own introducing commit; B1 exemption per 7.6.a research §4 + 7.6.b §2 Problem 2 verdict).
This was referenced May 11, 2026
5 tasks
artyhoo
added a commit
that referenced
this pull request
May 22, 2026
…cation (#161) Codifies 5 stage-0 memory conventions (DN-4 gaps #20/#23/#25/#26/#27): - phase-research-coverage.md §1.12 — lead with reasoned recommendation (#27); act when best path clear, reserve questions for genuine forks (#20) - ai-laziness-traps.md T17/T18/T19 — preserve-before-destructive (#25), preserve-unique-residue (#26), own-cold-QA-before-handoff (#23) - tracker rows → CODIFIED (#27 prose-only; mechanization deferred per #97/#98) Channel-selection: judgment rules → reuse 2 already-always-on rules, not new files (#always-on-bloat). §1.7 self-review at research-patches/2026-05-22-dn4-round2-codification.md. Prior-art: skipped — prose discipline codification of existing memory conventions, 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 5 research-only deliverable for
§13.25Project-Aware Tool Bootstrapping (armed 2026-05-10). Single 557-line research patch covering O0 build-vs-reuse + O0.1 trigger sweep + O1-O8 inventory + §9-§13 synthesis / SSOT proposals / decisions / implementation outline / compliance checks. No implementation; no shipped-artefact edits. Output feeds the separate Wave 5 review session (closes 9 open decisions) and then the orchestrator session (sub-waves 5.1-5.3).Changes
docs/meta-factory/open-questions.md— register §13.25 as armed trigger (commit0ea9bea, preparatory step from PRE-LAUNCH checklist of the research prompt).docs/meta-factory/research-patches/2026-05-10-§13.25-tool-bootstrapping-research.md— single deliverable file (commit7cce8a0).Key findings
/aif(already integrated dep per aif-comparison.md) implements user rules 1-4 end-to-end. Rules 5 (incrementality) + 6 (reject-memory) are gaps in every surveyed framework.self-reflectionskill required explicit operator invocation)./aif), docs: anti-pattern §4 sweep — filename-exempt prompts (PR #16 MINOR closure) #17 ADOPT VOCABULARY (skill-acquisition flow), feat: Phase 9 implementation — A6/A7/A8/A9 (housekeeping + Phase 11.1 closure) #18 DEFER (Continue.dev permissions), process: §1.7 recommendation self-discipline check #19 DEFER (Cline marketplace), Wave 0.5: revise §13.21 L3 closure plan + self-review #20 REJECT (Codex CLI primitive), Wave 1 (§13.21): add Authoritative-for headers to 11 shipped surfaces #21 DEFER (Roo MCP Installer).Prior-art consult
packages/core/<new-dir>/; no new file ≥80 LOC underpackages/). Both commits carry escape-hatchPrior-art:rationale ≥20 chars.prior-art-evaluations.mdin this PR — orchestrator session lands them in the atomic commit with the first capability artefact perprior-art-evaluations.md §3 step 1./aifsurface, last reviewed 2026-05-08 — not changed by this research; entry docs: Phase 8 entry research (Step 0 capability matrix + GO verdict) #8 «AIF Step 0» velocity unchanged).Test plan
vitest run principles/— 45/45 passed (run by pre-push hook on this push).Authoritative-forheader included only because Wave 5 research prompt's deliverable template required it (consistent with §13.21 L3 patch precedent).prior-art-evaluations.mdentries by ID throughout (entries feat: audit fixes Phase 1+2+3 (R2/R11 drift, manifest SSOT, depcruise integration) #1-docs: Phase 9 implementation prompt draft (PHASE-9-PROMPT.md) #15 referenced; docs: goal-hierarchy restructure + doc-authority discipline (L1+L2; L3+Option E baseline) #16-Wave 1 (§13.21): add Authoritative-for headers to 11 shipped surfaces #21 proposed); no broken references introduced.make self-auditgreen by inspection (no diff inpackages/,scripts/, orfactory/).What's next
.claude/orchestrator-prompts/wave-5-tool-bootstrapping/review.mdas first message; closes the 9 decisions in §11.project_wave_6_pending— runs before Wave 5 implementation.