LOCAL FILE CHECK · FREE TOOL
Does this report belong to this layout revision?
Compute a layout’s SHA-256 locally and compare it with the layout identity recorded in DRC/LVS report metadata. A passing filename or a report labelled “clean” is not enough to identify the checked bytes.
Metadata only: this tool does not run DRC/LVS, parse a vendor report or check electrical correctness. Enter metadata taken from the original run evidence and verify its authenticity with your engineering reviewer. The top cell and revisions below are reviewed declarations; use the GDS Inspector to inspect the actual GDS hierarchy first. Selected files never leave this browser.
Download the runnable teaching pack · Read the complete handoff handbook
Results will appear after you run the check.
Try the stale-report failure
- Unzip the pack and select layout-b.gds.
- Leave the teaching top cell, revision B and PDK label shown above.
- Open reports-stale.json and run the check. Expect two DRC mismatches: layout_sha256 and layout_revision.
- Open reports-consistent.json and check again. Expect “Metadata consistent”. This proves agreement among these teaching records only.
- Change the top cell to OTHER. Both reports now disagree. Return to the actual release identity before continuing.
- Download the findings and use the handoff manifest to prepare the package’s inventory.
What to do when a report is stale
Return to the frozen layout and its approved environment. Have the responsible engineer rerun the required checks with the accepted decks, inspect errors and waivers, and bind the resulting evidence to that exact layout. Editing a metadata hash to make this checker pass does not regenerate or validate a report.