Carry the Verification Discipline section to the fleet (#368, PR-4) - #373
Merged
Conversation
Resolves the #368 question. Verification Discipline is clean all-downstream guidance (test-asserts-mechanism, gates-fail-loud, run-all-linters, green-is-not-proof, fix-the-class), so add it to the carried AGENTS.md sections allowlist. Its two cross-references (WORKFLOW.md D8.4, the changes-job under Branching Model) point at other carried content, so no genericizing is needed. The section-presence check (PR-2) now requires it fleet-wide - repos whose AGENTS.md predates it will show a DRIFT until they adopt it, the intended convergence signal. Verified: required for both release and operational selectors, the hub's own AGENTS.md already has it, validate.py clean. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the fleet baseline spec so downstream audits require the ## Verification Discipline section to be present in carried AGENTS.md, resolving the decision in #368.
Changes:
- Add
"Verification Discipline"to theAGENTS.mdcarried-sections allowlist inspec/files.json, making missing sections show as DRIFT in audits.
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.
Resolves the original #368 question. Verification Discipline is clean all-downstream guidance (test-asserts-mechanism, gates-fail-loud, run-all-linters, green-is-not-proof, fix-the-class), so it joins the carried
AGENTS.mdsections allowlist inspec/files.json.Its two cross-references (WORKFLOW.md D8.4, the
changes-job under Branching Model) point at other carried content, so no genericizing is needed.The section-presence check (PR-2) now requires it fleet-wide — a repo whose
AGENTS.mdpredates it shows a DRIFT until it adopts the section, the intended convergence signal.Verified: required for both release and operational selectors, the hub's own
AGENTS.mdalready has it,validate.pyclean. One-line change. Held ondevelop.Closes the scope-model doc-surgery series (PR-1 mechanism, PR-2 section-presence, PR-3 operational extraction, PR-3b hub-pointer removal, PR-3c assessed and skipped, PR-4 this). The fixed-vs-customizable / per-unit-fidelity verification is the next design.