Interoperability is a sequence of gated boundaries, not a percentage.
One verified artifact at a time.
The long-term objective is bidirectional ecosystem interoperability and broad target support. The current repository proves narrower compiler, host, loader, ABI, and packaging slices.
entity Semaprax
status pre-alpha research
verified 2026-08-11
authority github.com/wavect/semapraxWhich platforms and ecosystems does Semaprax support?
The v0.2 repository demonstrates bounded native C11/Clang and browser/Wasm output, with platform-specific host and packaging harnesses for desktop, iOS, and Android. These gates do not yet amount to general application support or 100 percent bidirectional interoperability.
Target support evidence
| Platform | Evidence state | Verified artifact | Limitation | Roadmap stage |
|---|---|---|---|---|
| Linux native | Demonstrated | C11/Clang executables plus hosted Ubuntu compiler, host, loader, and sanitizer gates Evidence | Bounded language and ABI slices, not general Linux application compatibility | bounded artifact lanes |
| macOS native | Experimental | Hosted macOS matrix and desktop packaging harnesses Evidence | Host and package evidence does not prove a general macOS application platform | ownership and platform contracts |
| Windows native | Experimental | Hosted Windows matrix, hardened loader checks, and desktop packaging harnesses Evidence | Bounded loader and package contracts, not general Windows application support | ownership and platform contracts |
| Browser and Wasm | Demonstrated | Deployable browser packages and real Node/Wasm verification for documented subsets Evidence | No claim of full Web API, UI framework, or component ecosystem coverage | bounded artifact lanes |
| iOS | Experimental | Swift ownership, static surface, and arm64 simulator host harnesses Evidence | Private bounded contracts, not general App Store or iOS lifecycle support | ownership and platform contracts |
| Android | Experimental | JNI ownership and Android emulator harnesses Evidence | Bounded host contracts, not general Android application support | ownership and platform contracts |
Ecosystem boundary evidence
| Ecosystem boundary | Evidence state | Verified artifact | Limitation | Roadmap stage |
|---|---|---|---|---|
| C11 and Clang | Demonstrated | Deterministic generated C11 compiled and executed at O0 and O2 for admitted slices Evidence | Generated backend boundary, not arbitrary C header or library interoperability | bounded artifact lanes |
| Rust native host | Experimental | Dedicated native host and loader crates with authority, receipt, ownership, and sanitizer gates Evidence | Private host contracts are not a stable public Rust API | ownership and platform contracts |
| WebAssembly and WIT components | Experimental | Core Wasm plus isolated component-runtime and WIT boundary fixtures Evidence | General public component mapping and broad package integration remain closed | ownership and platform contracts |
| Swift and JNI | Experimental | Bounded Apple Swift and Android JNI ownership contracts Evidence | No general bidirectional foreign-function interface or ecosystem package compatibility | ownership and platform contracts |
| Existing language ecosystems | Roadmap | No general artifact Evidence | 100 percent interoperability is an objective, not a current capability | general language and ecosystem |
Long-term objective
A program should cross native, browser, mobile, desktop, and existing-language boundaries without losing ownership, error, or semantic identity facts. That objective remains roadmap work until each public boundary has reproducible conformance evidence.
GitHub specifications are the normative source. This page is a dated research summary. GitHub repository.
Questions, answered without the hype
Does Semaprax support every native target?
No. It has bounded evidence across native, Wasm, desktop, iOS, and Android lanes. General platform support remains experimental or roadmap work.
Is Semaprax 100 percent interoperable with other languages?
No. Full bidirectional ecosystem interoperability is a long-term objective. Current evidence covers narrower generated C11, Rust-host, WIT, Swift, and JNI boundaries.