open-ontologies
Plan, apply and roll back changes to a production ontology, with a blast radius report and a proof an auditor can re-check.
Not yet verifiedsource: GitHubRustMITcommit 2ecb50c2ca7e
Rust, MIT licensed. The project labels itself: ai native, description logics, formal verification, infrastructure as code, isabelle language, knowledge graph, lean and lean4.
open-ontologies has not been verified yet.
Measured by Argusic on a fresh machine every time. Every number links to its evidence.
At a glance
Subject data from GitHub, linked at the top of this page. Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the most recent recorded attempt, which did not reach a verdict. Every line is a recorded value, not an estimate.
- Exact commit tested
- 2ecb50c2ca7e
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Install time
- the run did not report one
- Cold machine to finish
- the attempt was stopped at the time limit after 87 minutes, so it never finished
- Errors hit and fixed
- the attempt was cut off at the time limit before it reported what it had hit
- How the result was proved
- runs before 2026-09-07 did not record the command used to check the result
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Model tokens used
- not recorded for this run
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Whether it works at all
- the attempt did not get far enough to verify anything before the time limit
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
✔ [152/172] Built OOCert.Mixed:c.o (1.3s) LAKE_EXIT=124 oo-dlmodel oo-dlrefute.trace oo-lrat.rsp oo-resolution.hash oo-dlmodel.hash oo-folmodel oo-lrat.trace oo-resolution.rsp oo-dlmodel.rsp oo-folmodel.hash oo-matcert oo-resolution.trace oo-dlmodel.trace oo-folmodel.rsp oo-matcert.hash oo-shacl oo-dlrefute oo-folmodel.trace oo-matcert.rsp oo-shacl.hash oo-dlrefute.hash oo-lrat oo-matcert.trace oo-shacl.rsp oo-dlrefute.rsp oo-lrat.hash oo-resolution oo-shacl.trace Leak lake build was cut at the 300s timeout (exit 124) but made progress. Continuing it. exec /bin/sh -lc '. "$HOME/.elan/env" && cd /work/repo/lean && timeout 400 lake build > /tmp/lake2.log 2…
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Ran out of time | 0.00 | 0.35 |
Topics (from GitHub)
ai-nativedescription-logicsformal-verificationinfrastructure-as-codeisabelle-languageknowledge-graphleanlean4mcpmcp-serverontologyowlowl2reasoningrustshaclsparqltheorem-proving
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/open-ontologies)Questions
- Does open-ontologies run?
- open-ontologies has not been fully verified yet. No recorded run has produced a verdict yet.
- How did Argusic test open-ontologies?
- On a fresh, disposable machine, with every command recorded. One attempt is recorded, and the full method is on the methodology page.
- Where is the evidence for open-ontologies?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.