Re-vendor the six verbatim fleet-law regions from the hub - #39
Merged
Conversation
The hub advanced on six byte-locked regions since the last conformance round, and the audit reports each as a stale carry: a region matching a past hub revision rather than the current canonical. AGENTS.md "Context and Delegation Discipline" no longer ends a session on a third review round, since a loop still producing findings is the deliverable in progress, and it gains the rule that a wait separates "met", "not yet", and "cannot be reached" instead of rendering all three as silence. "Where the Rules Live" gains the router row for quoting data into agent-authored text. GOVERNANCE.md gains "Representative Data in Agent-Authored Text", absent here entirely, which binds agent-authored text to constructed data rather than data observed in the maintainer's environment. "Git and Commit Rules" gains the rule that an authorization to commit carries the push, because nothing reviews a local commit. "Verification Discipline" gains the rule that a launched process is not a result. "PR Review Etiquette" gains the five outcomes that close a finding, the rule that a low-confidence finding is not a low-value one, the requirement that a decline carry proof rather than an assertion, the answer format for a suppressed finding, and the warning that a review's own overview cannot be trusted to say whether findings exist. The new "PR Review Etiquette" text points at scripts/pr_review.py, which this repo does not carry. That is a known open question at the hub, and a verbatim region is carried unchanged rather than locally patched. Audit run 2026-08-03T16:52:36Z, hub 1ed0cc8, against develop@39c896b. All six regions are promoted to hub main a9cd154. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@## develop #39 +/- ##
========================================
Coverage 43.37% 43.37% ========================================
Files 28 28 Lines 3896 3896 Branches 306 306 ========================================
Hits 1690 1690 Misses 2154 2154 Partials 52 52 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Pull request overview
This PR re-vendors six byte-locked “fleet-law” regions from the hub into this repository’s governance docs, keeping local policy text byte-identical with the current canonical hub version.
Changes:
- Add the new
Representative Data in Agent-Authored Textsection and extendGit and Commit Rulesto clarify that “commit” authorization includes pushing to the feature branch. - Strengthen
Verification Disciplineand expandPR Review Etiquettewith explicit finding-closure outcomes and guidance for handling suppressed/low-confidence findings. - Update
AGENTS.mdsession-scope guidance and the “Where the Rules Live” router to include the new representative-data section.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
GOVERNANCE.md | Re-vendors updated hub canonical sections: representative data rules, commit/push authorization, verification discipline, and expanded PR review etiquette. |
AGENTS.md | Re-vendors updated hub canonical guidance on session scope, wait semantics, and routes to the new governance section. |
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 freeto 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.
The hub advanced on six byte-locked regions since the last conformance round. The audit reports each as a stale carry - a region matching a past hub revision rather than the current canonical.
Audit run
2026-08-03T16:52:36Z | hub 1ed0cc8, read againstdevelop@39c896b. All six regions are promoted to hubmaina9cd154, so none of this waits on an unpromoted hub change.What changed
AGENTS.mdContext and Delegation DisciplineAGENTS.mdWhere the Rules LiveGOVERNANCE.mdRepresentative Data in Agent-Authored TextGOVERNANCE.mdGit and Commit RulesGOVERNANCE.mdVerification DisciplineGOVERNANCE.mdPR Review EtiquetteKnown wart, carried deliberately
The new
PR Review Etiquettetext points atscripts/pr_review.py, which this repo does not carry. That is an open question already recorded at the hub - whether a carried file may name hub-only machinery. A verbatim region is carried unchanged rather than locally patched, so the reference ships as-is and the fix belongs at the hub.Verification
origin/main, checked programmatically rather than by eye.dotnet husky runclean,editorconfig-checkerclean, and the hub prose gate clean on the changed lines.This is the first of four PRs in the round: verbatim re-vendor, then the carried intent docs, then the line-ending model, then a pipeline fix that blocks a partial publish.
🤖 Generated with Claude Code