Interoperability is a sequence of gated boundaries, not a percentage.
Start with one checked boundary in your existing stack.
Keep your application’s UI and infrastructure in its existing language, and introduce Semaprax for a selected kernel, validator, source law or typed Agent workflow. Version 0.8.0 adds richer Rust imports, generated owner and callback adapters, and real application examples alongside native and WebAssembly execution.
entity Semaprax
status beta
snapshot 615e501
authority github.com/wavect/semapraxRepository 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. |
Which platforms and ecosystems does Semaprax support?
The release ships Linux x86-64 GNU, Apple Silicon macOS and Windows x86-64 MSVC tools. Supported profiles include native C11/Clang, scalar JavaScript/TypeScript Wasm exports and generated owned-data consumers. Selected Rust integrations cover Regex/Url views, Serde records and iterators, bounded FnOnce/FnMut callbacks and same-thread Tokio/reqwest Future examples. Public generic APIs and generated package publication remain separate preview decisions. Opt-in Agent stage targets retain their own narrower contracts.
Target support evidence
| Platform | Source state | Evidence and provenance | Publication state | Supported scope |
|---|---|---|---|---|
| Linux native | Partial | Published v0.8.0 x86-64 GNU/Linux full-toolchain archive with SHA-256 checksum. Evidence | Bounded beta source/toolchain profile | Native compilation requires Clang; individual language, loader and host profiles remain bounded. |
| macOS native | Partial | Published v0.8.0 Apple Silicon full-toolchain archive with SHA-256 checksum. Evidence | Bounded beta source/toolchain profile | This release has no Intel macOS archive. Source builds and private desktop profiles are separate from a general macOS application platform. |
| Windows native | Partial | Published v0.8.0 x86-64 MSVC toolchain ZIP; the exact-tag Windows build, Project and private desktop jobs passed. Evidence | Bounded beta source/toolchain profile | Native builds require the appropriate C11 toolchain. ARM Windows archives, general desktop packaging and every host-specific isolation profile are outside this release inventory. |
| Browser and Core WebAssembly | Developer preview | Public scalar Wasm exports passed the exact-tag Chromium job. Private generated owned-data and compiler-owned generic Wasm provider profiles also execute. Evidence | Generated/private preview; publication and public support are separate decisions | Generated npm and public generic support remain separate publication decisions. Every language profile has its own export, runtime and browser limits; opt-in Agent stage hosts do not establish a general browser Agent platform. |
| iOS / Swift | Partial | Private Swift/iOS loader and application-runtime jobs passed in exact-tag CI. Evidence | Generated/private preview; publication and public support are separate decisions | These jobs do not establish every physical device, App Store deployment or a supported public mobile toolchain. |
| Android / JNI | Partial | Private Android JNI/Kotlin runtime jobs for arm64-v8a and x86_64 passed in exact-tag CI. Evidence | Generated/private preview; publication and public support are separate decisions | These jobs do not establish universal devices, packaging or a maintained public Android framework. |
Ecosystem boundary evidence
| Ecosystem boundary | Source state | Evidence and provenance | Publication state | Supported scope |
|---|---|---|---|---|
| C11 and Clang | Partial | Generated native backend for admitted checked programs. Evidence | Bounded beta source/toolchain profile | Requires a C11-capable Clang driver; not arbitrary C header/library interoperability. |
| Rust host and generated consumers | Developer preview | Selected indexed imports and generated owners, borrowed views and callback adapters execute real Regex/Url, Serde/iterator and reqwest/Tokio applications. Same-thread Future and Project-selected source-yield routes use caller-owned executors. Evidence | Generated/private preview; publication and public support are separate decisions | Exact signatures, Cargo inputs, targets and lifetimes are selected. Generated packages remain previews; arbitrary crates, general async/cross-thread behavior and zero-overhead interoperability are not established. |
| JavaScript / TypeScript / npm | Developer preview | The exact-tag Chromium scalar-export job passed. A private compiler-owned generic Core Wasm provider and canonical TypeScript carrier execute one checked endpoint. Evidence | Generated/private preview; publication and public support are separate decisions | The generic package is unpublished and unsupported. Broader hostile/hosted endpoint acceptance, browser coverage and copy-out/fuel parity remain open. |
| WIT and Component Model | Partial | The exact-tag private Wasmtime Component runtime job passed; Component v7 keeps its frozen WIT identity at 0.5.0. Evidence | Bounded beta source/toolchain profile | A private Component fixture is not public Component Model support, stable resource ABI or arbitrary composition. |
| Swift and JNI | Partial | Private ownership, loader and host-application integration profiles. Evidence | Bounded beta source/toolchain profile | No general bidirectional host-language/package compatibility or universal physical-device claim. |
| Public generic ABI | Roadmap | The exact-tag generic milestone jobs passed on Linux, macOS and Windows. Private compiler-owned Wasm/native boundaries and consumer settlement have bounded evidence. Evidence | Bounded beta source/toolchain profile | PG-9 remains unsupported and unpublished. A full public generic signature, broader checked endpoint shapes and release-candidate support decision remain open. |
| Model providers and host services | Experimental | The development harness supports explicit provider descriptors, project locks/trust, endpoint adoption and model-routing policies. Runtime Agent providers retain separate typed authorization, budgets and durable model/effect journals. Evidence | Bounded beta source/toolchain profile | Explicit credentials, runtime, storage and transport setup. Receipts distinguish observed usage and reported cost from reservations/estimates; unknown billing remains unknown. Learned routing and automatic defaults require qualification. |
Long-term objective
Preserve ownership, errors, stable identities and checked requirements as code crosses a language boundary. The current integration route selects an exact signature, target, dependency set and host capability; broader APIs and platforms need their own conformance and support evidence.
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.
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.
Live handbook
The current English learning path, published from main.
0.8.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.8.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.
Primary sources for this page
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.
- Published platform archives
- Native Rust imports and receiver-tied views
- Rich Rust owners, records and callback adapters
- Same-thread Rust Future lifecycle
- Project-selected source Future bridge
- Real combined Rust applications and measurements
- Public scalar Wasm exports
- Public generic support decision
- Target, package and execution limits
Questions and practical answers
Does Semaprax support every native target?
The release provides Linux x86-64 GNU, Apple Silicon macOS and Windows x86-64 MSVC archives. Native/Wasm language profiles and opt-in Agent stage hosts have separate admission and evidence. There is no Intel macOS, Linux arm64 or Windows arm64 binary in the 0.8.0 release asset set.
Is Semaprax 100 percent interoperable with other languages?
Integration is profile-specific. Version 0.8.0 includes scalar and owned-data exports, selected Rust imports, generated owners and callbacks, and bounded same-thread Futures. Stable general aggregate/resource/component/generic ABIs, arbitrary crate use and maintained package publication still require their own completion decisions.