Status: stable structure, evolving content — gates are scopes, not date or outcome commitments. No dates are attached to anything on this page.

Roadmap

Xtrape plans in release trains: a minor version (0.7, 0.8) anchors a milestone; each stop on the train is a gate with a defined scope. Two things matter when reading the trains:

• Gate status legend: shipped · in progress · active spine (current implementation focus) · planned (no runnable implementation yet).
• Milestone identity ≠ execution order. Numbers alone do not imply priority. The recorded execution order for the current train is spine first: after the 0.8.0 concept-freeze and rename gate, implementation proceeds directly to the 0.8.5 exposure spine; the Studio line (0.8.1–0.8.4) follows or interleaves afterwards.

What exists today — the 0.7.x train (shipped)

The 0.7.x train (0.7.1 → 0.7.6) built the OSS-ready Community Edition baseline through five gates: platform baseline → operational completeness → durable command kernel (including sensitive one-time results) → connector-initiated long-poll transport and the first public stack record → rename wave and OSS readiness.

Shipped scope: a headless Platform runtime, the Panel CE web operator UI, contracts and connector runtime packages, a demo/reference Widget, an integrated quickstart stack, documentation and this site, and Telegram as an optional adapter. Topology: single-tenant, single-node, SQLite by default, connector-initiated transport.

The train completed component-side (all 0.7.6 tags landed). The public release itself was not executed: the publication strategy was revised, and the phased open-source approach this site is part of replaced it. Public release is explicitly not a train gate.

The 0.8.x train

Gate	Status	Scope
0.8.0	in progress	Concept-freeze execution, repository topology, physical renames. Fixes the canonical object model and vocabulary migration (Store → Artifact Repository, Asset → Artifact/Resource, Runner → Worker).
0.8.1	planned	Studio scenario S1 (repository analysis report), Telegram conversational entry, stack reference deployment.
0.8.2	planned	Workbench sandbox v2 — sandboxed plugin model, service-owned UI artifacts.
0.8.3	planned	Studio write scenarios and hardening.
0.8.4	planned	Studio solidification and agent development experience.
0.8.5	active spine	Controlled Exposure and MCP foundation — the exposure spine: the Xtrape Exposure component and its MCP adapter.

Early Studio scenarios admitted in this train require zero governed approval — read-only analysis, allow-listed comments, sandboxed drafts. Write paths arrive later in the train.

Beyond

0.9.x (planned): private Artifact Repository and generated-service evolution.

Standing engineering rules

• Breaking protocol/runtime/deployment changes move to the next milestone unless the release record explains otherwise.
• Production deploys use immutable tags, never latest; published tags are immutable.
• Every minor bump requires a dependency and runtime review before the milestone closes, targeting stable releases only — pins do not fail loudly, and unreviewed pins drift into unsupported territory silently.
• Compatibility statements apply only to combinations explicitly listed in release records.

See Releases for the versioning model these trains ride on.