Traverse v0.15.0 — signed models on every host

[enricopiovesan]

Traverse v0.15.0

Tagged 2026-10-13 (v0.15.0). Product GitHub Release: Traverse v0.15.0.

Published today: the Traverse crates at 0.15.0 on crates.io, traverse-embedder-web@0.15.0 on npm, com.traverse-framework:traverse-embedder 0.15.0 on Maven Central, TraverseEmbedder 0.15.0 on nuget.org, the Swift xcframework on swift-host-v0.15.0, and registry client traverse-registry 0.28.0.

Throughline

Governed model execution on every host. In v0.14.0, signed exact-ref model packages ran on native Rust and the browser only. In v0.15.0 the same packages run on the Swift, Kotlin/Android and .NET embedders too, and every host enforces the package's machine-readable rights. The loop doesn't change: capabilities still discover → execute → trace, on the one shared runtime.wasm, and hosts still only do UI and I/O.

What changed

• Exact-ref execution on Swift, Kotlin/Android and .NET. Each host runs signed packages through a small audited native boundary. All three share one framed protocol crate, match the signed conformance vectors byte for byte, and pass the same 21-case rights suite.
• Model rights are enforced (breaking). An app that pins models must declare model_usage: commercial | non_commercial; without it, calls fail closed with usage_undeclared. Commercial use rejects packages whose rights say prohibited. Hosts can mark a package revoked (blocked) or deprecated (flagged), and every result carries model_evidence.
• Package your own ONNX model. traverse-cli model can digest, sign, verify and pin packages, and model package-onnx turns an ONNX model into a signed package on an import-free runner guest. The model packaging guide walks through it.
• Faster repeat inference. Guest ABI v3 prepares the model once and restores a clean snapshot for every call. Output is byte-identical on the fresh and snapshot paths.
• Core ML on Apple hosts, opt-in. A package can carry a signed Core ML variant. It runs only if the execution policy lists that placement and the variant passes an on-device self-check against its signed conformance vector; otherwise the call falls back to wasm-cpu, and placement_evidence says which one ran.

What's not done yet

• The Core ML evidence so far is macOS test runs plus an earlier iPhone spike. Governed-path iPhone evidence is still open in #1630.
• Everything is pre-1.0, and no host is Certified.

Upgrading

Read the upgrade guide. The short version: declare model_usage on any host that runs pinned models, add the new fields and variants if you build ExecutionPolicy or HostConnectorHostResult with struct literals or match every ModelFailureReason, and pin crates and traverse-embedder-web together at 0.15.0, with traverse-registry at 0.28.0.

For agents and readers

If you land on a swift-host-v* or runtime-wasm-v* GitHub Release, that's a binary distribution, not the product cut. Cite package versions from crates.io, npm, Maven Central, nuget.org or llms.txt.