docs(readme): add Agentic Coding Disciplines section + Table of Contents#413
Merged
Merged
Conversation
Adds a top-level Agentic Coding Disciplines section after Capabilities that states how this repo develops itself: plan-before-code (Rule 18), mechanical hook enforcement over documentation, verify-by-artifact, adversarial multi-layer review, self-correction via revision chains, and one-concern-per-PR with deploy-after-merge. Each point links to PLAN_TEMPLATE.md, PRINCIPLES.md, and CAPABILITIES.md and is grounded in current repo state. Also adds a Table of Contents (the README had none), listing the h2 sections. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
lantiscooperdev
left a comment
lantiscooperdev
left a comment
Collaborator
There was a problem hiding this comment.
Bot review, pre-merge coherence pass (not an approval)
Docs-only change. Reviewed for accuracy, link integrity, and consistency with current repo state.
Verified
- Section ordering: Table of Contents, Capabilities, Agentic Coding Disciplines, How it works. The TOC anchor
#agentic-coding-disciplinesmatches the new header, and the other TOC anchors map to existing h2 headers. - Claims are accurate as of this commit: the classifier gating only repo-source writes is the ESC behavior merged in PR #409; bp-010, the second-opinion harness, revision chains, and
tools/deploy-audit.mjsall exist. - Links resolve:
docs/PLAN_TEMPLATE.md,PRINCIPLES.md,CAPABILITIES.md, and the in-page#second-opinion-review-harnessanchor. - No regression: existing README content is unchanged; this is purely additive.
Note (non-blocking)
- The TOC lists h2 sections only, which is the right altitude for a README this size. If the team later wants h3 entries (for example under Scripts Reference), that is a separate follow-up.
Verdict
ACCEPT (docs). No blockers. Recommend merge after human approval.
lantiscooperdev
approved these changes
Jun 20, 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
2 participants
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
Adds two things to the project README:
Why
The README documented the product (cross-tool memory, behavioral patterns, enforcement gates) but not the engineering disciplines the project practices on itself. This section makes that explicit and links readers to the canonical docs.
What the section covers
plan-gatehook and the link todocs/PLAN_TEMPLATE.md.plan-gate,checkpoint-gate,stop-gate, the classifier gating only repo-source writes, gates failing closed.tools/deploy-audit.mjs.Every claim is grounded in current repo state.
Scope
Docs-only. README.md, plus 29 lines. No hooks, scripts, or patterns touched.
Generated with Claude Code