Ecosystem Architecture¶

Audience: Evaluators, adopters, and new contributors — canonical user-facing architecture.

Capability truth: What ships today. Contributor crate layout: Implementation architecture. Short stack: Strixonomy architecture.

Latest tagged: v0.27.0 — v0.27 ships today. Strixonomy IDE (VS Code) + Strixonomy engine (CLI / LSP / library) + Ontologos (reasoning).

Shipped today¶

Strixonomy IDE (VS Code) ──strixonomy-lsp──► Strixonomy engine
                                              ├── Ontologos (EL / RL / RDFS / DL)
                                              └── Oxigraph / Horned-OWL
Applications that ship today: VS Code extension · CLI · GitHub Actions (via CLI)
Plugin SDK 1.0 wire (TOML + subprocess) ships; curated marketplace → product 1.0

Writable formats and limits: Supported formats · Known limitations.

Future (not shipped)¶

Curated plugin marketplace, production owlmake hardening, language SDKs, MCP server, OntoStudio desktop, AI-native surfaces — see Platform roadmap. Do not treat these as product claims.

Engineering-only trees (docs/design/, docs/platform/, docs/ui/) are targets or implementer notes — not the capability matrix.

Responsibilities¶

Ontologos¶

Reasoning algorithms and semantic inference. The Strixonomy engine delegates classification, consistency, and explanations to Ontologos — it does not embed a separate reasoner.

Strixonomy engine¶

Reusable semantic workspace platform: index, query, diagnostics, refactoring, and semantic diff. Consumed by the VS Code IDE, CLI, and Rust library.

Plugin platform status:

• Shipped (SDK 1.0): frozen wire contract — workspace manifest discovery, reference plugins, CLI/LSP hooks, subprocess workflow runner, UI views/commands/preferences/context actions, lifecycle (depends_on / activation), provider actions (see Plugin authoring).
• Product 1.0 targets: curated marketplace/discovery and production owlmake hardening.

The engine is not a workflow engine; build, release, and QC automation should live in external tools and workflow plugins rather than becoming core engine dependencies.

External workflow plugins (e.g. owlmake)¶

SDK 1.0 wire ships today; production owlmake integration is product 1.0. owlmake is the reference workflow plugin design — ROBOT/ODK-style pipelines without becoming a core Strixonomy dependency. Today, ROBOT interop is the strixonomy robot CLI wrapper plus the subprocess workflow scaffold.

Strixonomy IDE¶

Reference IDE on top of the Strixonomy engine. Presents editing, reasoning, and diagnostics in VS Code. Plugin views, commands, preferences, and context actions ship today (SDK 1.0); marketplace-scale workflow automation remains a product 1.0 target.

Design Philosophy¶

Ontologos thinks.

Strixonomy engine understands.

Strixonomy IDE presents.

Workflow plugins automate.

Further reading¶