Advance by closing evidence gaps, not by expanding the claim.
A milestone is complete only when its full gate is exercised.
Version 0.8.0 establishes a released beta to build on. The next decisions concern which language, proof, Rust, harness and runtime profiles can broaden their supported scope, with executable acceptance and measured outcomes for each addition.
semaprax://roadmapv0.8.0
entity Semaprax
status beta
snapshot 615e501
authority github.com/wavect/semaprax
// STATUS
Repository status at the audited snapshot
Repository snapshot
615e501 · 2026-10-06. The v0.8.0 tag resolves to the pinned source commit. Its exact-tag CI completed successfully. This does not establish blanket production or security assurance.
Full product status
55 Partial · 0 Implemented · 0 Missing
Graph and project contract
Canonical source, stable IDs and checked compiler representations connect laws, semantic queries, edits and execution. Feature-selected graph and Project schemas preserve their own admission, compatibility and host-authority contracts.
Published beta release
v0.8.0 · Published 6 October 2026 at 07:37 UTC. All 82 exact-tag jobs succeeded. Three toolchain archives, SHA256SUMS, per-archive attestations and signed aggregate provenance were published. The release job independently verified the signed set before publication. The archives are not notarized or claimed reproducible; offline verification does not establish current revocation state. Exact-tag CI.
Package and API previews
The release includes useful language, law, harness and host-integration profiles. Generated Rust/npm packages, public generic ABIs and broader platform support retain separate publication and support decisions.
What is next for Semaprax?
Maintain the released source and archive guarantees, extend law and Rust profiles, qualify harness changes against real task quality and cost, and broaden checked reload and Agent recovery across hosts. Public generic ABIs, package publication and a maintained application platform remain separate milestones. The maximum catalog-normalizer case has passed its bounded interpreter/native/Core-Wasm application gate; it is no longer an unexecuted target. No v1.0 release date is announced.
// 01
Milestones by evidence state
Partial
Maintain the released foundation
Preserve source identity, deterministic checks, archive provenance and negative paths as the code evolves. Extend law coverage and protected-body repair with current proof, source and target evidence; an older successful release does not validate a later change.
Developer preview
Promote explicit package and API profiles
Broaden selected Rust APIs, callback captures and Future composition while recording each foreign assumption and target. Decide publication and supported compatibility for generated Rust/npm packages and public generic boundaries; PG-9 remains unsupported and unpublished.
Partial
Broaden ownership and everyday programming
Build on current records, generics, collections, immutable lists, ownership and bounded closures. Extend lifetime and payload composition deliberately, and measure realistic programs against resource ceilings and backend behavior.
Partial
Extend durable Agent and application profiles
Extend checkpoint restoration, failure settlement and opt-in stage targets. Carry checked hot reload onto more hosts and qualify harness retrieval, skills and routing through accepted-task and cost gates. The recorded paid campaign did not qualify a new default.
Roadmap
Broader targets and a maintained full product
Add host platforms, browser engines, devices and package ecosystems with their own repeatable conformance, lifecycle and maintenance commitments. A full application platform and the final 1.0 validation product remain broader work; no delivery date is implied.
// 02
Roadmap
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.
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.
Reviewed against the v0.8.0 tag and its pinned source commit. Versioned specifications define admission and authority; older release headings in the matrix and roadmap are historical. GitHub repository.
// DOCS
Open the Semaprax handbook
The online handbook is the English guide published from main and may cover changes after 0.8.0. Use the pinned snapshot when reproducing this release.
Reviewed against the v0.8.0 tag and its pinned source commit. Versioned specifications define admission and authority; older release headings in the matrix and roadmap are historical.
No v1.0 date is announced. Version 0.8.0 was published on 6 October 2026. The roadmap describes workstreams and acceptance gates; older numbered headings are not a reliable list of releases still awaiting publication.
How does a roadmap item become implemented?
A bounded implementation must satisfy its owning contract and positive/adverse gates. Broader support additionally needs the named hosts, interfaces and maintenance scope. Package publication and a change to harness defaults are separate decisions, with their own release or quality-and-cost evidence.
Research project by Wavect: Wavect GmbH. Created by Wavect as an open-source systems research project.