# Original register-description consistency example

Code: MIT. Data is synthetic and original. CPython 3.12.14 was used; its exact release source commit and executable hash are in ../../measurements/printed-hdl/P08-python.json. No external Python packages are needed.

From this folder run:

```sh
python3 check_registers.py generate registers.json release
python3 check_registers.py check registers.json release
python3 check_registers.py drift registers.json release
python3 check_registers.py check registers.json release
python3 check_registers.py generate registers.json release
python3 check_registers.py check registers.json release
```

Expected return codes:0,0,0,1,0,0. The failing step identifies C STATUS offset12 against expected4. The final generated files agree again. The directory named release is generated locally by these commands; the shipped offsets.sv, offsets.h and verification.json are copies of the final generated outputs.

This checks a deliberately restricted description format. It does not compile C, execute registers, validate IP-XACT or prove an IP release correct. The source script is byte-identical to the page’s printed script and to the file used for the recorded commands.