EVIDENCE · 615E501 · 2026-10-06

What v0.8.0 implements, and what it does not prove.

Evidence has a state, a scope, and an expiry date.

Version 0.8.0 resolves to commit 615e501 and was published on 6 October 2026 after all 82 exact-tag jobs passed. Its implementation includes source laws, richer Rust integration, a compiler-connected harness and checked development reload. The ledger below separates each working profile from its remaining product and support requirements.

semaprax://evidencev0.8.0

entity     Semaprax
status     beta
snapshot   615e501
authority  github.com/wavect/semaprax

// STATUS

Repository status at the audited snapshot

Repository snapshot	`615e501` · 2026-10-06. The v0.8.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.8.0` · Published 6 October 2026 at 07:37 UTC. All 82 exact-tag jobs succeeded. Three toolchain archives, SHA256SUMS, per-archive attestations and signed aggregate provenance were published. The release job independently verified the signed set before publication. The 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.

What does Semaprax implement today?

The release provides checked source and semantic edits, typed runtime Agents, bounded Lean/Z3 law proofs, selected Rust APIs and generated adapters, same-thread Futures, harness providers and skills, hot-reload development sessions, token reports and signed archive provenance. Exact-tag CI, focused local tests and measured application trials answer different questions. The full-goal matrix still records 55 Partial requirements; that total does not mean the individual implemented profiles are missing.

// 01

Capability evidence ledger

Current status	Source state	Evidence and provenance	Publication state	Supported scope	Evidence
Canonical source and stable identity `stable-semantic-program-graph`	Partial	Exact-tag Project and Rust jobs passed the admitted graph contracts; the full semantic-foundation goal remains Partial.	Bounded beta 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 projections `bounded-agent-context`	Partial	Bounded typed context, compact replay and committed local tokenizer comparisons are implemented.	Bounded beta source/toolchain profile	Select exact graph or task context with depth, direction, node and byte bounds. Model-text v2 reduces tokens on selected large inputs and grows on small ones; reports preserve the tokenizer and comparison boundary.	GitHub repository
Semantic edits, not arbitrary rewrites `revision-bound-semantic-patches`	Partial	Exact-tag source-repair and Project jobs passed bounded edit contracts; arbitrary repository rewrites are outside scope.	Bounded beta 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 boundary `managed-workspace-semantic-operations`	Partial	Project Product Acceptance passed on Linux, macOS and Windows; publication still requires explicit authority.	Bounded beta 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 evidence `semantic-evidence-capsules`	Partial	Revision-bound evidence is implemented and release claim reconciliation passed; a receipt grants no mutation authority.	Bounded beta 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 scaffolding `bounded-multi-file-project`	Partial	Project Manifest, Product Acceptance and installed-toolchain journey jobs passed; service-host breadth is separately scoped.	Bounded beta source/toolchain profile	Manifests define declared source, entries, tests and exports. Bundled calculator, library and service templates have their own profiles. new creates a fresh project from compiled-in files; source checking, interpreted tests and target builds follow the selected manifest contract.	GitHub repository
Interpreter, native and Core Wasm execution `native-and-wasm-lowering`	Partial	Three target archives and selected native/Wasm gates passed; each runtime profile retains its own admission limits.	Bounded beta source/toolchain profile	Admitted scalar, owned-data, generic, collection and immutable-list profiles execute through interpreter, native C11/Clang and Core Wasm with profile-specific conformance. Opt-in Agent stage hosts are separately bound; ordinary yields still refuse native/Wasm emission.	GitHub repository
Bounded scalar JavaScript/TypeScript exports `public-wasm-scalar-exports`	Partial	The exact-tag Chromium scalar-export job passed; other browser engines and owned-data packages are separate.	Bounded beta 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 Agents `bounded-agent-runtime`	Partial	AGENT-06 lifecycle/client jobs passed across Linux, macOS and Windows. Default live routes remain interpreter-selected; opt-in held target hosts have separate bounded evidence.	Bounded beta source/toolchain profile	Typed source roles drive initialization, observation, model proposals, authorization, effects and reduction. Bound Proposal schemas constrain decoding. Default live routes use the interpreter; selected library routes can supply held native C11/Core Wasm stage hosts under their own local parity and recovery gates.	GitHub repository
Ownership and replayable cleanup `ownership-inspired-memory-management`	Partial	GEN-05B and Rust jobs passed admitted ownership profiles; general lifetime safety remains open.	Bounded beta source/toolchain profile	Owned and borrowed values, cleanup plans, selected records/variants and resource compositions are executable. Bounded owned Bytes, scalar-snapshot, transactional mutable and synchronous borrowed-text callbacks have move, escape and cleanup controls. General lifetimes, arbitrary capture shapes and public borrowed ABIs remain open.	GitHub repository
A broader everyday language `everyday-language-and-collections`	Partial	The exact-tag STD-08 bundled-library job passed; complete Everyday library and physical providers remain open.	Bounded beta source/toolchain profile	Records, variants, classes, inheritance, scoped generic inference, Option/Result, mutation, loops, vectors, iterators, function values and bounded closures support useful programs. Immutable List<i64> adds persistent constructors and source-bound law examples; broader constraints and feature combinations retain limits.	GitHub repository
Budgets, durable recovery and model calls `model-budgets-and-durable-recovery`	Partial	AGENT-06 jobs passed bounded lifecycle and accounting paths; provider bills and host policies remain external facts.	Bounded beta 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 experiments `application-and-economic-agent-profiles`	Experimental	The bounded reference snapshot host has local packaged and selected hosted Linux/Podman evidence; economic-agent authority remains explicitly supplied.	Bounded beta source/toolchain profile	Reference-service routes compose checked session, task and job decisions with snapshot persistence and selected JSON-event or OTLP telemetry. SQL adapters are refused. Economic Agents retain explicit wallet, simulation, approval, signing and reconciliation responsibilities; no external exactly-once guarantee follows.	GitHub repository
Generated boundaries remain profile-specific `owned-data-package-previews`	Developer preview	Project Product Acceptance and native Rust SDK jobs passed on three hosts; generated package publication remains undecided.	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 support `broad-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 interoperability `bidirectional-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
Signed release provenance `release-provenance`	Demonstrated	Exact-tag publish job signed aggregate provenance, independently verified the signed asset set and published three archive attestations.	Published beta toolchain and provenance assets	Archive integrity and signed build provenance are evidenced; notarization, cross-host reproducibility and current revocation status are not.	GitHub repository
Compiler-owned generic target boundary `public-generic-compiled-boundaries`	Developer preview	The exact-tag generic milestone passed on Linux, macOS and Windows; a private checked Core Wasm provider, TypeScript carrier and native settlement corpus execute.	Unpublished private profile; PG-9 remains unsupported	One admitted generic endpoint and bounded consumer/settlement cases are real. Wider endpoint shapes, public ABI support and package publication remain open.	GitHub repository
Opt-in native and Wasm Agent stages `source-agent-target-parity`	Developer preview	Bounded source Agent stages execute through sealed interpreter, native C11 and Core Wasm routes, with selected local parity, recovery and migration gates.	Explicit library target selectors; default live routes remain interpreter-selected	A host supplies the held native or Wasm runtime explicitly. This does not establish general instruction metering, unrestricted cleanup or finalizer parity, every source profile, or broad deployed/hosted Agent target support.	GitHub repository
Bounded source yields and durable continuations `bounded-resumable-effects`	Experimental	Interpreter profiles admit sequential and control-dependent yields, selected owned-Bytes carrying and authenticated durable source recovery. A public owned-Agent slice has two-turn and selected process-restart gates.	No public native/Wasm continuation ABI	Each profile bounds suspension sites, owned state and restoration phases. Ordinary native/Wasm emitters still refuse yielding functions. General scheduling, arbitrary owned continuations, universal migration and a stable public continuation ABI remain open.	GitHub repository
Local signed Registry-v3 trust `signed-registry-local-trust`	Experimental	Producer-backed roots and leaves, signed metadata, held generations, lock-bound artifact reads and cache bridging have focused local gates.	No hosted registry or public distribution	Signed local evidence grants no ambient fetch, execution or package-publication authority. Production roots, network transport and supported distribution remain separate.	GitHub repository
Pinned Lean proof and obligation gate `lean-kernel-obligation-gate`	Demonstrated	The exact-tag hosted Lean job passed the Kernel-0 proof, axiom audit, generated obligation export and differential corpus.	Bounded research proof, not a general safety certificate	The proof covers its formal Kernel-0 slice. It does not prove the full language, all backend behavior or absence of vulnerabilities.	GitHub repository
Source laws and replayed proofs `source-laws-and-proofs`	Partial	Native law syntax, selected law inventories, protected repair and bounded installed Lean/Z3 profiles have executable positive and mutation/refusal evidence.	Bounded source and proof-tool profiles	Contract, relational, modular scalar, finite structured, protocol and immutable-list laws keep exact source and proof identities. Unsupported goals remain open or refused; lowering, foreign internals and external side effects are outside a general proof claim.	GitHub repository
Rich native Rust integration `native-rust-rich-interop`	Developer preview	Selected imports, generated owners/views/callbacks and real Regex/Url, Serde/iterator and reqwest/Tokio application gates exist.	Generated developer previews; selected native signatures	Owner-tied views and bounded FnOnce, FnMutI64 and synchronous borrowed-text captures preserve their specific lifetime and rollback contracts. Application receipts include adverse throughput and guest-host limits; arbitrary crate, ABI and zero-overhead claims remain open.	GitHub repository
Same-thread Rust Futures `local-rust-futures`	Developer preview	Generated local Future handles, selected source yield, caller-owned executors and real HTTP/cancellation/shutdown controls have local evidence.	Bounded local generated and Project-selected profiles	The host supplies the executor and runtime. One admitted source suspension and exact Project revision are bound to the generated adapter; streams, cross-thread execution, durable arbitrary Future state and universal async imports remain separate.	GitHub repository
Compiler-connected development harness `compiler-assisted-harness`	Experimental	Task/plan/repair feedback, provider locks/trust, retrieval, official skills, model routing and bridge/MCP have local and selected hosted Linux evidence.	Full-toolchain harness and standalone host; explicit project setup	Project-selected Graft/Graphify, RTK views and Ponytail/Caveman skills support bounded workflows. WikiSkill evolution and routing qualification are explicit gates. Windows, broader model/platform results and automatic default changes require additional evidence.	GitHub repository
Checked development hot reload `checked-hot-reload`	Developer preview	Retained interpreter sessions and VS Code controls pass selected macOS arm64 activation, rejection, safe-point and lifecycle gates.	Bounded local dev session; source-Agent migration is a separate lane	Candidates are checked before activation and invalid edits leave the active revision usable. The recorded small fixture reload is slower than restart. Other operating systems, native/Wasm state swapping and production rollout remain outside this result.	GitHub repository
Context, token and task-cost accounting `task-token-accounting`	Partial	Exact local tokenizer reports, session aggregation and normalized provider receipts are implemented; the recorded paid campaign did not qualify a change to defaults.	Local measurement and explicit provider-accounting profiles	Keep comparable selected payloads, tokenizer fingerprints, reservations, observed usage and reported/estimated money separate. Missing usage remains unavailable and failed calls remain accounted for. The recorded best saving did not meet the declared threshold.	GitHub repository

// 02

Boundaries that remain open

Beta release evidence does not establish production readiness, universal memory safety or absence of bugs.
A successful workflow covers the gates it ran. Ignored tests, unprovisioned hosts and additional target combinations require separate evidence.
Native law proofs cover their selected semantics and assumptions. They do not prove arbitrary Rust internals, all lowering or external settlement.
Generated Rust/npm package publication, public generic ABI support and broader Project profile promotion remain separate decisions.
Default live Agent routes use the interpreter. Opt-in caller-held native/Wasm stage routes have bounded evidence, not unrestricted backend parity.
Model providers, credentials, stores, wallet signing and external authority remain explicitly configured host responsibilities.
Durable recovery preserves uncertainty; it does not guarantee exactly-once network/payment effects or provider billing.
Compact payload reductions and paid trials do not establish a general token, latency, quality or task-cost advantage.

Reviewed against the v0.8.0 tag and its pinned source commit. Versioned specifications define admission and authority; older release headings in the matrix and roadmap are historical. GitHub repository.

// DOCS

Open the Semaprax handbook

The online handbook is the English guide published from main and may cover changes after 0.8.0. Use the pinned snapshot when reproducing this release.

Live handbook

The current English learning path, published from main.

0.8.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.8.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.

// REF

Primary sources for this page

Reviewed against the v0.8.0 tag and its pinned source commit. Versioned specifications define admission and authority; older release headings in the matrix and roadmap are historical.

// FAQ

Questions and practical answers

What does Demonstrated mean?

A named artifact or execution path passed its dedicated gate under the stated source, host and feature constraints. The ledger also records Partial, Developer preview and Experimental profiles. A demonstrated slice does not establish complete language or platform support.

Does a green CI run prove security?

It supplies evidence for the checks that actually ran, including positive and adverse paths. Version 0.8.0 also has signed release provenance and archive attestations. Those checks do not prove absence of vulnerabilities, cover every ignored or provisioned test, or turn a bounded proof into whole-language correctness.

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