Interoperability is a sequence of gated boundaries, not a percentage.
Start with one checked boundary in your existing stack.
Choose a released host archive, then choose the language boundary your application needs. Version 0.9.0 adds Linux arm64 and Intel macOS downloads, per-user installers and adapter-based model, tool and specialist selection. Existing Rust, C11 and Wasm profiles keep their own ownership, target and authority limits.
entity Semaprax
status beta
snapshot 933196b
authority github.com/wavect/semapraxWhich platforms and ecosystems does Semaprax support?
Five host archives cover GNU/Linux x86-64/arm64, macOS Apple Silicon/Intel and Windows x64. Native command profiles are distinct from interpreter and Wasm execution. Selected Rust imports, owners, callbacks and same-thread Futures remain scoped. Routing adapters include Jev, Laya, Mini Jev and Clef variants, with no learned adapter live-tested or qualified in the dated support matrix. Public generic APIs and generated package publication remain separate decisions.
Start with one checked boundary in your existing stack.
Target support evidence
.spxChecked programv0.9.0
Target support evidence
| Platform | Source state | Evidence and provenance | Publication state | Supported scope |
|---|---|---|---|---|
| Linux native | Partial | Published x86-64 and arm64 GNU/Linux v0.9.0 archives; both require glibc 2.35+. Evidence | Bounded beta source/toolchain profile | musl/Alpine and older glibc are refused. Native compilation needs Clang; archive installation does not widen language or host authority. |
| macOS native | Partial | Published Apple Silicon (macOS 11+) and Intel (macOS 10.12+) v0.9.0 archives. Evidence | Bounded beta source/toolchain profile | Archives are not notarized. A native install journey is not evidence for a general desktop application platform or every macOS host integration. |
| Windows native | Partial | Published x64 MSVC v0.9.0 ZIP for Windows 10 1809+ / Server 2019+; PowerShell 5.1/7 installer journey gates publication. 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 | One decision core serves development and runtime routing. Rules are the default; adapters can recommend screened model profiles, tools or specialists. Recommendations never grant capabilities or replace authorization. Evidence | Bounded beta source/toolchain profile | Hard screening checks confidentiality, tools, modalities, context and budgets before an advisory router sees candidates. Development phases and runtime deployments share engine code but keep separate evidence keys. Rules make zero router calls; no learned adapter is live-tested or qualified in the dated support record. |
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.
Repository status at the audited snapshot
| Repository snapshot | 933196b · 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 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.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 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. |
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.
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.
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.
- 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
- Tagged changelog and release history
- Installer verification and platform baselines
- Runtime routing, handoff and choice authority
- Native-only resource-output command contract
- Homebrew formula: both v0.9.0 macOS archives
- Post-release channel verification run
- WinGet submission: still open at review
Questions and practical answers
Does Semaprax support every native target?
Five host archives cover GNU/Linux x86-64/arm64, macOS Apple Silicon/Intel and Windows x64. Native command profiles are distinct from interpreter and Wasm execution. Selected Rust imports, owners, callbacks and same-thread Futures remain scoped. Routing adapters include Jev, Laya, Mini Jev and Clef variants, with no learned adapter live-tested or qualified in the dated support matrix. Public generic APIs and generated package publication remain separate decisions.
Is Semaprax 100 percent interoperable with other languages?
Integration is profile-specific. Version 0.9.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.