docs(rules): DN-4 — codify verify-before-claim family into §1.11 - #159
Merged
Conversation
Folds 4 stage-0 memory conventions (DN-4 gaps #16/#17/#22/#28 — the verify-against-source-of-truth family) into phase-research-coverage.md as a new §1.11, + §4 anti-pattern #claim-from-memory-not-source, + tracker rows → CODIFIED. Channel-selection rationale: judgment rules relevant at claim/ship moments (not path-scoped) → reuse the already-always-on rule rather than 4 new files (#always-on-bloat). §1.7 self-review patch shipped at research-patches/2026-05-22-dn4-verify-before-claim-codification.md. Prior-art: skipped — prose discipline codification of existing memory conventions, no new capability or dependency
artyhoo
enabled auto-merge (squash)
May 22, 2026 17:08
This was referenced May 22, 2026
This was referenced May 23, 2026
artyhoo
added a commit
that referenced
this pull request
May 25, 2026
… detection) (#220) Run `bash .claude/skills/meta-orchestrator/helpers/plan-currency-check.sh` (L2 Stage 3 detection shipped in #217) → 88 UNTRACKED-N entries surfaced between the 2026-05-22 reconciliation and origin/staging tip (#217). Map each to an existing §0 / Track row by adding the PR number to its evidence cell, or to a new §0 row for two umbrellas that landed in full since the prior snapshot. Re-run helper → 0 UNTRACKED remaining. Key changes: - Snapshot date 2026-05-22 → 2026-05-25 (header + §0). - N8 row: A-phase 🔲 → 🟡 — C1 SSOT-existence (#170), C2 kickoff T-enumeration floor (#174), C3 principle 13 §1.7 substance (#178), C4 delivery-channel marker (#177), activation #180. C5 + cost-levers remain gated on §5.3 utilisation trigger. - Track M.1 / M.4 → DONE: M.1 codified T20 via #212 (with NB note — recommendation-laziness took the T20 slot, mutation-equivalence T-bump 20→21 still pending); M.4 6 paired-negative bash-hook tests shipped #195/#196/#197/#198/#199/#200. - Two new §0 rows: Meta-orchestrator skill (Track P) — BUILD #186 + audit rounds #192/#193/#194/#201/#202 + UX refactor #203/#204/#205 + planner-completeness #213/#214/#217 + §1.7 PR-body mandate #216; Recommendation-laziness discipline — R-phase #206/#207, benchmark #210, I-phase Sub-waves A/C/D #211/#212/#215. - N7 row: + dogfood research-patch #135 / §4 demotion #166 / live-trial verified #171. N4b row: + design #136 / record #118. - Infra paragraph: PR refs for I.1 follow-ups (#121/#123/#124/#125/ #128/#130/#131/#143/#145/#146/#147/#148/#149/#172/#187), I.2 (#139/#142/#154/#175), I.3 DN-4 (#126/#132/#133/#138/#140/#152/ #159/#161/#162/#167). - Track 2.3 (channel-earliness audit) → DONE 2026-05-23 (#181); removed from "What actually remains". - Footer subsection: standalone work (#191 satellite-arch / #189 guard-liveness / #173 storm-readiness / #176 §10 port / #182 cleanup), Wave 10 follow-ups (#110/#112/#113), plan-revision history (#108/ #109/#153/#155/#157/#160/#164/#165/#168/#179/#185). Verification: - `bash .claude/skills/meta-orchestrator/helpers/plan-currency-check.sh | grep -c '^UNTRACKED'` → 0 (down from 88). - `npx markdownlint-cli docs/meta-factory/wave-sequencing-plan.md` → no violations. - `npx vitest run packages/core/skills/plan-currency-check.test.ts` → 14/14 passed. Prior-art: skipped — chore, doc reconciliation only, no new capability or rule introduced.
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
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.
Что сделано
Closes 4 of the 15 DN-4 stage-0 memory-codification gaps — the verify-against-source-of-truth family (#16/#17/#22/#28) — by folding them into the existing always-on rule:
phase-research-coverage.md(verify against git/GitHub/decided-docs before claim or ship-step) — generalises §1.7's provisional-verdict principle from recommendations to any claim.#claim-from-memory-not-source.CODIFIED → §1.11.research-patches/2026-05-22-dn4-verify-before-claim-codification.md.Channel-selection rationale (DN-4 applied to itself): these are judgment rules relevant at claim/ship moments (not path-scoped) → reuse the already-always-on rule rather than 4 new
.claude/rules/*.mdfiles (#always-on-bloat). Remaining 11 gaps stay PENDING for incremental on-touch codification per the tracker's own design (not batch-codified — avoids#codify-everything+ discipline-theatre).Cold-review (Phase -1, 1× Opus) — REVISE findings all addressed
§1.7 H1anchor (H1 = the distinct §13.39 gate) → removed, cites §1.7's actual provisional-verdict wording.gh pr list --state open(keyword search unreliable for fresh PRs).Как проверить
git diff --stat= 3 files§1.7 Forward-check applied
Complies with active layers — no-paid-LLM (zero LLM calls), doc-authority (edits a headered rule; patch inherits folder authority), channel-selection (
#always-on-bloatfold-not-new-file verdict), memory-codification §3 (this IS the codify step). Evidence:.claude/rules/phase-research-coverage.md:73(§1.11). Not a capability commit (no dep / no ≥80-LOC file) → escape-hatch trailer.§1.7 Backward-check applied
§1.11 extends §1.7-§1.10 without contradiction (
phase-research-coverage.md:75); the 4 conventions were verified stage-0 (not enforced elsewhere) per the memory-coverage audit §4;#claim-from-memory-not-sourceis a unique anti-pattern name; tracker flips exactly #16/#17/#22/#28. Full walk in the self-review patch §3.