feat(verified): reuse/rebuild rule and failure fingerprint (Phase A of #6655) - #6671
Merged
Merged
Conversation
…#6655) specs/verified/reuse.t27 is the one written rule of when a sealed artifact may be reused: five identity parts (spec, use-closure, toolchain, config, sealed verdict), MISSING never counts as SAME (fail closed), the reason is the first part that differs. It also packs a normalized failure (stage, class, scope) into one u64 fingerprint (packing, not hashing), the open-new/update/close transitions for failure issues, and the hardware step state (UNPROVEN without device evidence). Composes existing mechanisms instead of restating them: specs/ci/affected.t27 (which specs a change touches), t27c seal, bootstrap_receipt.json and the t27b reference cache key. No hash primitive, no new service. 12 tests pass under zig test on the Railway lab with master t27c (1c0299f); 5 of 5 mutants killed; gen-verilog and gen-c generate; t27c seal --verify: all hashes MATCH. Closes #6670 Refs #6656 Refs #6655 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
This was referenced Oct 6, 2026
Closed
Owner
Author
|
The |
This was referenced Oct 6, 2026
Merged
This was referenced Oct 6, 2026
This was referenced Oct 6, 2026
This was referenced Oct 6, 2026
Merged
Merged
Merged
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.
Closes #6670
Refs #6656, #6655
What
specs/verified/reuse.t27(moduleVerifiedReuse) plus its seal. It is the first slice of the Verified Compute epic, and the rule is written once:use-closure seals, toolchain, config and the sealed verdict. An artifact is reused only when every part is recorded and SAME and the old verdict passed. A MISSING part never counts as SAME. The reason given is the first part that differs, so the same pair of records always gives the same reason.(stage, error_class, scope)is packed into one u64. This is packing, not hashing: it is injective and the parts can be read back. The issue transitions are: a new fingerprint opens a new issue, a fingerprint with an open issue updates it, and an issue closes only on a passing fix run with a verified seal and no recurrence.It composes existing pieces and restates none of them:
specs/ci/affected.t27for selection,t27c seal,bootstrap_receipt.jsonfor toolchain identity, and the t27b cache key (#6535). There is no hash primitive and no new service.Evidence
Run on the Railway lab with t27c built from master
1c0299f59:t27c gen ... && zig testAll 12 tests passed.gen-verilog,gen-ct27c seal --verifyall hashes MATCHNot in this PR
trior CI. That needs a toolchain field in the seal, which is a compiler change and will get its own child issue.🤖 Generated with Claude Code