Repository navigation
fix(PCB anytime): bind checkpoints to router and environment provenance - #2642
Draft
Tristan-Stoltz-ERC wants to merge 11 commits into
Draft
Tristan-Stoltz-ERC wants to merge 11 commits into
Tristan-Stoltz-ERC wants to merge 11 commits into
Conversation
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.
Summary
Stacks on PCB route evaluator PR #2482 and hardens two evidence boundaries.
Anytime archive provenance
DRC parse-boundary integrity
These are provenance consistency checks, not cryptographic execution attestation; method pins do not by themselves prove which process generated the output. Runs still need invocation/exit-status/log evidence.
Evidence status
Latest exact head:
3201cede1cd4840d1734154609d2b421033a59b5. Focused workflow #39749872486 is queued after adding the deterministic parse-boundary mutation regression. No passing result is claimed for this head yet. The tests use synthetic files and do not establish real-router performance, signal/power integrity, manufacturability, physical conformity, safety or release readiness.