Signature verified
SOUNIO • HIGH-STAKES SCIENTIFIC SOFTWARE Release provenance v0.100.3 GPU public contract 13/13 Stdlib reliability 81/86
Scientific software should expose uncertainty, provenance, and proof as part of the product.
Sounio is being built for researchers and technical leaders who need more than beautiful abstractions: checked artifacts, visible boundaries, and runtime evidence that survives contact with real scientific pressure.
2 attested targets
96 active entrypoints
Research programs and validation pressure are part of the product story, not a side note.
Built for teams shipping high-consequence software who need trust to be explicit.
Flagship storefront object
WebGPU proof, not decorative motion.
The homepage now carries a live provenance field above the fold so the GPU/runtime story is visible before the first docs click.
Capability probe
Live proof object
Provenance field with visible uncertainty transport
A storefront-grade GPU object: WebGPU when the browser permits it, deterministic fallback when it does not.
Lattice
34×22
Projected lanes
272
Gate
22%
Pulse
76%
Verified now
Claims should be inspectable, current, and sourced.
The homepage trust layer is driven by checked artifacts, not frozen marketing numbers. Follow the evidence, then decide whether the language is credible enough for your work.
Open the proof hubv0.100.3
Signature verified
Provenance checked 2026-03-06
81/86
stdlib reliability fixtures passing
96 active module entrypoints
13/13
public GPU contract checks passing
2 attested binary targets
7/7
required hyper lanes passing
science runtime status: pass
Flagship Proof Surface Render path WebGPU first Semantic object Provenance field Product role Storefront proof
A GPU story people can actually see.
The website needed one unmistakable technical object. This is it: a browser-side provenance field that prefers WebGPU, exposes uncertainty as a first-class visual signal, and still degrades cleanly when the browser cannot render on the GPU.
It is not the whole backend. It is the storefront counterpart to the PTX, runtime, and attestation work living in the repo. The point is to make the GPU thesis legible before anyone reads a single release note, then pair it with the climate truncation object below so the storefront proves judgment as well as acceleration.
Canvas fallback if browser support is absent.
Confidence lattice, uncertainty widening, tensor pulse.
A visible GPU thesis, not decorative motion.
Artifact-backed evidence Public checks 13/13 Attested targets 2 Native lanes 7/7 Release surface v0.100.3
Current public GPU contract passing in the checked snapshot.
Binary targets with published attestation evidence.
Required native execution lanes currently passing.
Signature verified for the currently surfaced core release.
Current source version souc 1.0.0-beta.4
Runtime posture pass
Flagship Systems
One object proves acceleration. The second proves judgment.
The storefront now carries two distinct proof objects. The GPU surface makes compute visible. The climate surface makes semantic refusal visible. Together they argue that Sounio is about trustworthy scientific systems, not just fast kernels.
Why two objects matter Flagship A Flagship B
A real storefront needs more than one trick.
A single WebGPU demo is memorable but incomplete. It can still read like a technical toy. The second flagship object changes the message: this project is also about when computation should stop, widen uncertainty, or refuse a false sense of certainty.
WebGPU provenance field
Shows that the storefront can carry a real GPU object, not only screenshots and prose.
Inspect the GPU routeClimate truncation surface
Shows that refusal is a feature: when ensemble variance becomes useless, the product stops instead of pretending confidence.
Inspect the climate routeClimate Flagship: Policy Truncation
A second storefront object: increase historical uncertainty and watch the system refuse a 2100 policy projection once the ensemble becomes unusable.
Increase to simulate wider confidence intervals in sparse pre-1950 surface temperature records.
Historical Record
Future Projection
Ensemble Spread (Uncertainty)
Sounio WASM Runtime
Why this site is changing.
It now leads with proof, boundaries, and real pressure instead of trying to look like a generic language launch site.
Trust is part of the language surface
Uncertainty, provenance, and effect boundaries are meant to stay visible all the way from source code to runtime behavior.
The public contract is inspectable
Current release provenance is signed, the stdlib reliability gate is 81/86, and the public GPU contract currently passes 13/13 checks.
The project is under real pressure
Research programs in PBPK, connectomics, and exceptional algebra keep forcing compiler and runtime edges into the open instead of letting them stay hypothetical.
Current verified snapshot
Read the full proof surface 
What is true right now, not what might be true later.
Release provenance is currently attested at v0.100.3. The stdlib reliability gate is 81/86, with 96 active module entrypoints. The GPU public contract passes 13/13 public checks with 2 attested binary targets.
Research pressure, not presentation theatre.
Sounio is being shaped by scientific programs that force uncertainty, provenance, algebra, and runtime evidence to stay honest. The point is not to look ambitious. The point is to survive contact with real work, and now to surface that pressure through flagship objects the site can actually carry.
Ollivier-Ricci curvature and biomedical graph work
The project is under pressure from real mathematical and biomedical work, not synthetic benchmark theatre.
Epistemic PBPK and GUM-through-ODE validation
PBPK, dosing, and uncertainty propagation keep forcing concrete compiler and runtime decisions into the open.
168-theorem, Fano classification, and hypercomplex execution
Non-associative and hypercomplex surfaces are not decorative. They are part of the technical burden the language is carrying.
v0.100.3 Signature verified
13/13 public GPU checks passing
81/86 stdlib reliability fixtures passing
7/7 required hyper lanes passing
- Top-level gpu-emit is not in the checked artifact CLI
- Intrinsic namespace is not yet part of the checked public surface
- Allocation intrinsics are not yet part of the checked public surface
- Sounio type checker does not infer `Option<i32>` from `Option::None` — bidirectional type inference required; compiler change needed
- uses unsafe blocks, raw pointer types (*const u8), and byte literals (b'..') which are not supported in the current JIT
Choose your route into the project.
The site now optimizes for three serious journeys instead of trying to make every page do every job at once.
Start with the claim, then inspect the evidence.
Use this path if you are evaluating whether Sounio is real, differentiated, and credible enough for serious attention.
See what is verifiedGet to a first successful run fast.
Use this path if you want the shortest route from installation to one bounded, real example without wading through every subsystem.
Start with docsTrace claims back to artifacts and source surfaces.
Use this path if you need release provenance, public contract boundaries, and machine-checked status artifacts before you trust the story.
Inspect provenancePrimary product surfaces.
These are the routes that matter most if you are assessing the project seriously.
Proof
See the current verified snapshot, boundaries, and source-of-truth artifacts.
Inspect the proof hubDocs
One direct route into the language, the implementation, and the current feature envelope.
Open docsResearch
Browse the scientific programs and validation pressure that are shaping the compiler.
View researchReleases
Track attested release provenance instead of trusting stale version marketing.
Read release provenanceShowcases
See bounded examples and domain narratives without mistaking them for the full contract.
Browse showcasesPlayground
Use the interactive surface once you understand the current proof envelope and boundaries.
Open playground