What shipped, and what comes next.
Solarxy is a node-based parametric modeler and an inspection, validation, and review tool on one Rust core across desktop, CLI, and the web. This page is the map: the architecture, every shipped release, the release program to 1.0, and every roadmap card with the release it ships in or the reason it does not have one yet.
Where the product stands.
The direction is set: grow toward the breadth of a mature web creative engine, in procedural modeling, visual programming, interactivity, animation, and rendering, sequenced realistically. The distance is a heading, not a promise, and this page says per item what is shipped, what is committed, and what is exploratory.
One core, two shells, one wasm instance.
Architecture is a planning dimension in its own right. These are the seams the whole roadmap extends along, and the commitments that hold everywhere.
Load-bearing commitments
From a desktop viewer to a browser engine.
The desktop viewer, validator, and reviewer grew first. Then the web pivot put the same Rust core in the browser and node-based modeling on top of it, and the point releases since have each grown the registry. Expand any entry for what landed.
Releases
What landed, release by release.
The most recent releases in full, sourced from the release notes. Expand any release for what it changed and what it deliberately left out.
Five rungs to the Horizon.
The near-term view: what ships between here and 1.0. 1.0 is a maturity bar, not a feature bar: stable, documented, embeddable, and publishable, explicitly not complete. Capability keeps shipping as 1.x, and the full numbered program is the next section.
Thirteen releases, and every card has a home.
Every roadmap card carries exactly one disposition: shipped, scheduled to a named release, backlog with the trigger that would schedule it, deferred with a rationale, or won't-do with a reason. Shipped, committed, and exploratory work are labeled as what they are, and the labels never blur. Horizon is stated in releases, not dates.
Click any card id to open that card in the explorer further down the page.
Where every card lives
A card cannot drift: if it is not scheduled, something specific has to become true first, and that thing is written down. Click a disposition to filter the explorer.
Backlog triggers
The backlog is grouped into waves, each waiting on something specific.
Five primary personas.
All five are first-class, and each grounds a set of the journeys below. Priya joins with the CLI render in v0.9.0, giving an owner to the pipeline features that already shipped without one.
Sixteen user journeys.
The concrete flows the product is designed around. Expand any row for the step by step; which release advances which journey is the matrix in the next section, so coverage is checkable rather than asserted.
The five-point realtime UX contract
Journeys against releases.
Feature coverage is easy to assert and hard to check. This is the check: a filled dot means the release completes or substantially advances that journey.
Seventy-two cards, one explorer.
Every roadmap card, graded by impact, effort, architectural fit, and priority tier, and carrying the release it ships in or its disposition. Filter, regroup, and search; click a card for the full rationale. Three foundational enablers anchor the set, and all three have shipped.