docs: README absolutism resolution — A3 Practice note + D1 Class A/B/C tags - #69
Merged
Merged
Conversation
Adds `> **Class:**` line as first blockquote header line to each of 8 .claude/rules/*.md files, declaring executable-artifact status: - A (5): ai-laziness-traps, build-first-reuse-default, doc-authority-hierarchy, no-paid-llm-in-ci, phase-research-coverage - C (3): dual-implementation-discipline, parallel-subwave-isolation, reviewer-discipline Extends doc-authority-hierarchy.md §3 to document the convention (field placement, allowed values, link to motivating research-patch). Resolves Decision D1 from research-patch 2026-05-16-readme-absolutism-vs-class-c-practice.md §7 — D1b blockquote form chosen over D1a YAML frontmatter to match existing header convention (verified: principle 09 test 17/17 pass, skill-drift script PASS). Prior-art: skipped — doc-only edit, Class metadata annotation on existing rule files, no new capability artifact, no new dependency.
Closes the honest-disclosure gap between README invariant absolutism («every rule = executable artifact») and current practice — 3 rules are currently Class C (prose-only, mechanism deferred): dual-implementation-discipline, parallel-subwave-isolation, reviewer-discipline. Practice note added to §Goal block after the «CI is the last-resort gate» line; points to motivating research-patch and to the doc-authority-hierarchy §3 Class field convention (added in prior commit 3827f95). Resolves Decision A3 from research-patch 2026-05-16-readme-absolutism-vs-class-c-practice.md §7. Decision A2 (time-box Class C with max-defer + quarterly audit) is separate medium-term work, not in this PR scope. Prior-art: skipped — doc-only edit, README §Goal Practice note, no new capability artifact, no new dependency.
This was referenced May 23, 2026
artyhoo
added a commit
that referenced
this pull request
May 25, 2026
…mplate (#216) Adds §4b to templates/meta-kickoff.template.md — a path-triggered, always-present mandate that any Worker whose target file matches a discipline-bearing path (.claude/rules/, packages/core/principles/, EXECUTION-PLAN, prior-art-evaluations, CLAUDE.md, packages/core/templates/, .claude/skills/, agents/) MUST include §1.7 Forward/Backward-check sections in the PR body with the exact H3 + "applied" shape + ≥40 chars + ≥1 file:line citation per section. Origin: 6th recurrence of the §1.7-missing-from-PR-body CI gate fail in ~2 weeks (#58/#69/#105/#111/#212/#215). Memory feedback_pr_s17_authoring_checklist says "memory ≠ enough, execute the grep" — but in-line memory does not reliably activate inside paste-block Worker prompts. The mandate must be in the prompt itself. The §4b block: - Names all 8 path patterns that trigger the mandate - Documents 5 hard rules (H3 not H2; "applied" required; ≥40 chars; ≥1 file:line; "Skipped" escape-hatch needs ≥60-char rationale) - Provides a copy-paste pre-flight grep block Workers can run BEFORE gh pr create - Lists the 6 historical incident PR numbers as evidence Self-evaluating: Workers whose target file does NOT match the path list ignore §4b. The mandate is path-scoped, not all-Workers. No template placeholder added (no SKILL.md change needed) — block is static prose, always present in every generated meta-kickoff. Workers read it and self-apply. Prior-art: skipped — template prose addition; not a capability commit per CLAUDE.md «What is a capability commit?» (no new dep, no new file ≥50 LOC in new packages/core subdir, no new ≥80 LOC file under packages/). Evidence base: memory feedback_pr_s17_authoring_checklist + recurrence incidents PR #58/#69/#105/#111/#212/#215.
8 tasks
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
Resolves Decisions A3 + D1 from research-patch
2026-05-16-readme-absolutism-vs-class-c-practice.md §7.fe2cee3): README §Goal Practice note closes honest-disclosure gap between «every rule = executable artifact» absolutism and 3 Class C rules in current practice.3827f95): 8.claude/rules/*.mdfiles self-describe class via> **Class:** A/B/Cblockquote line. D1b form chosen over D1a YAML frontmatter to match existing header convention.doc-authority-hierarchy.md §3extended to document the field.Class assignments
Not in scope
§1.7 Forward-check applied
Recommendation (Class field convention as enforced by 8 rule files + §3 doc-update) complies with existing disciplines — concrete evidence:
checkDocsHaveAuthorityHeaderparses> **Authoritative for:**blockquote): 17/17 pass post-edit. Class line is inserted as first blockquote line, Authoritative-for follows unchanged.packages/. Each commit carriesPrior-art: skipped — doc-only edit, ...trailer with ≥20-char rationale per CLAUDE.md escape-hatch syntax.§1.7 Backward-check applied
Complete sweep of all
.claude/rules/*.mdfiles under new Class field scope — 8/8 tagged, no exemption mechanism (all rules in scope of self-describe convention):> **Class:** A> **Class:** A> **Class:** A> **Class:** C> **Class:** A> **Class:** C> **Class:** A(line 12 because file has pre-existing YAML frontmatter at top)> **Class:** CSelf-reflexive: §1.7 applied to this PR itself — both Forward and Backward sections present, file:line citations in each (per project convention).
Test plan