Plan, apply and roll back changes to a production ontology, with a blast radius report and a proof an auditor can re-check.
Rust ai-nativedescription-logicsformal-verificationinfrastructure-as-codeisabelle-languageknowledge-graphleanlean4mcpmcp-serverontologyowlowl2reasoningrustshaclsparqltheorem-proving
python: recite the Rust by the lines it is now at
FABIOTESS261c23bec70b
diff --git a/python/src/open_ontologies_lite/horn/reason.py b/python/src/open_ontologies_lite/horn/reason.pyindex cbc58ad1..74ef1b49 100644--- a/python/src/open_ontologies_lite/horn/reason.py+++ b/python/src/open_ontologies_lite/horn/reason.py@@ -246,7 +246,7 @@ def _facts(store, graphs) -> tuple[list[Fact], list[str]]:The default is the DEFAULT GRAPH ALONE, which is where `OntologyEngine.load()`puts everything, so this package's own users lose nothing by it. The Rustengine flattens every named graph here EXCEPT the inferred one- (`src/reason.rs:1105`, `graph.triples_outside(&[INFERRED_GRAPH])`). Before+ (`src/reason.rs:2745`, `graph.triples_outside(&[INFERRED_GRAPH])`). Before15 September 2026 it excepted nothing, which was the defect above: a storeholding a prior materialisation turned derived triples into assertions."""diff --git a/python/tests/test_horn_differential.py b/python/tests/test_horn_differential.pyindex 3a2828e0..da3f7533 100644--- a/python/tests/test_horn_differential.py+++ b/python/tests/test_horn_differential.py@@ -26,7 +26,7 @@ WHAT IS COMPARED, AND WHAT IS NOT.The assertion is SET EQUALITY OF DERIVED TRIPLES against the Rust `run_horn`, overthe same `builtin_rules.tsv`. Byte identity of the two `horn.tsv` files is NOT agoal and must not be asserted: the Rust emitter sorts interned `u32` triples-(`src/reason.rs:2757`, `all.sort_unstable()` over `Vec<(u32,u32,u32)>`), so its+(`src/reason.rs:2815`, `all.sort_unstable()` over `Vec<(u32,u32,u32)>`), so itsline order is first-appearance order in the store, not lexicographic order.Reproducing it from Python would mean reimplementing the interner and betting onidentical store-iteration order across two bindings, to buy nothing the setdiff --git a/python/tests/test_horn_fixpoint_and_scope.py b/python/tests/test_horn_fixpoint_and_scope.pyindex 5f9ad720..db871fcc 100644--- a/python/tests/test_horn_fixpoint_and_scope.py+++ b/python/tests/test_horn_fixpoint_and_scope.py@@ -24,7 +24,7 @@ previous materialisation in the inferred graph turned derived triples intoASSERTIONS. The checker could not detect it: the soundness theorem is conditionalon the assertions, and it is TOLD what they are, so the result was a greenabsolute verdict about a graph nobody asserted. It now reads-`src/reason.rs:1105`, `graph.triples_outside(&[INFERRED_GRAPH])`, and the+`src/reason.rs:2745`, `graph.triples_outside(&[INFERRED_GRAPH])`, and theinferred graph is out of scope.The two engines still differ in HOW, and the difference is deliberate. Rust