Record the hub's verification ruling and what it will ask of this repo - #45
Merged
Conversation
A finding that lives only in a chat message is not recorded. #597 was filed from here and its ruling landed, and neither appeared in this repo's own backlog, so the next session would have re-derived the whole thing from the miss that started it. #597 is added to the open-against-the-hub table. It was filed after a mandatory pre-merge gate in OPERATIONS.md was skipped on #40, and the ruling is that a verification a runner cannot perform needs a declared destination rather than a better per-repository pointer, because the pointer is what failed. What #598 will ask of this repo is recorded with it, and so is the reason not to act yet: it is merged to the hub's develop and not to main, so it binds nothing, which is the trap this file already records about reading main as ground truth. The work itself is smaller than it sounds and is written down so it is not re-measured. This repo's OPERATIONS.md carries 13 level-two headings and matches none of the five declared today, so the change is a rename and reorder rather than new prose. Both gaps are near-misses rather than absences: the gate's own section is `Local Verification Before a Pull Request` against the incoming `Local Verification`, and `Backup and Restore` is one word from the declared `Backup and Recovery`. That shape is worth stating, since a repository that wrote its operational document before the spec declared headings will have covered the same ground under its own names. The absence of any signal is recorded too. OPERATIONS.md is presence-checked only, which is why the full audit on 2026-08-05 reported nothing about a file using none of the declared headings, and the heading check belongs to a hub cluster that has not shipped. Until it does, nothing here will fail. Reference definitions added for #597, #598, and this repo's #40. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Updates TODO.md to record the hub’s ruling on ProjectTemplate#597 and to document what work ProjectTemplate#598 (once promoted to hub main) will require from this repository, so the backlog doesn’t rely on external chat or hub-only context.
Changes:
- Adds ProjectTemplate#597 to the “open against the hub” findings table, including rationale and linkage to prior PR #40 and hub PR #598.
- Documents (in
TODO.md) the expected futureOPERATIONS.mdheading rename/reorder work once hub PR #598 becomes ground truth. - Adds new reference links for
pr-40,issue-597, andpr-598.
Adding #597 to the table left the sentence above it saying "Two findings are open at the hub. Neither is work this repo can do." Both halves became false in the same edit: there are three, and the new one is the only entry in the table that this repo will act on. The second half was the more misleading of the two. A reader scanning for what this repo owes would have been told by the lead sentence that nothing in the table qualifies, and stopped there, which is the opposite of why the row was added. The sentence now separates the two kinds rather than generalizing over them, and points at the paragraph stating what the actionable one will ask. Verified by counting: three table rows, and a lead sentence that says three. #597 confirmed still OPEN at the hub rather than assumed, since the change answering it has already merged there and a closed issue would have made "open at the hub" wrong too. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Documentation only.
TODO.mdgains the hub work this repo is party to but had not written down.Why
#597 was filed from here and its ruling has landed, and neither appeared in this repo's own backlog. A finding that exists only in a chat message or in another repository's issue is not recorded here — the next session would have re-derived the whole thing starting from the same miss.
What is recorded
#597 joins the open-against-the-hub table. It was filed after a mandatory pre-merge gate in
OPERATIONS.mdwas skipped on #40. The ruling is that a verification a runner structurally cannot perform needs a declared destination, not a better per-repository pointer — because the pointer is precisely what failed, and requiring it to be better leaves the guarantee resting on each repository's wording.What ProjectTemplate#598 will ask of this repo, together with the reason not to act on it yet: it is merged to the hub's
developand not tomain, so it binds nothing. That is the trap this file already records about readingmainas ground truth.The work, measured now so it is not re-measured later.
OPERATIONS.mdhere carries 13 level-two headings and matches none of the five declared today, so this is a rename and reorder rather than new prose. Both gaps are near-misses, not absences:Local Verification Before a Pull RequestLocal Verification(incoming, sixth)Backup and RestoreBackup and RecoveryThat shape is worth stating rather than leaving to be rediscovered: a repository that wrote its operational document before the spec declared headings will have covered the same ground under its own names, so the useful output of a heading check is a mapping, not a list of five missing things.
The absence of any signal is recorded too.
OPERATIONS.mdis presence-checked only, which is why the full audit on 2026-08-05 reported nothing about a file using none of the declared headings. The heading check belongs to a hub cluster that has not shipped, so until it does, nothing here will fail and nothing will remind anyone.Verification
TODO.mdresolve, with no unused definitions — checked programmatically, since three new labels were added (issue-597,pr-598, and this repo'spr-40).Not done here
The heading rename itself. The hub's ruling says nothing is asked of this repo until #598 reaches
mainand the re-vendor visit arrives, and acting againstdevelopwould be building on a ref that is explicitly not ground truth.🤖 Generated with Claude Code