Release timeline (non-commitment)¶

Planning ranges for Strixonomy IDE / Strixonomy engine. These are product goals, not contractual delivery dates. Shipped behavior is always defined by What ships today for the version you deploy.

Current release¶

Pre-1.0: minor releases may change library APIs, LSP JSON, and SQL virtual table columns — README.

Documented milestone goals (not dates)¶

Canonical forward plan: Platform roadmap. Engineering milestone history: Milestones (shipped).

There is no documented calendar date for v1.0. Enterprise plans should not assume a quarter or year without maintainer confirmation outside these docs.

What each near-term milestone implies¶

v0.10 (shipped)¶

• Semantic diff for PR review workflows (CLI, LSP, VS Code panel)
• Incremental indexing, multi-root workspaces, optional .strixonomy/cache
• Stable strixonomy::Workspace API
• Does not by itself complete Protégé parity or full OBO write-back

v1.0 (planned)¶

• Extended OWL 2 DL axiom catalog and Protégé round-trip playbooks per parity matrix
• Installable plugin host / owlmake-style workflow integration (SDK 1.0 wire frozen in v0.25; curated marketplace + production owlmake planned product 1.0 — Plugin policy)
• Formal performance benchmarks (currently v1.0 backlog — performance sizing)
• Extended Protégé migration playbooks (today: first-week guide, coexistence, decision matrix)

How to plan enterprise adoption without a v1.0 date¶

1. Now (v0.26): CI gates + controlled IDE pilot — production readiness
2. Run production evidence protocol on your corpus
3. Re-evaluate at each pinned minor bump using migration index
4. Do not retire Protégé for DL/OBO workflows until items you need are green in SHIPPED and acceptable under known limitations

Design docs vs shipped docs¶

Related¶

• Governance
• Roadmap (engineering detail)
• Enterprise evaluation
• Changelog