Skip to content

fix(PCB anytime): bind checkpoints to router and environment provenance - #2642

Draft
Tristan-Stoltz-ERC wants to merge 11 commits into
research/pcb-route-benchmark-evaluator-v0-1from
research/pcb-anytime-provenance-v0-1
Draft

Tristan-Stoltz-ERC wants to merge 11 commits into
research/pcb-route-benchmark-evaluator-v0-1from
research/pcb-anytime-provenance-v0-1

Conversation

@Tristan-Stoltz-ERC

@Tristan-Stoltz-ERC Tristan-Stoltz-ERC commented Oct 22, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Stacks on PCB route evaluator PR #2482 and hardens two evidence boundaries.

Anytime archive provenance

  • Bumps the anytime archive/checkpoint schema to v0.2.
  • Requires every incumbent archive to carry full router method/build/config pins and a machine identity (OS, architecture, CPU, cores, memory).
  • Each checkpoint repeats method ID, config digest and environment; archive recording rejects cross-method, cross-config and cross-environment mixing.
  • The archive initializer that previously derived identity from only board/manifest/DRC policy is removed; initialization now requires explicit router and environment pin JSON.
  • Adds regression tests for method, configuration and environment mismatch.

DRC parse-boundary integrity

  • Re-resolves output-board and DRC-report paths under the canonical run root and re-hashes the actual bytes immediately before native DRC JSON parsing.
  • Adds a deterministic test seam that mutates a verified DRC report after the initial artifact-hash pass and before parse. The test requires the parse-boundary re-hash to reject the changed file.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant