Roadmap
This page is the public roadmap. It names what is done, what is in progress, what is next, and what depends on an external trigger. The authoritative source for day-to-day status is GitHub milestones on the compiler repository; this page summarises them.
Current release
v0.8.0, released April 2026.
The changelog has full release notes. Major items in v0.8.0: the guarantees document formalised into three tiers, the conformance suite expanded to 700+ tests, the reflection API, field-level confidentiality with taint propagation, and the runtime implementer's guide.
Pre-v1.0 breaking-change policy
Termin is pre-v1.0. The practical consequences for adopters:
- Minor version bumps may introduce breaking changes to the IR (intermediate representation) format. The IR is the compiled JSON artifact that a runtime consumes. Migration guidance accompanies each release. The conformance suite is the migration contract — an application that passes against IR version X and fails against IR version Y identifies exactly what changed.
- The DSL surface may change. Rename, deprecation, and removal of DSL constructs are permitted between minor versions, always with migration notes.
- Long support windows are not committed. Critical fixes are backported to the most recent minor version; deeper support SLAs are a post-v1.0 question.
v1.0 is the signal that the IR format is stable, the conformance suite is locked, and support SLAs can be contracted.
Path to v1.0
The work between v0.8 and v1.0 is organised into five tracks. Each milestone links to its GitHub milestone for day-to-day status.
Provider observability and review framework
- Compute and Channel observability primitives — structured logging, tracing, and health signals declared in source.
- A formal provider review framework: the review standard, the conformance subset required per provider type, the provider manifest schema, and the revocation process.
- At least one Tier 2 provider that has completed the formal review — a proof that the framework is operational, not aspirational.
Triggered by: a volunteer reviewer pool with enough coverage to run the first review. Without that, the Tier 2 framework stays on paper.
Expanded presentation primitives
- Richer data-table behaviours (grouping, virtualisation for large tables).
- Form composition for multi-step entry.
- Additional chart and aggregation primitives.
Scope is bounded: Termin is not adding a general-purpose UI toolkit. The cut-off is "what is expressible in declarative composition without reintroducing imperative UI code."
Third-party security audit
- Scope: the compiler, the reference runtime, and the conformance suite.
- Deliverable: a public report with scope, findings, remediation, and follow-up verification.
Triggered by: funding. The project has no commercial arm, so the audit is gated on grants, pro-bono engagement from security firms with OSS practices, or a community-funded campaign. Announcing the firm, scope, and date shifts this item from "on the roadmap" to "a commitment."
Migration tooling
termin migrate— automated IR upgrades between minor versions where the transformation is deterministic.- Published upgrade notes for each release that includes a breaking change.
- Integration with the conformance suite so an application's post-migration behaviour is testable against the same tests it passed before.
Storage and identity adapters
- A PostgreSQL storage adapter alongside the reference SQLite adapter.
- A pluggable identity subsystem supporting enterprise single-sign-on standards (SSO, SAML, OIDC — the protocols corporate IT uses for login), replacing the stub cookie-based auth used in development.
These are runtime adapter concerns — they expand what deployment shapes are practical without changing the language.
Recently completed
Shipped in v0.7 and v0.8:
- JSON Schema for the IR (draft 2020-12), validated against every example.
- Runtime implementer's guide with the full behavioural contract, including the WebSocket subscription protocol.
- Field-level confidentiality with taint propagation.
- Boundary isolation enforcement.
- State-transition scope gating.
- Two runtimes consuming the same conformance suite.
Deferred
Items considered but deferred until a specific trigger:
- Hosted playground / try-in-browser. Candidate URL:
termin.getclarit.ai, hosted on separate infrastructure so termin.dev itself stays static. Triggered by: a reasonable estimate showing it drives more installs than the equivalent engineering time spent on the compiler or runtime. - Community forum or chat bridge. Triggered by: unsolicited external discussion volume justifying the moderation commitment.
- Localised documentation. Triggered by: a partner or contributor willing to maintain a translation.
- Commercial services. Explicitly not planned. Apache 2.0, no paid tier, no hosted commercial offering, no enterprise edition. A deliberate, publicly-announced change of policy would be required to revisit — see /license and /what-is-termin.
No v1.0 date
A public v1.0 target date is not committed until the remaining work is scoped. The roadmap items above are the scope; the date will be committed when the remaining effort on each is estimable rather than exploratory. The changelog will carry the commitment when it lands.
If that is a blocker for your adoption decision, say so on a GitHub Issue. Adopter feedback is the signal the roadmap is calibrated against.