Current priority: close the v0.2 release exit
Establish one exact passing head and promotion record. Promote Project v8 only after npm, browser, Rust, native, hostile-input, and compatibility gates pass together.
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 c16348f
authority github.com/wavect/semaprax// STATUS
Repository status at the audited snapshot
| Repository snapshot | c16348f · 2026-08-29. Documentation passed, but the overall workflow failed, so this head is not labelled verified. |
|---|---|
| Full product status | 49 Partial · 0 Implemented · 0 Missing |
| Graph and project contract | Graph ≤ v24 · Project v1 baseline · Project v8, v9, v10 developer preview |
| Promotion baseline | No exact passing promotion commit or workflow run is asserted for this snapshot. |
| Authored developer preview | Owned-data, record, and UTF-8 project profiles, package analysis, borrowing additions, Project Agent Transport, and Revision Store are present in source but unpublished or unpromoted. |
What is next for Semaprax?
The immediate priority is the v0.2 release exit and exact-head promotion, followed by promotion of Project v8 across npm, browser, Rust, native, and hostile-input gates while preserving Project v1-v7 compatibility and making an intentional Rust publication decision. Authored Project v9-v10, transport, revision, borrowing, and package-analysis work remains preview material. The longer sequence is 0.3 ownership and development speed, 0.4 supported components and packages, 0.5 concurrency and applications, and 1.0 maintained end-to-end validation.
// 01
Milestones by evidence state
Authored developer previews
Project v8-v10, Project Agent Transport v5, Revision Store v1, Shared Loan Plan, projected-field borrowing, package reports, offline locks, and compatibility evidence are present but unpromoted.
0.3: ownership and development loop
Advance general ownership while making the implementation and validation loop faster without weakening evidence gates.
0.4: components, packages, and interoperability
Turn bounded previews into supported components and package boundaries with explicit publication and conformance evidence.
0.5: concurrency and applications
Add concurrency and application-level capabilities only after the lower-level contracts are supportable.
1.0: maintained end-to-end validation
Maintain reproducible validation across the complete promised product boundary rather than promoting isolated slices.
// 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 repositoryBidirectional ecosystem interoperability
A long-term objective for typed, ownership-safe boundaries with existing languages and package ecosystems. No percentage claim is made.
GitHub repositoryGitHub 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.