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
Stop publishing a pointer into the private notes, a guess about someone else's work, and a client's name
FABIOTESS4af857708d76
diff --git a/.gitignore b/.gitignoreindex 5356ca29..89b625a0 100644--- a/.gitignore+++ b/.gitignore@@ -33,3 +33,32 @@ python/oo_lite_test.duckdbdemo/derived/demo/corpus_extracted/demo/_review.jsonl++# Confidentiality guards, promoted from one case study's .gitignore to the root.+# The pattern that protected `case-studies/foundry-owl-crosswalk/` worked, and it+# protected exactly one directory out of eighteen. A naming discipline defeated+# by one misnamed file is not a guard.+#+# Outreach drafts name real recipients. Never publish them.+OUTREACH.md+**/OUTREACH.md+**/OUTREACH*.md+**/outreach/+**/CAMPAIGN*.md+**/PROSPECTS*.md+**/PRIVATE*.md+**/BIDNOBID*.md+**/*-internal.md++# Environment files. `studio/.env` was committed once; it held a port number and+# no harm was done, which is the only reason this is a near miss and not a story.+.env+.env.*+!.env.example+**/.env+!**/.env.example++# In-progress research. This was protected only by .git/info/exclude, which is+# local-only: it does not travel with the repo, it is gone on a fresh clone, and+# it is invisible to a collaborator or to an agent working in one.+benchmark/handshake_gate/diff --git a/benchmark/layer3-prototype/onto_compile.py b/benchmark/layer3-prototype/onto_compile.pyindex 122cb979..f135026a 100644--- a/benchmark/layer3-prototype/onto_compile.py+++ b/benchmark/layer3-prototype/onto_compile.py@@ -1,4 +1,4 @@-"""Compile an OWL ontology into flat DuckDB tables — the Kalgera pattern.+"""Compile an OWL ontology into flat DuckDB tables.The ontology stays the SPECIFICATION. Execution is native columnar SQL.diff --git a/benchmark/layer3-prototype/parity.py b/benchmark/layer3-prototype/parity.pyindex b7ca3ea4..ad8007b0 100644--- a/benchmark/layer3-prototype/parity.py+++ b/benchmark/layer3-prototype/parity.py@@ -1,6 +1,6 @@"""Parity test: compiled DuckDB path vs HermiT full ABox consistency.-The Kalgera discipline. The fast path is only usable if it is pinned against+The fast path is only usable if it is pinned againstthe audited baseline, otherwise it is an optimisation with no correctness story.Generates random candidate claims from the ontology's own vocabulary, asks bothdiff --git a/case-studies/jc3iedm-ies4-crosswalk/README.md b/case-studies/jc3iedm-ies4-crosswalk/README.mdindex 70e0c3b0..6bd5551f 100644--- a/case-studies/jc3iedm-ies4-crosswalk/README.md+++ b/case-studies/jc3iedm-ies4-crosswalk/README.md@@ -20,11 +20,14 @@ A production crosswalk would need:## Why this exists-Per the May 2026 IES4 ecosystem research (recorded in [memory](../../../../.claude/projects/-Users-fabio/memory/) under `project_open_ontologies_v0_2.md`):--> No public JC3IEDM ↔ IES4 crosswalk exists as of May 2026. JC3IEDM is ER-shaped and operational-C2; IES4 is 4D-ontological and intelligence-shaped. A crosswalk is almost certainly being built privately inside the IES Working Group (FMN Spiral 3 land-C2 profile is the natural pull) but nothing public.--This case study fills the public gap with a documented sketch. It can be cited as Open Ontologies' contribution to UK/NATO defence-modelling discussions.+No public JC3IEDM to IES4 crosswalk was findable as of May 2026. The two models+are shaped differently: JC3IEDM is entity-relationship and operational C2, while+IES4 is 4D-ontological and intelligence-shaped, so a mapping has to reconcile two+modelling traditions rather than rename fields.++This case study fills that public gap with a documented sketch. It describes only+what is in this repository, and it makes no claim about work anyone else may or+may not be doing.## Methodology