ROADMAP · NO RELEASE DATE PROMISES

Advance by closing evidence gaps, not by expanding the claim.

A milestone is complete only when its full gate is exercised.

Semaprax follows an evidence-first roadmap. Design documents record intent; completion requires the exact implementation, negative tests, artifact checks, and supported-host gates named by the repository.

semaprax://roadmapv0.2

entity     Semaprax
status     pre-alpha research
verified   2026-08-11
authority  github.com/wavect/semaprax

What is next for Semaprax?

The roadmap moves from the v0.2 semantic core toward broader ownership, callable and component boundaries, public platform conformance, repository-scale agent workflows, and wider ecosystem interoperability. Dates remain unset until reproducible gates exist.

// 01

Milestones by evidence state

Implemented

v0.2 semantic core

Typed meaning, persistent identity, graphs, bounded context, deterministic diagnostics, and revision-bound patch families.

Demonstrated

Bounded artifact lanes

Exact native, Wasm, host, loader, package, semantic review, and evidence paths under named constraints.

Experimental

Ownership and platform contracts

Broader resource semantics, public ABI boundaries, mobile lifecycle integration, and application-platform conformance.

Roadmap

General language and ecosystem

Repository-scale economics, full target coverage, mature tooling, package distribution, and bidirectional interoperability.

// 02

Roadmap

Broad native platform support

General macOS, Windows, Linux, web, iOS, and Android application support beyond the current bounded host and package gates.

GitHub repository

Roadmap

Bidirectional ecosystem interoperability

A long-term objective for typed, ownership-safe boundaries with existing languages and package ecosystems. No percentage claim is made.

GitHub repository

GitHub specifications are the normative source. This page is a dated research summary. GitHub repository.

// FAQ

Questions, answered without the hype

When will Semaprax v1.0 ship?

There is no announced date. A release should follow reproducible installation, green CI, and completion of the exact gates required for its claimed scope.

How does a roadmap item become implemented?

The implementation, negative cases, artifacts, supported-host checks, and documentation named by its completion gate must all pass. A design document alone is not implementation evidence.

Research project by Wavect: Wavect GmbH. Created by Wavect as an open-source systems research project.