Which artifact do I need?¶
Strixonomy is a product family. You usually need one primary artifact — not all of them.
Decision table¶
| I want to… | Install | Docs |
|---|---|---|
| Browse and edit ontologies in VS Code | Strixonomy extension (Marketplace or Open VSX) | First success (~10 min) |
| Validate, query, or classify ontologies in CI | Linux x64: release tarball from Releases (preferred). macOS / Windows / other: cargo install strixonomy-cli --locked --version 0.27.0 | CI integration · Install · Install CLI & CI (detail) |
| Embed indexing/query in a Rust application | strixonomy = "0.27" in Cargo.toml | Rust library guide |
| Build a custom editor on the language server | Bundle or spawn strixonomy-lsp | LSP API |
| Run OWL reasoning (classification, explanations) | Included via Strixonomy — no separate install | Reasoner guide |
Product names (30 seconds)¶
| Name | What it is |
|---|---|
| Strixonomy IDE | VS Code / Cursor extension |
| Strixonomy engine | Rust engine — strixonomy CLI, strixonomy-lsp, and strixonomy-* crates |
| Ontologos | External reasoner library used by the engine (not installed separately for normal use) |
Full naming and legacy OntoCore/OntoCode map: Product identity.
The extension bundles strixonomy-lsp. You do not need Rust to use the IDE.
Common combinations¶
Solo ontology author: Strixonomy extension only.
Team with Git + CI: Strixonomy extension locally + strixonomy validate (and optional classify / diff) in CI.
Rust service or pipeline: strixonomy crate or strixonomy-cli — no VS Code required.
Air-gapped enterprise: VSIX + optional CLI tarball from GitHub Releases — Enterprise deployment.
What ships today¶
Canonical capability matrix: What ships today.
Next step¶
- IDE path → First success (~10 min core path)
- CLI / Rust path → Rust & CLI guide