What the v0.2 prototype proves, and what it does not.
Evidence has a state, a scope, and an expiry date.
The repository is an executable architectural seed. A passing bounded gate proves only the exact language slice, artifact, host, and failure behavior named by that gate.
entity Semaprax
status pre-alpha research
verified 2026-08-11
authority github.com/wavect/semapraxWhat does Semaprax implement today?
Semaprax v0.2 implements a small typed language, stable graph identity, bounded agent context, revision-bound semantic patch families, fail-closed verification, and deterministic native and browser/Wasm lowering for documented subsets. General language, ownership, platform, and ecosystem coverage remains partial or planned.
Capability evidence ledger
| Current status | Evidence state | Scope | Verified | Evidence |
|---|---|---|---|---|
Stable semantic program graphstable-semantic-program-graph | Implemented | Versioned Graph v10-v14 JSON for the documented typed subset, with persistent identities and validated HIR shared by native and Wasm lowering. | 2026-08-11 | GitHub repository |
Bounded agent contextbounded-agent-context | Implemented | Agent Context v1 plus additive v2 call traversal, with deterministic byte, node, depth, and frontier limits. | 2026-08-11 | GitHub repository |
Revision-bound semantic patchesrevision-bound-semantic-patches | Implemented | Atomic Patch v1 and bounded Patch v2 operations, with exact revision checks, stale rejection, and selective semantic delta validation. | 2026-08-11 | GitHub repository |
Semantic review and evidence capsulessemantic-evidence-capsules | Demonstrated | Bounded review, impact, target, patch, and workspace evidence routes with deterministic artifacts and explicit nonclaims. | 2026-08-11 | GitHub repository |
Native and browser/Wasm loweringnative-and-wasm-lowering | Demonstrated | Documented scalar, control-flow, record, variant, generic, contract, and bounded ownership slices through C11/Clang and real Node/Wasm gates. | 2026-08-11 | GitHub repository |
Ownership-inspired memory managementownership-inspired-memory-management | Experimental | Explicit own, borrow, and shared boundaries plus move checking and bounded resource cleanup protocols. This is not Rust compatibility or a complete borrow checker. | 2026-08-11 | GitHub repository |
Broad native platform supportbroad-platform-support | Roadmap | General macOS, Windows, Linux, web, iOS, and Android application support beyond the current bounded host and package gates. | 2026-08-11 | GitHub repository |
Bidirectional ecosystem interoperabilitybidirectional-ecosystem-interoperability | Roadmap | A long-term objective for typed, ownership-safe boundaries with existing languages and package ecosystems. No percentage claim is made. | 2026-08-11 | GitHub repository |
Claims this page intentionally does not make
- Semaprax is not described as production-ready.
- A platform harness is not treated as complete application-platform support.
- A generated artifact is not treated as successful loading or execution unless its dedicated gate says so.
- Ownership-inspired semantics are not presented as Rust compatibility or a complete borrow checker.
GitHub specifications are the normative source. This page is a dated research summary. GitHub repository.
Questions, answered without the hype
What does Demonstrated mean?
A named artifact or execution path passed its dedicated gate under stated constraints. It does not imply complete language, ecosystem, or platform support.
Does a green CI run prove security?
No. It supports the tested invariants and failure paths. It does not prove the absence of vulnerabilities or general safety outside the tested boundary.