From 374fd2afcb88050416ee0bf56da3f867a8794bef Mon Sep 17 00:00:00 2001 From: Pieter Viljoen Date: Sun, 9 Aug 2026 09:23:30 -0700 Subject: [PATCH] Refresh the Divergence Ledger and Clear Three Spent Backlog Claims The ledger is a live pass over each repo's ground-truth branch, so the committed copy is only as current as its last run, which was 2026-08-06. Regenerating it moved three rows: AGENTS.md "Fleet Bootstrap" is now divergent at Blog and HomeAutomation-Config, and GOVERNANCE.md "Verification Discipline" and "Workflow YAML Conventions" widened from one repo to four. The reason TODO.md gave for regenerating did not survive the run. It said the committed copy still rendered repo-config/configure.sh under a re-vendor disposition, and that copy already carried retire, so the warning was true of the decision rather than of the file. The line now says why the file goes stale at all and records what this run actually moved. Two spent claims go with it. The "Verified Complete, Awaiting Close" entry for #578 is deleted, since #578 closed on 2026-08-08 and the part the fleet still owes is carried by the re-vendor entry, which names all three sections it touches. The README rework's State read backlog, which is not one of the four values this file defines, and it is now decision, on where Build Artifacts belongs, which is the only thing in that cluster a hub pull request settles. Co-Authored-By: Claude Opus 5 (1M context) --- TODO.md | 11 +++-------- reports/divergences.md | 5 +++-- 2 files changed, 6 insertions(+), 10 deletions(-) diff --git a/TODO.md b/TODO.md index e15382e0..34d78bd5 100644 --- a/TODO.md +++ b/TODO.md @@ -124,7 +124,7 @@ One pull request measuring the remaining carried surface against the carry-versu The spec rework and its audit check shipped. What remains is the per-repo conformance the check now reports, and one section the fleet carries that the model does not name. -**State** `backlog`. **Touches** each repo's `README.md` on its next visit, plus [`spec/readme-structure.md`][readme-structure] and [`spec/readme-sections.json`][readme-sections] if `Build Artifacts` is adopted. **Cost** one edit per repo, driven by the finding rather than by a sweep. +**State** `decision`, on where `## Build Artifacts` belongs, which is the only thing here a hub pull request settles. The four conformance entries above it are not selectable as hub work at all: each lands on a repo's own next visit, in the sense "Fleet Sweeps" below gives that phrase, and they sit here rather than there because the finding counts are what the shipped check measures. **Touches** each repo's `README.md` on its next visit, plus [`spec/readme-structure.md`][readme-structure] and [`spec/readme-sections.json`][readme-sections] if `Build Artifacts` is adopted. **Cost** one edit per repo, driven by the finding rather than by a sweep. - **Work off the conformance backlog the `readme-structure` dimension now reports.** Measured across all 22 cataloged repos on 2026-08-08, against the shipped checks: 73 findings, 71 on sections and 2 on shields, plus the 3 retired-badge findings the entry below carries. - **Blocked by** - Nothing, and no repo is edited by the hub. Each lands on its own next visit. @@ -390,7 +390,7 @@ Work that lands on a downstream visit rather than as a hub pull request, so it i Blog is the pilot. A sweep is proven there before any fleet-wide rollout, because it is the smallest tree, `hugo` plus `source-only` with no build to break, cataloged and audited on 2026-08-05, and one of only two repos carrying `AGENTS.md` "Fleet Bootstrap" today, so a carried-section change can be observed arriving there. The other carrier is HomeAutomation-Config, which is `operational` and therefore exercises the direct-to-`develop` path rather than the pull request one, which is the second visit worth making rather than the first. -Regenerate [reports/divergences.md][divergences-report] before using it as the work list, since the committed copy predates the retirement decision and renders `repo-config/configure.sh` under a re-vendor disposition that no longer applies to it. A stale ledger is the same hazard as a stale exemption, in that it hands out a work list measured against a tree that no longer exists. +Regenerate [reports/divergences.md][divergences-report] before using it as the work list, since it is a live pass over each repo's ground-truth branch and the committed copy is only as current as its last run. A stale ledger is the same hazard as a stale exemption, in that it hands out a work list measured against a tree that no longer exists. The reason this line used to give, that the committed copy still rendered `repo-config/configure.sh` under a re-vendor disposition, did not survive the check: that copy already carried the `retire` disposition, so the warning was true of the decision rather than of the file. What the 2026-08-09 regeneration actually moved was three rows, adding `AGENTS.md` "Fleet Bootstrap" as divergent at Blog and HomeAutomation-Config, and widening `GOVERNANCE.md` "Verification Discipline" and "Workflow YAML Conventions" from one repo to four. - **Re-vendor the changed `verbatim` content, which is one sweep covering seven files.** Every repo holding a copy of a changed section is byte-mismatched against the hub until it takes the new one, which the audit reports as stale rather than modified. - **Hub state** - Done, verified `develop` at `3d1a0b1` on 2026-08-06 for the sections below, with the prose batch adding five more [`GOVERNANCE.md`][governance] sections, verified `develop` at `d791930` on 2026-08-07. @@ -465,12 +465,7 @@ Actions on issues that are the maintainer's to take, each carrying its evidence Each was checked against the tree and has nothing left to do anywhere. Closing is the maintainer's call, and each wants the evidence quoted in the closing comment rather than a bare close. -- **[#578][issue-578], three rules that state the common case and leave the recurring one unstated.** Complete on all three items. - - **Fixed by** - The pull request carrying this entry, since the fix and the entry ship in one squash and the closing comment cites that SHA. - - **Checked** - `develop` at `a706ddb` on 2026-08-08, where all three gaps were re-read before the widening was written. - - **Closing evidence** - [`GOVERNANCE.md`][governance] "Branching Model" now states that an issue closes when its work is verifiably complete and that the keyword automates the case where completion and promotion coincide rather than adding a condition to it, naming work complete on `develop` with no promotion imminent as the second hand-close case beside a promotion that merged without the keyword, which answers item 1. "Communicating with the User" now says the message carrying the clickable link comes **before** the prompt rather than merely alongside it, since a prompt blocks on an answer and a later message arrives after that answer is given, which answers item 2. "Operational Repositories" now states when to decline the direct-commit grant, as a shape rather than a line count, and records that it stays guidance because a `pull_request` rule on the operational ruleset would gate the direct push and withdraw the allowance, which answers item 3. - - **Detail** - The item 1 rule sits in "Branching Model" rather than the "Git and Commit Rules" the retired cluster named, which is where the re-vendor has to look for it. - - **Detail** - Sweeping item 3 by term rather than by the instance the issue named found [`WORKFLOW.md`][workflow] section 3 restating the same allowance with the same silence, so it now points at the section that owns the test rather than repeating it, which is one rule in one place and a cross-reference for the second reader. +Nothing is awaiting close today. [#578][issue-578] was the last entry here and closed on 2026-08-08, and the part of it the fleet still owes is carried by the re-vendor entry under "Fleet Sweeps", which names the three sections it touches. diff --git a/reports/divergences.md b/reports/divergences.md index 1ec747dc..e203949c 100644 --- a/reports/divergences.md +++ b/reports/divergences.md @@ -35,6 +35,7 @@ Generated by `python3 spec/fidelity_honesty.py --report` - do not hand-edit. Cur A past hub revision, not the current canonical - the audit already flags these as DRIFT. Copy the current file down. No judgment needed. +- **AGENTS.md > Fleet Bootstrap** (2): Blog, HomeAutomation-Config - **AGENTS.md > Context and Delegation Discipline** (1): Financial-Modeling - **AGENTS.md > Where the Rules Live** (4): Blog, Financial-Modeling, HomeAutomation-Config, PhotoCleaner - **GOVERNANCE.md > Foundational Principles** (1): Financial-Modeling @@ -46,10 +47,10 @@ A past hub revision, not the current canonical - the audit already flags these a - **GOVERNANCE.md > Operational Repositories** (4): Blog, Financial-Modeling, HomeAutomation-Config, PhotoCleaner - **GOVERNANCE.md > Pull Request Title and Commit Message Conventions** (1): Financial-Modeling - **GOVERNANCE.md > Documentation Style Conventions** (4): Blog, Financial-Modeling, HomeAutomation-Config, PhotoCleaner -- **GOVERNANCE.md > Verification Discipline** (1): Financial-Modeling +- **GOVERNANCE.md > Verification Discipline** (4): Blog, Financial-Modeling, HomeAutomation-Config, PhotoCleaner - **GOVERNANCE.md > PR Review Etiquette** (4): Blog, Financial-Modeling, HomeAutomation-Config, PhotoCleaner - **GOVERNANCE.md > Communicating with the User** (4): Blog, Financial-Modeling, HomeAutomation-Config, PhotoCleaner -- **GOVERNANCE.md > Workflow YAML Conventions** (1): Financial-Modeling +- **GOVERNANCE.md > Workflow YAML Conventions** (4): Blog, Financial-Modeling, HomeAutomation-Config, PhotoCleaner - **GOVERNANCE.md > Supported Development Platforms** (1): Financial-Modeling - **GOVERNANCE.md > Editor and Tasks** (1): Financial-Modeling - **GOVERNANCE.md > Repository Details** (4): Blog, Financial-Modeling, HomeAutomation-Config, PhotoCleaner