Skip to content

Re-vendor the six verbatim fleet-law regions from the hub - #39

Merged
ptr727 merged 1 commit into
developfrom
feature/revendor-verbatim-sections
Aug 3, 2026
Merged

Re-vendor the six verbatim fleet-law regions from the hub#39
ptr727 merged 1 commit into
developfrom
feature/revendor-verbatim-sections

Conversation

@ptr727

@ptr727 ptr727 commented Aug 3, 2026

Copy link
Copy Markdown
Owner

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 against develop@39c896b. All six regions are promoted to hub main a9cd154, so none of this waits on an unpromoted hub change.

What changed

File Section What the hub added
AGENTS.md Context and Delegation Discipline A review round no longer ends a session, since a loop still producing findings is the deliverable in progress. Plus the rule that a wait separates "met", "not yet", and "cannot be reached" instead of rendering all three as silence.
AGENTS.md Where the Rules Live The router row for quoting data into a comment, commit, test, or doc.
GOVERNANCE.md Representative Data in Agent-Authored Text Absent here entirely. Binds agent-authored text to constructed data rather than data observed in the maintainer's environment.
GOVERNANCE.md Git and Commit Rules An authorization to commit carries the push, because nothing reviews a local commit.
GOVERNANCE.md Verification Discipline A launched process is not a result, and a cause nobody observed is not a diagnosis.
GOVERNANCE.md PR Review Etiquette 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.

Known wart, carried deliberately

The new PR Review Etiquette text points at scripts/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

  • Each of the six regions is byte-identical to the hub canonical on origin/main, checked programmatically rather than by eye.
  • No other line in either file changed. The repo-adapted intro paragraphs and the non-verbatim sections are untouched.
  • dotnet husky run clean, editorconfig-checker clean, 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

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>
Copilot AI review requested due to automatic review settings August 3, 2026 17:17
@codecov

codecov Bot commented Aug 3, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 43.37%. Comparing base (39c896b) to head (9f318f5).

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.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 Text section and extend Git and Commit Rules to clarify that “commit” authorization includes pushing to the feature branch.
  • Strengthen Verification Discipline and expand PR Review Etiquette with explicit finding-closure outcomes and guidance for handling suppressed/low-confidence findings.
  • Update AGENTS.md session-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.

@ptr727
ptr727 merged commit 671812b into develop Aug 3, 2026
14 checks passed
@ptr727
ptr727 deleted the feature/revendor-verbatim-sections branch August 18, 2026 17:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants