Repository navigation
One fact, one number: replace the forked deploy run count with a dated receipt - #8730
Merged
Merged
Conversation
…d receipt Two annotations described the same deleted deploy workflow with different numbers -- the workflow annotation said 14 runs, the witness annotation said 30. One fact with two numbers is a §3 fork, and a count restated as a timeless fact decays the moment anything changes. Measured from the run history rather than picking a side: 30 runs between 2026-08-20T03:55:43Z and 2026-08-20T17:14:32Z, 29 failure and 1 cancelled, zero successes ever. So 14 was wrong -- and "exited 127 on all 30" was also wrong, because one run was cancelled and never reached the shell at all. Both annotations now carry the dated window, so the claim is falsifiable against a stated observation instead of asserting a number nobody can re-derive. 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
1 participant
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.
Two annotations described the same deleted deploy workflow with different numbers —
fleet_desired_admission_workflowsaid 14 runs,fleet_desired_admission_witness_testsaid 30. One fact with two numbers is a §3 fork, and it landed in #8643 with both halves intact.Measured rather than picking a side, from the run history of the deleted workflow:
So 14 was wrong — and
exited 127 on all 30was also wrong, because one run was cancelled and never reached the shell at all. Both annotations now carry the dated window instead of a bare count.Why a receipt rather than a corrected number. A count measured once and then restated as a timeless fact decays silently: nothing re-derives it, nothing contradicts it when it drifts, and the next person to measure gets a third number — which is exactly how this fork was produced. A dated window is falsifiable against a stated observation. The subject is a deleted workflow, so the window is closed and the receipt cannot go stale.
Prose-only; no semantic change, no emitted-artifact change. Annotations stay at module-item grain (§4c) — verified no indented
//was introduced.— sent from nimble-fox-671