Plan, apply and roll back changes to a production ontology, with a blast radius report and a proof an auditor can re-check.
builtin_rules.tsv is a copy, and the direction it can drift in matters
This file is a verbatim copy of tests/fixtures/horn/builtin_rules.tsv in the
repository root. The original is whatever oo-horn rules prints, which is
OOCert.Builtin.asHorn rendered by OOCert.HornParse.ruleStr, and
tests/lean_horn_certificate_test.rs::the_built_in_rules_are_emitted_as_data
pins the fixture to the checker.
It is copied rather than generated because lean/HMain.lean decides which
warrant a run earned by tableLines R == tableLines Builtin.asHorn, a full
ordered equality over the canonical rendering of the whole table. The emitter
therefore writes these bytes verbatim and never re-renders them: a renderer that
changed one byte would cost the absolute verdict, silently, and the run would
still look like a success.
A drifted copy can only weaken a verdict from the absolute one to the
relativised one, never strengthen one, because the comparison happens inside the
checker over the file it was handed. That is the safe direction, and it is also
a silent one, which is why test_horn_checked.py compares these bytes against
oo-horn rules and fails rather than skips on a mismatch, and why the report
carries rules_table_drift when they differ.
Do not edit this file. Copy the fixture again.
Why this directory is called tables and not data
The repository's root .gitignore carries data/ on line 3, with no leading
slash, so it matches a directory of that name at ANY depth. A vendored table
under horn/data/ is therefore invisible to git: uv build would still produce
a working wheel on the machine that wrote the file, because hatchling reads the
filesystem, and a wheel built from a fresh clone or from CI would ship without
the table and raise FileNotFoundError on the first call to builtin_rules().
The root .gitignore already carries four negation entries for exactly this
collision under case-studies/. Renaming is the version that needs no
coordination: it survives anyone regenerating that file, and it cannot be
re-broken by a change in a directory this package does not own. Do not rename it
back.