schema-2 sharded receipts: per-shard fingerprints + policy-gated carry-forward - #8
Merged
Conversation
… ancestry+fingerprint soundness, policy-gated at verify (allow_carried default false)
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.
What
--gpu-proof-shard NAME(+ optional--gpu-proof-shard-fingerprint-paths) emits a receipt whoseshardsblock pins that shard's own narrow fingerprint and test membership by node id. Flattests[]stays authoritative for outcomes; schema-1 receipts are byte-for-byte unchanged.gpu-proof mergeunions schema-2 shards (unique names enforced), and gains--carry-from OLD: a shard absent from the fresh inputs is grafted iff (1) the old commit is an ancestor of the fresh one and (2) its narrow fingerprint recomputes identical at the current tree. Grafted shards are markedcarriedwith full provenance — never silent.tests[], and carried shards are rejected unless the policy setsallow_carried: true(bounded bycarried_max_age_days, default 30) — that is the trust boundary, documented insecurity_model.md. A schema-1 receipt carrying a smuggledshardsblock is rejected.Why
Big suites run GPU tests as many pytest invocations (crash isolation, sharding). With per-shard fingerprints, a merged receipt can honestly say: every test either ran at this commit, or ran at an ancestor on inputs that are provably byte-identical today — and CI can verify that claim instead of taking a local skip-list on faith.
Testing
mkdocs build --strictclean.allow_carried: true.