Maintain the released foundation
Preserve exact-tag release gates, source/revision identity, admitted runtime behavior and negative paths on later commits. A successful old release is not evidence for new code.
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.
entity Semaprax
status pre-alpha research
snapshot b9f593c
authority github.com/wavect/semaprax// STATUS
Repository status at the audited snapshot
| Repository snapshot | b9f593c · 2026-09-16. The reviewed main commit equals the v0.5.0 tag. Its exact-tag CI completed successfully; the separate branch CI was cancelled. Neither is a blanket production or security guarantee. |
|---|---|
| Full product status | 55 Partial · 0 Implemented · 0 Missing |
| Graph and project contract | Feature-selected graph schemas preserve earlier contracts. Project v1 is the baseline; owned-data profiles v8, v9, v10 and v11 have distinct admission and support boundaries. |
| Published pre-release | v0.5.0 · Published 16 September 2026 at 09:43 UTC. Three archives: Linux x86-64, macOS Apple Silicon and Windows x86-64, with SHA256SUMS. The packaged semaprax binary is the full toolchain, not the standalone Cargo CLI. Exact-tag CI. |
| Package and API previews | A published toolchain does not publish its generated Rust/npm packages or promote private APIs. Project v8-v11 support decisions, public generic ownership, broader platforms and native/Wasm Agent-stage execution remain separate. |
What is next for Semaprax?
v0.5.0 is already published, not a future concurrency milestone. Preserve the working semantic, ownership, iterative Agent and host-integration profiles, then extend the missing functionality and explicitly promote selected public boundaries. The repository roadmap retains older numbered workstream headings; they are not future release dates. Its 55-row product contract remains Partial, and no v1.0 date is announced.
// 01
Milestones by evidence state
Promote explicit package and API profiles
Decide publication and support for generated Rust/npm consumers, Project v8-v11 and private transports. Public generic ownership needs its own descriptor/carrier and remaining gates, not just internal generic support.
Broaden ownership and everyday programming
Build on existing collections, generics, function values, bounded closures and I/O. Complete general lifetime safety, broader payload composition, owning captures and the remaining Everyday profile rather than listing existing features as absent.
Extend durable Agent and application profiles
Preserve iterative authorization, checkpoint/migration bindings and cumulative model accounting. Broader providers, distributed coordination, supported app tooling and native/Wasm Agent stages require additional implementation and evidence.
Broader targets and a maintained full product
Add browser engines, physical devices, installed workflows and ecosystem boundaries only with their own conformance and support decisions. Validate the complete promised product continuously; no date or completion percentage is implied.
// 02
Roadmap
Broad native and application support
Three toolchain archives are published, and bounded browser/mobile/desktop profiles exist. A complete supported application platform across browser engines, physical devices, operating systems and installed workflows remains a broader product requirement.
GitHub repositoryGeneral bidirectional ecosystem interoperability
General ownership-safe foreign interfaces, stable aggregate/resource/component and generic ABIs, maintained package publication and broad host-language compatibility remain open. Metadata, generated code and private host fixtures do not complete this requirement.
GitHub repositoryReviewed against the pinned source commit and the v0.5.0 release record. Versioned specifications define admission and authority; older v0.4 release headings in the matrix and roadmap are historical, not the latest release identity. GitHub repository.
// REF
Primary sources for this page
Reviewed against the pinned source commit and the v0.5.0 release record. Versioned specifications define admission and authority; older v0.4 release headings in the matrix and roadmap are historical, not the latest release identity.
// FAQ
Questions, answered without the hype
When will Semaprax v1.0 ship?
No v1.0 release date is announced. v0.5.0 was published on 16 September 2026. Older numbered roadmap headings identify workstreams, not versions that are still awaiting release. Future releases need fresh evidence and explicit support decisions.
How does a roadmap item become implemented?
An implemented slice must satisfy its exact tests and admission contract; completing a full requirement additionally needs all named targets and completion gates. Public support and registry publication are separate decisions. A green workflow or design document alone does not settle all four.
Research project by Wavect: Wavect GmbH. Created by Wavect as an open-source systems research project.