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
docs(readme): describe the /api routes accurately, including the writes
Nicolas Geysseeaaac13cdde4
diff --git a/README.md b/README.mdindex 70e39348..51b70e2f 100644--- a/README.md+++ b/README.md@@ -203,9 +203,17 @@ open-ontologies serve-http --host 127.0.0.1 --port 8080| Route | Auth | Purpose ||---|---|---|| `/mcp` | bearer, if a token is configured | MCP Streamable HTTP — the `onto_*` tools |-| `/api/*` | bearer, if a token is configured | stats, events and other introspection |+| `/api/stats`, `/api/lineage` | bearer, if a token is configured | read-only introspection |+| `/api/query` | bearer, if a token is configured | SPARQL SELECT |+| `/api/update`, `/api/load`, `/api/load-turtle`, `/api/save` | bearer, if a token is configured | **mutating** — SPARQL UPDATE, and `/load` / `/save` read and write files on the server at a path taken from the request body || `/health` | never | liveness probe |+> **The HTTP surface is not read-only.** When no token is configured the bearer+> layer is not installed at all, so every route above — including the ones that+> write to the server's filesystem — is reachable by anyone who can open the+> port. Set a token, or bind to a loopback address, whenever the port is+> reachable by anything other than the local process.+`/health` returns `{"status":"ok","version":"<crate version>"}` and isdeliberately outside the bearer layer, so an orchestrator can probe the processwithout holding API credentials. It reports nothing about loaded state — use