Skip to content

docs(site): main-status drift (#1630 iPhone evidence, #1661 multi-IO, catalog model.execute) + 2 SEO Q&As #163

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
enricopiovesan merged 1 commit into from
Oct 16, 2026
Merged

docs(site): main-status drift (#1630 iPhone evidence, #1661 multi-IO, catalog model.execute) + 2 SEO Q&As #163

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 7 additions & 5 deletions public/llms.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Traverse

> Traverse is a governed capability runtime for portable business logic. Value loop: **discover → execute → trace**. Usual authoring is skill-first plain English via `traverse-capability-author` (contract → WASM → human-reviewed PR); manual authoring still uses Rust→WASM — you do **not** need to write Rust for the usual path. One shared `runtime.wasm`; browser, native desktop, CLI, and MCP are clients/embedders, not different Traverse runtimes. Shipped consumers today: JS/TS (`traverse-embedder-web`), Rust (`traverse-embedder`), agents via `traverse-mcp`; Python shells out to `traverse-cli capability-package execute` (**no Python SDK**). v0.15.0 headline: governed model execution on every host — signed exact-ref on native Rust, the browser, Swift, Kotlin/Android, and .NET; every host enforces model rights (`model_usage` is required); Core ML is an opt-in Apple placement (macOS cargo-test evidence plus the Decision 113 iPhone spike; governed-path iPhone evidence is traverse#1630, still open). Swift (xcframework `swift-host-v0.15.0`; `Package.swift` on main pins the `swift-host-v0.15.0-1` rebuild, traverse#1695), Kotlin (Maven Central `com.traverse-framework:traverse-embedder` 0.15.0), and .NET (nuget.org `TraverseEmbedder` 0.15.0) are published, pre-1.0, and not Certified; edge is planned; cloud placement is an explicit non-goal for v0.1 — see /platforms.html and /what-is-real-today.html. Apache 2.0, pre-1.0 (v0.15.0). The agent proposes; the runtime decides.
> Traverse is a governed capability runtime for portable business logic. Value loop: **discover → execute → trace**. Usual authoring is skill-first plain English via `traverse-capability-author` (contract → WASM → human-reviewed PR); manual authoring still uses Rust→WASM — you do **not** need to write Rust for the usual path. One shared `runtime.wasm`; browser, native desktop, CLI, and MCP are clients/embedders, not different Traverse runtimes. Shipped consumers today: JS/TS (`traverse-embedder-web`), Rust (`traverse-embedder`), agents via `traverse-mcp`; Python shells out to `traverse-cli capability-package execute` (**no Python SDK**). v0.15.0 headline: governed model execution on every host — signed exact-ref on native Rust, the browser, Swift, Kotlin/Android, and .NET; every host enforces model rights (`model_usage` is required); Core ML is an opt-in Apple placement (macOS cargo-test evidence plus the Decision 113 iPhone spike; governed-path iPhone evidence for traverse#1630 landed on main after v0.15.0: BirdNET p95 141 ms per 3 s clip on one iPhone 14 Pro Max, unreleased schema 2.3.0). Swift (xcframework `swift-host-v0.15.0`; `Package.swift` on main pins the `swift-host-v0.15.0-1` rebuild, traverse#1695), Kotlin (Maven Central `com.traverse-framework:traverse-embedder` 0.15.0), and .NET (nuget.org `TraverseEmbedder` 0.15.0) are published, pre-1.0, and not Certified; edge is planned; cloud placement is an explicit non-goal for v0.1 — see /platforms.html and /what-is-real-today.html. Apache 2.0, pre-1.0 (v0.15.0). The agent proposes; the runtime decides.
- Start here (narrative): https://traverse-framework.com/blog/what-is-real-today-start-here.html
- How do I start with Traverse as an agent?: https://traverse-framework.com/questions/how-do-i-start-with-traverse-as-an-agent.html
- What does Traverse not claim yet?: https://traverse-framework.com/questions/what-does-traverse-not-claim-yet.html
Expand Down Expand Up @@ -75,15 +75,17 @@ Current packages: crates.io Traverse at 0.15.0; npm `traverse-embedder-web@0.15.
- [Changelog](https://traverse-framework.com/changelog.html): release-by-release history.
- [Security & Permanence Audit](https://traverse-framework.com/security-audit.html): every known finding, its GitHub ticket, and its real status — not a marketing page.
- [FAQ](https://traverse-framework.com/faq.html) and [Questions](https://traverse-framework.com/questions.html): 70+ specific Q&A pages, mostly long-tail but accurate.
- [What is exact-ref model execution?](https://traverse-framework.com/questions/what-is-exact-ref-model-execution.html): discover → execute → trace; one shared `runtime.wasm`; signed schema `2.0.0` and later + `model.sig.json`; host-owned trust; **breaking** `model_usage` (`commercial` | `non_commercial`, else `usage_undeclared`); third-party ONNX via `traverse-cli model`; guest ABI v3 snapshot reuse; Core ML opt-in on Apple (macOS cargo test + Decision 113 spike; governed-path iPhone evidence traverse#1630 still open); `digits-mlp-1.0.0` (test-only key; custody #1567 still open); published exact-ref execute is native + web 0.15.0 + Swift ExactModelHost (`swift-host-v0.15.0`) + Kotlin and .NET ExactModelHost in Maven/NuGet 0.15.0 (#1651 closed; first landed in v0.12.0). No host is Certified. [Release](https://github.com/traverse-framework/traverse/releases/tag/v0.15.0) · historical embedder notes: [v0.14.0: what changed for embedders](https://traverse-framework.com/blog/traverse-0-14-0-what-changed-for-embedders.html).
- [What is exact-ref model execution?](https://traverse-framework.com/questions/what-is-exact-ref-model-execution.html): discover → execute → trace; one shared `runtime.wasm`; signed schema `2.0.0` and later + `model.sig.json`; host-owned trust; **breaking** `model_usage` (`commercial` | `non_commercial`, else `usage_undeclared`); third-party ONNX via `traverse-cli model`; guest ABI v3 snapshot reuse; Core ML opt-in on Apple (macOS cargo test + Decision 113 spike; governed-path iPhone evidence for traverse#1630 landed on main after v0.15.0, unreleased); `digits-mlp-1.0.0` (test-only key; custody #1567 still open); published exact-ref execute is native + web 0.15.0 + Swift ExactModelHost (`swift-host-v0.15.0`) + Kotlin and .NET ExactModelHost in Maven/NuGet 0.15.0 (#1651 closed; first landed in v0.12.0). No host is Certified. [Release](https://github.com/traverse-framework/traverse/releases/tag/v0.15.0) · historical embedder notes: [v0.14.0: what changed for embedders](https://traverse-framework.com/blog/traverse-0-14-0-what-changed-for-embedders.html).
- [How do hosts trust signed models?](https://traverse-framework.com/questions/how-do-hosts-trust-signed-models.html): discover → execute → trace; one shared `runtime.wasm`; host-owned trust roots gate `register_package`; pin by digest + `model.sig.json`; `model_usage` required in v0.15.0; test-only digits-mlp key (custody #1567 still open); published exact-ref execute is native + web + Swift `swift-host-v0.15.0` + Kotlin and .NET 0.15.0; third-party ONNX can be packaged and signed with `traverse-cli model`.
- [Which hosts run signed exact-ref models?](https://traverse-framework.com/questions/which-hosts-run-signed-exact-ref-models.html) · [Is production model signing ready?](https://traverse-framework.com/questions/is-production-model-signing-ready.html) · [Can Kotlin or .NET run exact-ref yet?](https://traverse-framework.com/questions/can-kotlin-or-dotnet-embedders-run-exact-ref-yet.html): discover → execute → trace; one shared `runtime.wasm`; published exact-ref is native + web 0.15.0 + Swift `swift-host-v0.15.0` + Kotlin and .NET 0.15.0 (#1651 closed); production signing custody is not finished (#1567 still open; v0.15.0 shipped key-generation tooling).
- [What is ExactModelHost?](https://traverse-framework.com/questions/what-is-exact-model-host.html): host-side connector for governed exact-ref model packages (Spec 138). Register a signed package under host-owned trust roots, then execute under discover → execute → trace. Not a second runtime. Published in 0.15.0: native connector, web `ExactModelBrowserHost`, Swift `ExactModelHost` on `swift-host-v0.15.0`, Kotlin and .NET `ExactModelHost` in Maven/NuGet 0.15.0 (#1651 closed). Test-only digits-mlp key; custody #1567 still open. Not catalog `model.execute`. Not Hugging Face.
- [Signed models on every host. The rights travel with them.](https://traverse-framework.com/blog/signed-models-on-every-host.html): Oct 15 v0.15.0 narrative — discover → execute → trace; signed exact-ref on native Rust, web, Swift `swift-host-v0.15.0`, Kotlin and .NET 0.15.0 via small audited native boundaries sharing `traverse-model-host-frame`, byte-identical conformance vectors, one 21-case rights suite; **breaking** `model_usage`; `traverse-cli model` + `package-onnx` (install `traverse-cli-rs`, runner from `onnx-runner-v0.15.0`); ABI v3 prepare-once; Core ML opt-in on Apple (iPhone governed evidence traverse#1630 open). Caveats: web `modelUsage` not validated in 0.15.0 (traverse#1685; fix #1698 on main, unreleased), CLI verify usage (traverse#1686, main only), test-only key (custody #1567), registry capability revocation #1598 not shipped. No host Certified.
- [Signed models on every host. The rights travel with them.](https://traverse-framework.com/blog/signed-models-on-every-host.html): Oct 15 v0.15.0 narrative — discover → execute → trace; signed exact-ref on native Rust, web, Swift `swift-host-v0.15.0`, Kotlin and .NET 0.15.0 via small audited native boundaries sharing `traverse-model-host-frame`, byte-identical conformance vectors, one 21-case rights suite; **breaking** `model_usage`; `traverse-cli model` + `package-onnx` (install `traverse-cli-rs`, runner from `onnx-runner-v0.15.0`); ABI v3 prepare-once; Core ML opt-in on Apple (iPhone governed evidence traverse#1630 landed on main after the release, unreleased). Caveats: web `modelUsage` not validated in 0.15.0 (traverse#1685; fix #1698 on main, unreleased), CLI verify usage (traverse#1686, main only), test-only key (custody #1567), registry capability revocation #1598 not shipped. No host Certified.
- [What is model_usage?](https://traverse-framework.com/questions/what-is-model-usage-in-traverse.html): since v0.15.0 apps with `exact_model_dependencies` must declare `model_usage: commercial | non_commercial` or fail closed with `usage_undeclared`; `commercial` rejects `prohibited` packages (`rights_policy_denied`); results carry `model_evidence`; Rust `ExactModelHostConnector::model_usage`, web `modelUsage`, Swift `modelUsage:` (no default), Kotlin/.NET `modelUsage`. Gaps: published web 0.15.0 accepts any string (traverse#1685; fix #1698 merged on main, rejects with `usage_invalid`, unreleased); `traverse-cli-rs` 0.15.0 `model verify` has no usage flag (traverse#1686, fixed on main after release).
- [How do I package my own ONNX model?](https://traverse-framework.com/questions/how-do-i-package-an-onnx-model-for-traverse.html): `cargo install traverse-cli-rs --version =0.15.0 --locked` (Rust ≥ 1.94; crates.io `traverse-cli` is unrelated); `runner.wasm` from GitHub release `onnx-runner-v0.15.0` (sha256 `f3902703fe79cc161c13b87cf507dcb25cb53ea3c2a68bed6cc753f9df100966`); `model package-onnx` → sign → verify → conformance → pin; one input + one output tensor only (traverse#1661); post-processing belongs in capabilities, hosts stay UI + I/O. Not catalog `model.execute`, not Hugging Face.
- [How do I package my own ONNX model?](https://traverse-framework.com/questions/how-do-i-package-an-onnx-model-for-traverse.html): `cargo install traverse-cli-rs --version =0.15.0 --locked` (Rust ≥ 1.94; crates.io `traverse-cli` is unrelated); `runner.wasm` from GitHub release `onnx-runner-v0.15.0` (sha256 `f3902703fe79cc161c13b87cf507dcb25cb53ea3c2a68bed6cc753f9df100966`); `model package-onnx` → sign → verify → conformance → pin; 0.15.0 packager is one input + one output tensor; named multi-input/multi-output packaging for HF-style text encoders merged on main after the release (traverse#1661, PR #1704), not released, rebuilt audited runner + signed reference encoder pending; post-processing belongs in capabilities, hosts stay UI + I/O. This is the host connector path, not Hugging Face.
- [What happens when a host marks a model package revoked?](https://traverse-framework.com/questions/what-happens-when-a-host-marks-a-model-package-revoked.html): v0.15.0 hosts own a package-status map for signed model packages — `revoked` blocks (`package_revoked`), `deprecated` runs and is flagged; `model_evidence` on every result. Not registry capability revocation (runtime refusal is traverse#1598, not shipped).
- [Can Traverse run models on a GPU or the Apple Neural Engine?](https://traverse-framework.com/questions/can-traverse-run-models-on-a-gpu-or-neural-engine.html): Core ML is an opt-in Apple placement in v0.15.0. Default stays `wasm-cpu`. Ordered placements, on-device self-check, fail-closed `placement_unavailable`, placement evidence (Decision 112). Evidence so far is macOS cargo test plus the Decision 113 iPhone spike. Governed-path iPhone evidence is traverse#1630, still open. No web, Android, or desktop GPU adapter. No host is Certified.
- [Can Traverse run models on a GPU or the Apple Neural Engine?](https://traverse-framework.com/questions/can-traverse-run-models-on-a-gpu-or-neural-engine.html): Core ML is an opt-in Apple placement in v0.15.0. Default stays `wasm-cpu`. Ordered placements, on-device self-check, fail-closed `placement_unavailable`, placement evidence (Decision 112). Published-release evidence is macOS cargo test plus the Decision 113 iPhone spike. Governed-path iPhone evidence landed on main after v0.15.0 (traverse#1630): BirdNET on one iPhone 14 Pro Max, p95 141 ms per 3 s clip under `[coreml, wasm-cpu]`; needs unreleased schema 2.3.0 `score_transform`; `cpu_and_neural_engine` failed self-check and fell back to `wasm-cpu`. No web, Android, or desktop GPU adapter. No host is Certified.
- [How fast does a model run on iPhone with Traverse?](https://traverse-framework.com/questions/how-fast-does-a-model-run-on-iphone-with-traverse.html): one measured case on unreleased main (traverse#1630, PR #1709): iPhone 14 Pro Max, iOS 26.6, Release build, Swift `ExactModelHost`, BirdNET v2.4 int8, policy `[coreml, wasm-cpu]` — Core ML `all` p95 141.3 ms per 3 s clip vs `wasm-cpu` p95 10.0 s; top-5 21/21 vs wasm-cpu; timing is the whole governed call. Not reproducible on v0.15.0 (needs schema 2.3.0 `score_transform`). One device, one model, test-only key, non-commercial weights. Follow-ups #1706, #1707, #1708. No host is Certified.
- [What is the model.execute catalog capability?](https://traverse-framework.com/questions/what-is-the-model-execute-catalog-capability.html): `model.execute@1.0.0` in the registry catalog (registry#639, index-v407, Oct 15 2026) — a shim over host connector `traverse.model-runtime`: exact pin + `input_ref` + `model_usage` + non-empty `trust_root` in; `model_evidence` or unchanged fail-closed Spec 138 reason out. Does not fetch models, hold keys, or choose a model. Pins connector 2.3.0 (on Traverse main; v0.15.0 hosts carry 2.2.0). Registry spec 027 is draft. No published-release demo yet.
- [What is digits-mlp?](https://traverse-framework.com/questions/what-is-digits-mlp.html): first trained exact-ref package in v0.14.0 (UCI digits MLP, 96.10% held-out, bit-identical); test-only signing; not a general LLM.
- [Does the website use the latest traverse-embedder-web?](https://traverse-framework.com/questions/does-the-website-use-the-latest-traverse-embedder.html): site pins `^0.15.0` (matching npm) and `/discover` admits its signed demo fixture through `registerPackage` with `modelUsage: non_commercial`; the site can lag future releases, so product apps pin published packages, not the website demo.
- [How does Traverse complement Hugging Face?](https://traverse-framework.com/questions/how-does-traverse-complement-hugging-face.html): Hub = provenance; Traverse = pinned signed client-first capability; not Transformers.js/Hub replacement; no defer promise until a second executor exists.
Expand Down
Loading
Loading