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.

Version 0.9.0 is published; five host archives and installer journeys are current capabilities. The next gates concern broader target/profile acceptance, native-test verification, qualified routing and project-sized law evidence. Keep local source results, hosted release gates and public support decisions separate.

semaprax://roadmapv0.9.0
entity     Semaprax
status     beta
snapshot   933196b
authority  github.com/wavect/semaprax

What is next for Semaprax?

The five host downloads are shipped, not future platform promises. Broader device, browser, public generic and package support still needs explicit acceptance and maintenance decisions. Qualify learned routing separately per domain; retain LAW16 failures and close its remaining AC1/#392 gates. No v1.0 date is announced.

Milestones by evidence state

  1. v0.9.0 Published

  2. Partial

    Maintain the released foundation

    Linux arm64 and Intel macOS join the existing targets. Linux requires glibc 2.35+; macOS and Windows minima are listed per archive. Each target passes its own installed-distribution journey before publication.

  3. 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.

  4. 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.

  5. Partial

    Extend durable Agent and application profiles

    Only an accepted settled turn can open a new route. A handoff carries at most 16 KiB state, accepted-output digests and result references, not the transcript. Delegation reserves the parent allowance and inherits its deadline. Tool/specialist choices are reauthorized against live grants and argument schemas; uncertainty halts for reconciliation.

  6. Roadmap

    Broader targets and a maintained full product

    The five host downloads are shipped, not future platform promises. Broader device, browser, public generic and package support still needs explicit acceptance and maintenance decisions. Qualify learned routing separately per domain; retain LAW16 failures and close its remaining AC1/#392 gates. No v1.0 date is announced.

  7. v1.0 No date announced

Roadmap

Roadmap

Broad native and application support

Five 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 repository
Roadmap

General 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 repository
// STATUS

Repository status at the audited snapshot

Repository snapshot933196b · 2026-10-15. The v0.9.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 status55 Partial · 0 Implemented · 0 Missing
Graph and project contractCanonical 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 releasev0.9.0 · Published 11 October 2026 at 15:07 UTC. All 91 jobs in the exact-tag publication run succeeded. Five toolchain archives and two installers ship with SHA256SUMS, five archive attestations and independently verified signed aggregate provenance. Native installer journeys gate publication. Archives are not notarized or claimed reproducible; offline verification does not establish current revocation state. Exact-tag CI.
Package and API previewsThe 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.

Reviewed on 15 October 2026 against the v0.9.0 commit, published assets and release run. The tagged install handbook and channel registry still show v0.8.0 examples; use this page’s pinned v0.9.0 downloads. Older matrix/roadmap headings are historical. The live handbook follows main and can describe newer work. GitHub repository.

// DOCS

Open the Semaprax handbook

The online handbook is the English guide published from main and may cover changes after 0.9.0. Use the pinned snapshot when reproducing this release.

Live handbook

The current English learning path, published from main.

0.9.0 handbook snapshot

The handbook files at the exact reviewed release commit.

Build your first project

Current English guide to the calculator manifest, checks, tests and builds.

Learn the language essentials

Current English introduction to values, functions and source structure.

Work with a coding agent

Current English guide to semantic context and safe change workflows.

CLI reference for 0.9.0

Pinned command forms and the standalone/full-toolchain boundary.

VS Code extension

Pinned setup, semantic navigation, review and development controls.

Runnable examples

Pinned examples for the language, projects, laws, Agents and host integrations.

// REF

Primary sources for this page

Reviewed on 15 October 2026 against the v0.9.0 commit, published assets and release run. The tagged install handbook and channel registry still show v0.8.0 examples; use this page’s pinned v0.9.0 downloads. Older matrix/roadmap headings are historical. The live handbook follows main and can describe newer work.

  1. Published beta baseline
  2. Remaining product requirements and profile gates
  3. Repository workstreams
  4. Source-law proof and trust requirements
  5. Rust application scope and overhead
  6. Harness default qualification criteria
  7. Hot-reload platform and performance evidence
  8. Public generic support decision
  9. Tagged changelog and release history
  10. Runtime routing, handoff and choice authority
  11. Routing support and unevaluated qualification gate
  12. LAW16 retained trials, adverse outcomes and scope
// FAQ

Questions and practical answers

When will Semaprax v1.0 ship?

The five host downloads are shipped, not future platform promises. Broader device, browser, public generic and package support still needs explicit acceptance and maintenance decisions. Qualify learned routing separately per domain; retain LAW16 failures and close its remaining AC1/#392 gates. No v1.0 date is announced.

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.