TARGET MATRIX · SNAPSHOT 036CC69 · 2026-09-02

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 contains narrower compiler, host, loader, ABI, and generated-package slices whose source, execution, publication, and support states must be read separately.

semaprax://interoperabilityv0.2.0
entity     Semaprax
status     pre-alpha research
snapshot   036cc69
authority  github.com/wavect/semaprax
// STATUS

Repository status at the audited snapshot

Repository snapshot036cc69 · 2026-09-02. Documentation passed, but the current CI run was cancelled. The separate v0.2.0 release tag passed all 45 jobs.
Full product status49 Partial · 0 Implemented · 0 Missing
Graph and project contractGraph ≤ v24 · Project v1 baseline · Project v8, v9, v10 developer preview
Promotion baseline5f6fb965 · The v0.2.0 prerelease was published after all 45 jobs in the exact-tag release run passed.
Authored developer previewProject v8-v10, package, borrowing, transport, and revision-store paths received exact-tag hosted regression coverage. Generated packages remain unpublished and the profiles remain unpromoted.

Which platforms and ecosystems does Semaprax support?

Semaprax retains bounded interpreter, C11/Clang, Core Wasm/Node, and scalar JavaScript/TypeScript lanes. Project v8 adds authored npm/Core-Wasm and safe Rust routes for Bytes, Option<Bytes>, and Result<Bytes, i64>; Project v9 and v10 add flat owned records and owned UTF-8. Those package surfaces are unpublished and unpromoted, and do not establish a stable general ABI or broad host-language compatibility.

// 01

Target support evidence

PlatformSource stateExact-head evidencePublication stateSupported scope
Linux nativePartialThe v0.2.0 tag passed selected Linux C11/Clang, host, loader, archive-smoke, and sanitizer gates for admitted slices EvidenceBounded research artifactsBounded language and ABI slices, not general Linux application compatibility
macOS nativePartialThe v0.2.0 tag passed selected macOS, Apple Silicon archive-smoke, native, and desktop regressions EvidencePrivate bounded harnessesHost and package evidence does not prove a general macOS application platform
Windows nativePartialThe v0.2.0 tag passed selected Windows x86-64 archive-smoke, hardened-loader, package, and desktop regressions EvidencePrivate bounded harnessesBounded loader and package contracts, not general Windows application support
Browser and WasmDeveloper previewThe v0.2.0 tag ran selected scalar Core Wasm/Node and Project v8-v10 npm/Core-Wasm package regressions EvidenceScalar baseline bounded; Project v8-v10 unpublished and unpromotedProject v8 admits Bytes, Option<Bytes>, and Result<Bytes, i64>; v9 flat owned records and v10 UTF-8 remain unpromoted. No multi-browser or general Web API support
iOSPartialBounded Swift ownership, static-surface, and arm64 simulator harness evidence; no complete exact-head product gate EvidencePrivate bounded contractsPrivate bounded contracts, not general App Store or iOS lifecycle support
AndroidPartialBounded JNI ownership and Android emulator harness evidence; no complete exact-head product gate EvidencePrivate bounded contractsBounded host contracts, not general Android application support
// 02

Ecosystem boundary evidence

Ecosystem boundarySource stateExact-head evidencePublication stateSupported scope
C11 and ClangPartialThe v0.2.0 tag ran deterministic C11 compilation and selected O0/O2 execution regressions for admitted slices EvidenceGenerated research backendGenerated backend boundary, not arbitrary C header or library interoperability
Rust native hostDeveloper previewEarlier private scalar bridge evidence plus an authored safe Rust package route for Project v8 EvidenceUnpublished developer previewThe Project v8 route is unpublished and unpromoted. It admits only Bytes, Option<Bytes>, and Result<Bytes, i64>, not general Rust interoperability
WebAssembly and WIT componentsPartialCore Wasm/Node lanes and isolated component-runtime and WIT boundary fixtures; complete exact-head promotion remains open EvidenceCore Wasm bounded; general components unpublishedGeneral public component mapping and broad package integration remain closed
Swift and JNIPartialBounded Apple Swift and Android JNI ownership contracts; no full product gate EvidencePrivate bounded contractsNo general bidirectional foreign-function interface or ecosystem package compatibility
Existing language ecosystemsRoadmapPackage reports, offline locks, and Compatibility Evidence v1 provide bounded analysis, not general compatibility EvidenceNo stable general public ABIGeneral bidirectional FFI, stable public aggregate and resource ABIs, package compatibility, and full Component Model publication remain open

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.

// FAQ

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.

Research project by Wavect: Wavect GmbH. Created by Wavect as an open-source systems research project.