EVIDENCE · B9F593C · 2026-09-16
What v0.5.0 implements, and what it does not prove.
Evidence has a state, a scope, and an expiry date.
The published v0.5.0 tag and reviewed main both resolve to b9f593c. Exact-tag release CI succeeded, and three toolchain archives were published. The full product contract still records 55 Partial, 0 Implemented and 0 Missing requirements. That is a coverage classification, not a completion percentage.
entity Semaprax
status pre-alpha research
snapshot b9f593c
authority github.com/wavect/semaprax// STATUS
Repository status at the audited snapshot
| Repository snapshot | b9f593c · 2026-09-16. The reviewed main commit equals the v0.5.0 tag. Its exact-tag CI completed successfully; the separate branch CI was cancelled. Neither is a blanket production or security guarantee. |
|---|---|
| Full product status | 55 Partial · 0 Implemented · 0 Missing |
| Graph and project contract | Feature-selected graph schemas preserve earlier contracts. Project v1 is the baseline; owned-data profiles v8, v9, v10 and v11 have distinct admission and support boundaries. |
| Published pre-release | v0.5.0 · Published 16 September 2026 at 09:43 UTC. Three archives: Linux x86-64, macOS Apple Silicon and Windows x86-64, with SHA256SUMS. The packaged semaprax binary is the full toolchain, not the standalone Cargo CLI. Exact-tag CI. |
| Package and API previews | A published toolchain does not publish its generated Rust/npm packages or promote private APIs. Project v8-v11 support decisions, public generic ownership, broader platforms and native/Wasm Agent-stage execution remain separate. |
What does Semaprax implement today?
There are executable language, semantic-change, iterative Agent, generated-consumer and host-integration profiles, including the v0.5.0 model-streaming, accounting, retry and job additions. Their existence does not complete the broader requirements. The matrix corrects the former 50-row dashboard to 55 actual requirements without changing thresholds; the website had an even older 49-row snapshot. Some repository status prose still names v0.4.0, so current release identity comes from the v0.5.0 release and exact-tag workflow.
// 01
Capability evidence ledger
| Current status | Source state | Evidence and provenance | Publication state | Supported scope | Evidence |
|---|---|---|---|---|---|
Canonical source and stable identitystable-semantic-program-graph | Partial | Present in the pinned implementation; the release workflow succeeded for its selected gates. Consult the owning contract for exact admission. | Bounded pre-alpha source/toolchain profile | Readable `.spx` remains the canonical Git representation. Explicit `@id` values identify declarations independently of supported display-name changes. The revision binds canonical source and the compiler-owned implicit prelude, not incidental source spans or a graph wire format. | GitHub repository |
Bounded context and compact projectionsbounded-agent-context | Partial | Present in the pinned implementation; the release workflow succeeded for its selected gates. Consult the owning contract for exact admission. | Bounded pre-alpha source/toolchain profile | Context v1/v2 applies depth, node and byte budgets; v2 adds directional traversal. Task-oriented context and text, binary and model-text projections add focused exchange with replay checks. Smaller serialized output is not automatically fewer billed model tokens or better answers. | GitHub repository |
Semantic edits, not arbitrary rewritesrevision-bound-semantic-patches | Partial | Present in the pinned implementation; the release workflow succeeded for its selected gates. Consult the owning contract for exact admission. | Bounded pre-alpha source/toolchain profile | Inspect context, derive a candidate, preview impact, review, replay checks, then explicitly authorize application. The operation families now extend beyond renames to bounded expression replacement, structural changes and specified rebase/merge composition. Each protocol keeps its own revision, identity and operation limits. | GitHub repository |
Managed publication is a separate boundarymanaged-workspace-semantic-operations | Partial | Present in the pinned implementation; the release workflow succeeded for its selected gates. Consult the owning contract for exact admission. | Bounded pre-alpha source/toolchain profile | Managed workspace generations, candidate evidence, Project revision storage and MCP workflows retain explicit write and publication authority. Validation of multiple files is not an atomic update to arbitrary raw paths, Git or editors. The Rust embedding API supplies capped inputs, cancellation and opaque sessions, not unrestricted host access. | GitHub repository |
Replayable semantic evidencesemantic-evidence-capsules | Partial | Present in the pinned implementation; the release workflow succeeded for its selected gates. Consult the owning contract for exact admission. | Bounded pre-alpha source/toolchain profile | Evidence binds checked facts and candidate changes to source and revisions. A receipt can support review or rejection; it does not grant execution, mutation or publication authority. | GitHub repository |
Multi-module projects and offline scaffoldingbounded-multi-file-project | Partial | Present in the pinned implementation; the release workflow succeeded for its selected gates. Consult the owning contract for exact admission. | Bounded pre-alpha source/toolchain profile | Project manifests define source closure, entries, tests and selected exports. The bundled calculator supports check/test/run and admitted builds. new creates a fresh project from bundled files without initializing Git or fetching a registry. | GitHub repository |
Interpreter, native and Core Wasm executionnative-and-wasm-lowering | Partial | Present in the pinned implementation; the release workflow succeeded for its selected gates. Consult the owning contract for exact admission. | Bounded pre-alpha source/toolchain profile | Admitted scalar and owned-data profiles execute through the interpreter, C11/Clang and Core Wasm. Target conformance is profile-specific; ordinary library execution does not imply native/Wasm execution of source Agent stages. | GitHub repository |
Bounded scalar JavaScript/TypeScript exportspublic-wasm-scalar-exports | Partial | Present in the pinned implementation; the release workflow succeeded for its selected gates. Consult the owning contract for exact admission. | Bounded pre-alpha source/toolchain profile | Stable-ID scalar exports have a separate public Wasm profile and browser fixture. Owned-data packages, broad browser support, components and generic signatures have their own contracts and cannot inherit this support claim. | GitHub repository |
Typed runtime Agentsbounded-agent-runtime | Partial | Present in the pinned implementation; the release workflow succeeded for its selected gates. Consult the owning contract for exact admission. | Bounded pre-alpha source/toolchain profile | Initialize, observe, propose, decode, authorize, execute and reduce. The checked reducer selects Continue, Complete, Suspend or Fail, with authorization repeated each turn. Compiled Proposal schemas constrain streaming and typed decoding before effect dispatch. Source Agent stages currently execute in the retained interpreter, not native/Wasm parity. | GitHub repository |
Ownership and replayable cleanupownership-inspired-memory-management | Partial | Present in the pinned implementation; the release workflow succeeded for its selected gates. Consult the owning contract for exact admission. | Bounded pre-alpha source/toolchain profile | Owned and borrowed values, cleanup plans, loan facts and selected resource/generic compositions are implemented. v0.5.0 adds direct owned String variant payloads, while generic String substitutions and nested owned-record variant payloads remain restricted. This is not a complete general lifetime system or a Rust compatibility claim. | GitHub repository |
A broader everyday languageeveryday-language-and-collections | Partial | Present in the pinned implementation; the release workflow succeeded for its selected gates. Consult the owning contract for exact admission. | Bounded pre-alpha source/toolchain profile | Admitted profiles include records, variants, classes, inheritance, generics, Option/Result, explicit mutation, loops, collections, iterators, function values and bounded closures. Text, bytes and the bundled library support useful small programs. Owning closure captures, general generic constraints and arbitrary feature combinations remain limited. | GitHub repository |
Budgets, durable recovery and model callsmodel-budgets-and-durable-recovery | Partial | Present in the pinned implementation; the release workflow succeeded for its selected gates. Consult the owning contract for exact admission. | Bounded pre-alpha source/toolchain profile | Explicit host adapters supply credentials, transport and stores. Limits can cover calls, tokens, bytes, deadlines and quoted costs. Durable profiles acknowledge intent before dispatch and refuse uncertain redispatch. Generic host profiles support bounded retry/failover; the bound source-model route does not automatically retry or switch providers. Usage observations are not guaranteed invoices. | GitHub repository |
Application and economic-agent experimentsapplication-and-economic-agent-profiles | Experimental | Present in the pinned implementation; the release workflow succeeded for its selected gates. Consult the owning contract for exact admission. | Bounded pre-alpha source/toolchain profile | Checked HTTPS POST, Rust-host authentication/sessions and checkpointed jobs are separate integration profiles, not a full web framework. Economic Agents explore payment intents, simulation, approval and reconciliation with host-supplied wallets/signing. A model proposal is neither payment authority nor an exactly-once settlement guarantee. | GitHub repository |
Generated boundaries remain profile-specificowned-data-package-previews | Developer preview | Present in the pinned implementation; the release workflow succeeded for its selected gates. Consult the owning contract for exact admission. | Generated/private preview; publication and public support are separate decisions | Project v8 carries Bytes and selected Option/Result forms; v9 adds flat owned records, v10 owned UTF-8 and v11 nested owned records. Generated native/Rust and npm/Wasm consumers, private transports and public generic metadata each have separate contracts. Toolchain release, package publication and public support are different decisions. | GitHub repository |
Broad native and application supportbroad-platform-support | Roadmap | Three toolchain archives are published, and bounded browser/mobile/desktop profiles exist. A complete supported application platform across browser engines, physical devices, operating systems and installed workflows remains a broader product requirement. | Full support not established | Three toolchain archives are published, and bounded browser/mobile/desktop profiles exist. A complete supported application platform across browser engines, physical devices, operating systems and installed workflows remains a broader product requirement. | GitHub repository |
General bidirectional ecosystem interoperabilitybidirectional-ecosystem-interoperability | Roadmap | General ownership-safe foreign interfaces, stable aggregate/resource/component and generic ABIs, maintained package publication and broad host-language compatibility remain open. Metadata, generated code and private host fixtures do not complete this requirement. | Full support not established | General ownership-safe foreign interfaces, stable aggregate/resource/component and generic ABIs, maintained package publication and broad host-language compatibility remain open. Metadata, generated code and private host fixtures do not complete this requirement. | GitHub repository |
// 02
Claims this page intentionally does not make
- No production-readiness, universal memory-safety or bug-free guarantee.
- A successful workflow covers its selected gates, not ignored tests or every target and feature combination.
- Internal ownership/generic implementation does not establish a stable public generic ABI.
- Generated Rust/npm packages and Project v8-v11 promotion remain separate from the toolchain release.
- Source Agent stages use the retained interpreter; native/Wasm library execution does not establish Agent-stage parity.
- Provider transport, credentials, storage, authentication and signing remain explicit host responsibilities.
- Recovery records are not exactly-once network/payment guarantees or proof of provider invoices.
- No general token, latency, quality or economic advantage over other languages is established.
Reviewed against the pinned source commit and the v0.5.0 release record. Versioned specifications define admission and authority; older v0.4 release headings in the matrix and roadmap are historical, not the latest release identity. GitHub repository.
// REF
Primary sources for this page
Reviewed against the pinned source commit and the v0.5.0 release record. Versioned specifications define admission and authority; older v0.4 release headings in the matrix and roadmap are historical, not the latest release identity.
// FAQ
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.
Research project by Wavect: Wavect GmbH. Created by Wavect as an open-source systems research project.