What shipped in Traverse. Each release is backed by versioned, reviewable work.
Native — Linux, macOS, Windows
Shipped
- The default target and the most mature. traverse-runtime gives you full orchestration — NativeExecutor, ThreadPoolExecutor, and a Wasmtime-backed WasmExecutor for sandboxed capability execution. This is what traverse-cli runs on, and what every quickstart walks you through.
+ The default target and the most mature. traverse-runtime gives you full orchestration — NativeExecutor, ThreadPoolExecutor, and a Wasmtime-backed WasmExecutor for sandboxed capability execution. This is what traverse-cli runs on, and what every quickstart walks you through. Signed exact-ref execute (ExactModelHostConnector) shipped in the v0.14.0 crates. Capabilities still discover → execute → trace on one shared runtime.wasm.
Three things are true here, all shipped. First, the runtime core builds for wasm32-unknown-unknown with native adapters excluded — contracts, registry resolution, routing, traces, and events all run in a browser or edge-WASM guest with your own executor behind CapabilityExecutor. Second: the public Web/TypeScript embedder SDK (traverse-embedder-web), shipped in v0.8.0, loads a bundle, digest-verifies every WASM capability, and executes it directly in the browser's native WebAssembly host through a minimal WASI preview1 shim — no nested engine, no server sidecar. Third, added in v0.10.0: a governed browser-hosted path for executing a single verified capability by exact id and version, either through traverse-cli serve's verified-entrypoint endpoint or along the validated execute_entrypoint flow, returning a result plus a redacted trace receipt (specs 023, 115).
- Scope it honestly: in-browser workflow execution via the embedder SDK is limited to linear, direct-triggered pipelines — event-driven and conditional edges are rejected at init — and the verified-entrypoint path runs one pre-published capability at a time against already-synced registry state rather than an arbitrary live-registry lookup. traverse-embedder-web@0.14.0 is published to npm (aligned with the v0.14.0 cut). The runtime's requested_target placement router still resolves only local; browser execution is reached through these SDKs and endpoints, not by requesting a browser target.
+ Scope it honestly: in-browser workflow execution via the embedder SDK is limited to linear, direct-triggered pipelines — event-driven and conditional edges are rejected at init — and the verified-entrypoint path runs one pre-published capability at a time against already-synced registry state rather than an arbitrary live-registry lookup. traverse-embedder-web@0.14.0 is published to npm (aligned with the v0.14.0 cut) and executes signed exact-ref (ExactModelBrowserHost). The runtime's requested_target placement router still resolves only local; browser execution is reached through these SDKs and endpoints, not by requesting a browser target.
- The engine blocker recorded here as of July 19, 2026 is resolved. The wasmi feasibility spike below was adopted the next day: ADR-0014 selected the wasmi Apple runtime profile, ADR-0015 governed a production Swift wasmi C ABI, and Spec 074 (Approved) now defines the resource-control certification conditions. packages/swift/TraverseEmbedder ships a production WasmiHostBridgeClient backed by TraverseSwiftHost — a released XCFramework wrapping the wasmi interpreter behind a narrow C ABI — that enforces host-owned artifact-size, memory, fuel-per-invocation, and I/O limits on every call. The earlier WasmKit path, which never exposed those controls, has been removed from the package entirely (Decision 96, #1469); WasmKit is not supported. The xcframework ships as versioned swift-host-v* GitHub release assets (currently swift-host-v0.14.0-4), and Package.swift pins its checksum.
+ The engine blocker recorded here as of July 19, 2026 is resolved. The wasmi feasibility spike below was adopted the next day: ADR-0014 selected the wasmi Apple runtime profile, ADR-0015 governed a production Swift wasmi C ABI, and Spec 074 (Approved) now defines the resource-control certification conditions. packages/swift/TraverseEmbedder ships a production WasmiHostBridgeClient backed by TraverseSwiftHost — a released XCFramework wrapping the wasmi interpreter behind a narrow C ABI — that enforces host-owned artifact-size, memory, fuel-per-invocation, and I/O limits on every call. The earlier WasmKit path, which never exposed those controls, has been removed from the package entirely (Decision 96, #1469); WasmKit is not supported. The xcframework ships as versioned swift-host-v* GitHub release assets (currently swift-host-v0.14.0-4), and Package.swift pins its checksum. That same published xcframework includes ExactModelHost for signed exact-ref execute (GitHub Release + SPM binary target).
The iOS and macOS clients in reference-apps run embedded: in-process TraverseEmbedder loading a digest-pinned runtime.wasm, with no traverse-cli serve sidecar. What's still open: Spec 529 (approved September 13, 2026) defines one host-neutral Certified/Preview classification across Web, Linux/Rust, Apple, Android, and Windows/.NET, but the five-platform conformance runner it calls for is later work, so no host is Certified today. Treat this as real, resource-bounded, pre-1.0 execution, not a certified release.
- packages/kotlin/TraverseEmbedder has a working ChicoryRuntimeBridge pinned to Chicory 1.7.5. Bundle validation, lifecycle types, and the no-sidecar Compose reference-app integration have all landed — and the package is published on Maven Central as com.traverse-framework:traverse-embedder (0.14.0, lockstep with the core release). Like every host, it's pre-1.0 and not Certified under Spec 529 yet.
+ packages/kotlin/TraverseEmbedder has a working ChicoryRuntimeBridge pinned to Chicory 1.7.5. Bundle validation, lifecycle types, and the no-sidecar Compose reference-app integration have all landed — and the package is published on Maven Central as com.traverse-framework:traverse-embedder (0.14.0, lockstep with the core release). Like every host, it's pre-1.0 and not Certified under Spec 529 yet. That published 0.14.0 AAR does not include signed exact-ref execute. ExactModelHost is on traverse main (#1580, closed) and reaches Maven Central only with the next package cut (#1651).
@@ -89,7 +89,7 @@ const _body = `
.NET / WinUI
In progress
- packages/dotnet/TraverseEmbedder has a working WasmtimeRuntimeBridge pinned to Wasmtime .NET 44.0.0. Request marshalling, event subscriptions, evidence publication, the shared conformance suite, and the no-sidecar WinUI reference-app integration have all landed — and the package is published on nuget.org as TraverseEmbedder (0.14.0, lockstep with the core release). Like every host, it's pre-1.0 and not Certified under Spec 529 yet.
+ packages/dotnet/TraverseEmbedder has a working WasmtimeRuntimeBridge pinned to Wasmtime .NET 44.0.0. Request marshalling, event subscriptions, evidence publication, the shared conformance suite, and the no-sidecar WinUI reference-app integration have all landed — and the package is published on nuget.org as TraverseEmbedder (0.14.0, lockstep with the core release). Like every host, it's pre-1.0 and not Certified under Spec 529 yet. That published 0.14.0 package does not include signed exact-ref execute. ExactModelHost is on traverse main (#1602, closed) and reaches nuget.org only with the next package cut (#1651).
diff --git a/src/pages/questions/can-kotlin-or-dotnet-embedders-run-exact-ref-yet.astro b/src/pages/questions/can-kotlin-or-dotnet-embedders-run-exact-ref-yet.astro
index 2c960b7..206247d 100644
--- a/src/pages/questions/can-kotlin-or-dotnet-embedders-run-exact-ref-yet.astro
+++ b/src/pages/questions/can-kotlin-or-dotnet-embedders-run-exact-ref-yet.astro
@@ -9,7 +9,7 @@ const jsonLd = JSON.stringify({
name: 'Can Kotlin or .NET embedders run exact-ref models in Traverse yet?',
acceptedAnswer: {
'@type': 'Answer',
- text: 'No for exact-ref execute. Kotlin (Maven Central com.traverse-framework:traverse-embedder 0.14.0) and .NET (nuget.org TraverseEmbedder 0.14.0) are published packages and do not execute signed exact-ref models yet (#1580 and #1602). Native Rust, web, and Swift ExactModelHost (swift-host-v0.14.0-1) do, as of v0.14.0 / #1579.',
+ text: 'Discover → execute → trace. One shared runtime.wasm. Not from the published 0.14.0 packages. Kotlin ExactModelHost is on traverse main (#1580 closed) but Maven Central com.traverse-framework:traverse-embedder is still 0.14.0. .NET ExactModelHost is on traverse main (#1602 closed) but nuget.org TraverseEmbedder is still 0.14.0. Next package cuts: #1651. Published exact-ref execute is native Rust (v0.14.0), traverse-embedder-web@0.14.0, and Swift ExactModelHost on swift-host-v0.14.0-4.',
},
}],
});
@@ -25,21 +25,22 @@ const relatedLinks = [
---
- Short answer: no for Kotlin and .NET exact-ref execute today. The packages are published — Kotlin com.traverse-framework:traverse-embedder 0.14.0 on Maven Central, .NET TraverseEmbedder 0.14.0 on nuget.org — and they do not have Spec 138 exact-ref parity yet.
+ Short answer: discover → execute → trace, on one shared runtime.wasm. Not from the published packages. Kotlin com.traverse-framework:traverse-embedder 0.14.0 on Maven Central and .NET TraverseEmbedder 0.14.0 on nuget.org do not include exact-ref execute. Both ExactModelHost implementations are on traverse main. The next package cuts are #1651.
- What works instead
- Native Rust and the web embedder execute signed exact-ref in the v0.14.0 cut. Swift ExactModelHost reached parity via swift-host-v0.14.0-1 (#1579) — GitHub Release + SPM binary target, not a CocoaPods claim. Full matrix: Which hosts run signed exact-ref models?.
+ What a published consumer can run
+ Native Rust and the web embedder execute signed exact-ref in the v0.14.0 cut. Swift ExactModelHost is in the published xcframework swift-host-v0.14.0-4, which Package.swift pins (first on swift-host-v0.14.0-1, #1579). Distribution is GitHub Release + SPM binary target, not a CocoaPods claim. Full matrix: Which hosts run signed exact-ref models?.
- Tracked gaps
+ On main, not in the published package
- - Kotlin: #1580
- - .NET: #1602
+ - Kotlin
ExactModelHost: #1580 closed. Maven Central still lists 0.13.0 and 0.14.0. The 0.14.0 AAR was published 2026-09-29, before the host.
+ - .NET
ExactModelHost: #1602 closed. nuget.org still lists 0.13.0 and 0.14.0.
+ - Next cuts for both packages: #1651.
Honest consumers
diff --git a/src/pages/questions/how-do-hosts-trust-signed-models.astro b/src/pages/questions/how-do-hosts-trust-signed-models.astro
index 22d782a..a72e07b 100644
--- a/src/pages/questions/how-do-hosts-trust-signed-models.astro
+++ b/src/pages/questions/how-do-hosts-trust-signed-models.astro
@@ -9,7 +9,7 @@ const jsonLd = JSON.stringify({
name: 'How do hosts trust signed models in Traverse?',
acceptedAnswer: {
'@type': 'Answer',
- text: 'As of Traverse v0.14.0 (signed Spec 138), model packages use schema 2.0.0 manifests plus a detached Ed25519 model.sig.json. Host-owned trust roots gate register_package / registerPackage; apps never add trust. Pin by digest and signature, never a naked URL. The first trained package digits-mlp-1.0.0 ships with a test-only key; production signing is #1567. Exact-ref execute is native Rust, web, and Swift ExactModelHost (swift-host-v0.14.0-1); Kotlin and .NET do not execute exact-ref yet. ONNX as a generic runner is not shipped.',
+ text: 'Discover → execute → trace. One shared runtime.wasm. As of Traverse v0.14.0 (signed Spec 138), model packages use schema 2.0.0 manifests plus a detached Ed25519 model.sig.json. Host-owned trust roots gate register_package / registerPackage; apps never add trust. Pin by digest and signature, never a naked URL. The first trained package digits-mlp-1.0.0 ships with a test-only key; production signing is #1567. Published exact-ref execute is native Rust, web, and Swift ExactModelHost (swift-host-v0.14.0-4). Kotlin and .NET ExactModelHost are on traverse main and are not in the published 0.14.0 packages (#1651). ONNX as a generic runner is not shipped.',
},
}],
});
@@ -28,7 +28,7 @@ const relatedLinks = [
---
The first trained package digits-mlp-1.0.0 is signed with a test-only key so CI and demos can exercise the path. Production model signing is tracked separately as #1567. Do not treat the test key as a production trust root.
Host honesty
- Exact-ref execute is implemented on native Rust, the web embedder, and Swift ExactModelHost (xcframework swift-host-v0.14.0-1 + Package.swift pin). Kotlin and .NET do not execute exact-ref yet — check Platforms. This page is about signed-model trust for Spec 138 exact-ref; it does not claim a generic ONNX runner is shipped. Deeper loop: What is exact-ref model execution?
+ Discover → execute → trace, on one shared runtime.wasm. Published exact-ref execute is native Rust, the web embedder, and Swift ExactModelHost (xcframework swift-host-v0.14.0-4 + Package.swift pin). Kotlin and .NET ExactModelHost are on traverse main and are not in the published 0.14.0 packages (#1651) — check Platforms. This page is about signed-model trust for Spec 138 exact-ref; it does not claim a generic ONNX runner is shipped. Deeper loop: What is exact-ref model execution?
diff --git a/src/pages/questions/what-does-traverse-not-claim-yet.astro b/src/pages/questions/what-does-traverse-not-claim-yet.astro
index 6a72216..3ba4e4b 100644
--- a/src/pages/questions/what-does-traverse-not-claim-yet.astro
+++ b/src/pages/questions/what-does-traverse-not-claim-yet.astro
@@ -9,7 +9,7 @@ const jsonLd = JSON.stringify({
name: 'What does Traverse not claim yet?',
acceptedAnswer: {
'@type': 'Answer',
- text: 'Traverse does not claim a Python SDK; that Swift/Kotlin/.NET hosts are Certified; that Kotlin or .NET execute exact-ref yet; that it is a general agent-orchestration framework or web framework; cloud placement as a v0.1 goal; invented customers or production SLAs; or that approved-spec counts are the product pitch. Swift, Kotlin, and .NET packages are published and pre-1.0. Shipped consumers today are JS/TS and Rust embedders plus MCP; Python is CLI-only; check platforms.html and what-is-real-today.html before assuming a host.',
+ text: 'Traverse does not claim a Python SDK; that Swift/Kotlin/.NET hosts are Certified; that the published Kotlin or .NET 0.14.0 packages execute exact-ref (both ExactModelHost types are on main; package cuts are #1651); that it is a general agent-orchestration framework or web framework; cloud placement as a v0.1 goal; invented customers or production SLAs; or that approved-spec counts are the product pitch. Discover → execute → trace. One shared runtime.wasm. Swift ExactModelHost is published on swift-host-v0.14.0-4. Swift, Kotlin, and .NET packages are published and pre-1.0. Shipped consumers today are JS/TS and Rust embedders plus MCP; Python is CLI-only; check platforms.html and what-is-real-today.html before assuming a host.',
},
}],
});
@@ -37,7 +37,7 @@ const relatedLinks = [
Consumers and packages
- No Python SDK. Python shells out to
traverse-cli capability-package execute. See Does Traverse have a Python SDK?.
- - Swift / Kotlin / .NET packages are published and pre-1.0 (Swift xcframework on
swift-host-v* tags, Kotlin com.traverse-framework:traverse-embedder 0.14.0 on Maven Central, .NET TraverseEmbedder 0.14.0 on nuget.org). They are marked In progress. No host is Certified. Kotlin and .NET do not execute exact-ref yet.
+ - Swift / Kotlin / .NET packages are published and pre-1.0 (Swift xcframework on
swift-host-v* tags, currently swift-host-v0.14.0-4, Kotlin com.traverse-framework:traverse-embedder 0.14.0 on Maven Central, .NET TraverseEmbedder 0.14.0 on nuget.org). They are marked In progress. No host is Certified. Swift ExactModelHost on that xcframework executes exact-ref. Kotlin and .NET ExactModelHost are on traverse main and are not in those 0.14.0 packages (#1651).
- Edge is planned; cloud placement is an explicit non-goal for v0.1.
diff --git a/src/pages/questions/what-is-digits-mlp.astro b/src/pages/questions/what-is-digits-mlp.astro
index 703eadf..cdd3789 100644
--- a/src/pages/questions/what-is-digits-mlp.astro
+++ b/src/pages/questions/what-is-digits-mlp.astro
@@ -36,7 +36,7 @@ const relatedLinks = [
A 64→32→10 multilayer perceptron trained on the UCI Optical Recognition of Handwritten Digits dataset (CC BY 4.0). Held-out accuracy is 96.10%. The guest runs bit-identically in the trainer, on the native host, and in the browser embedder — same pinned bytes, same scores.
How it fits the product
- Exact-ref means the app pins the package by digest and signature and calls governed model.execute — never a naked URL. See What is exact-ref model execution?. Hosts that execute that path today: native Rust, web, and Swift ExactModelHost (swift-host-v0.14.0-1). Kotlin and .NET do not execute exact-ref yet.
+ Exact-ref means the app pins the package by digest and signature and calls governed model.execute — never a naked URL. Discover → execute → trace, on one shared runtime.wasm. See What is exact-ref model execution?. Published hosts that execute that path: native Rust, web, and Swift ExactModelHost (swift-host-v0.14.0-4). Kotlin and .NET ExactModelHost are on traverse main and are not in the published 0.14.0 packages.
Honest limits
diff --git a/src/pages/questions/what-is-exact-ref-model-execution.astro b/src/pages/questions/what-is-exact-ref-model-execution.astro
index cce8e03..d73c1fe 100644
--- a/src/pages/questions/what-is-exact-ref-model-execution.astro
+++ b/src/pages/questions/what-is-exact-ref-model-execution.astro
@@ -9,7 +9,7 @@ const jsonLd = JSON.stringify({
name: 'What is exact-ref model execution in Traverse?',
acceptedAnswer: {
'@type': 'Answer',
- text: 'Exact-ref model execution is how Traverse runs a WASM model package that an app has pinned by digest and signature — never by a naked URL. Hosts call the Spec 137 model.execute surface with opaque input_ref / output_ref handles. As of Traverse v0.14.0, packages use schema 2.0.0 manifests plus a detached Ed25519 model.sig.json; host-owned trust roots gate register_package; the first trained digits-mlp-1.0.0 ships signed with a test-only key (production signing is separate). Exact-ref execute is implemented on native Rust, web, and Swift ExactModelHost (Package.swift pin to swift-host-v0.14.0-1); Kotlin and .NET do not execute exact-ref yet. First landed in v0.12.0; Swift parity closed #1579 on 2026-09-30.',
+ text: 'Exact-ref model execution is how Traverse runs a WASM model package that an app has pinned by digest and signature — never by a naked URL. Discover → execute → trace. One shared runtime.wasm; embedders are clients. Hosts call the Spec 137 model.execute surface with opaque input_ref / output_ref handles. As of Traverse v0.14.0, packages use schema 2.0.0 manifests plus a detached Ed25519 model.sig.json; host-owned trust roots gate register_package; the first trained digits-mlp-1.0.0 ships signed with a test-only key (production signing is separate). Published exact-ref execute: native Rust, web, and Swift ExactModelHost (Package.swift pin to swift-host-v0.14.0-4). Kotlin and .NET ExactModelHost are on traverse main and are not in the published 0.14.0 packages (#1651). First landed in v0.12.0; Swift parity closed #1579 on 2026-09-30.',
},
}],
});
@@ -31,7 +31,7 @@ const relatedLinks = [
---
What landed in v0.14.0
Spec 138 first shipped in v0.12.0 (see the historical v0.12.0 write-up). v0.14.0 adds signed packages, host-owned trust, machine-readable rights, and the first trained model digits-mlp-1.0.0 (64→32→10 MLP on UCI digits, CC BY 4.0, 96.10% held-out, bit-identical trainer / native / browser). That package is signed with the test-only key; production model signing is #1567.
- Host honesty: exact-ref execute is implemented in the Rust native runtime, the web embedder, and Swift ExactModelHost (published xcframework swift-host-v0.14.0-1; Package.swift binary pin; digits conformance byte-identical). Kotlin and .NET do not execute exact-ref yet. Pin the Traverse crates and npm at 0.14.0. That release still pins traverse-registry at =0.25.0; crates.io has since published traverse-registry 0.27.0.
+ Host honesty: discover → execute → trace, on one shared runtime.wasm. Published exact-ref execute is the Rust native runtime, the web embedder, and Swift ExactModelHost (published xcframework swift-host-v0.14.0-4; Package.swift binary pin). Kotlin ExactModelHost is on traverse main (#1580, closed) and is not in Maven Central com.traverse-framework:traverse-embedder 0.14.0. .NET ExactModelHost is on traverse main (#1602, closed) and is not in nuget.org TraverseEmbedder 0.14.0. Next package cuts: #1651. Pin the Traverse crates and npm at 0.14.0. That release still pins traverse-registry at =0.25.0; crates.io has since published traverse-registry 0.27.0.
What it is not
- It is not “the model is in charge.” It is not Spec 045. It is not a guest model_invoke import — that stays out of scope for Spec 138 v1. And it is not permission to treat a URL as a model identity, or to assume Kotlin/.NET already execute exact-ref.
+ It is not “the model is in charge.” It is not Spec 045. It is not a guest model_invoke import — that stays out of scope for Spec 138 v1. And it is not permission to treat a URL as a model identity, or to assume the published Kotlin or .NET 0.14.0 packages already execute exact-ref.
diff --git a/src/pages/questions/which-hosts-run-signed-exact-ref-models.astro b/src/pages/questions/which-hosts-run-signed-exact-ref-models.astro
index d343a70..1fd7a54 100644
--- a/src/pages/questions/which-hosts-run-signed-exact-ref-models.astro
+++ b/src/pages/questions/which-hosts-run-signed-exact-ref-models.astro
@@ -9,7 +9,7 @@ const jsonLd = JSON.stringify({
name: 'Which hosts run signed exact-ref models in Traverse?',
acceptedAnswer: {
'@type': 'Answer',
- text: 'As of Traverse v0.14.0 and swift-host-v0.14.0-1: native Rust, the web embedder, and Swift ExactModelHost execute signed exact-ref models (Spec 138). Kotlin and .NET embedders do not execute exact-ref yet (tracked #1580 and #1602). digits-mlp-1.0.0 uses a test-only signing key; production custody is #1567. No generic ONNX runner is shipped. One shared runtime.wasm; embedders are clients.',
+ text: 'Discover → execute → trace. One shared runtime.wasm; embedders are clients. Published exact-ref execute: native Rust in the v0.14.0 crates, traverse-embedder-web@0.14.0, and Swift ExactModelHost on the published xcframework swift-host-v0.14.0-4 (Package.swift binary pin; GitHub Release + SPM, not CocoaPods). Kotlin ExactModelHost is on traverse main (#1580 closed) but Maven Central com.traverse-framework:traverse-embedder is still 0.14.0, which does not include it. .NET ExactModelHost is on traverse main (#1602 closed) but nuget.org TraverseEmbedder is still 0.14.0, which does not include it. Next package cuts: #1651. digits-mlp-1.0.0 uses a test-only key; production custody is #1567. No generic ONNX runner.',
},
}],
});
@@ -26,21 +26,22 @@ const relatedLinks = [
---
- Short answer: native Rust, web (traverse-embedder-web), and Swift ExactModelHost execute signed exact-ref models today. Kotlin and .NET do not — yet. Pin by digest and signature; never treat a naked URL as identity.
+ Short answer: discover → execute → trace, on one shared runtime.wasm. Published exact-ref execute is native Rust, the web embedder, and Swift ExactModelHost. Kotlin and .NET ExactModelHost are on traverse main and are not in the published 0.14.0 packages, so Maven Central and nuget.org still cannot run exact-ref. Pin by digest and signature; never treat a naked URL as identity.
- Honest matrix (v0.14.0 / swift-host-v0.14.0-1)
+ Honest matrix (checked 9 October 2026)
- - Native Rust — exact-ref execute shipped in the v0.14.0 product cut.
- - Web —
traverse-embedder-web@0.14.0 executes exact-ref.
- - Swift —
ExactModelHost via published xcframework swift-host-v0.14.0-1 and in-repo Package.swift binary pin (#1579). Distribution is GitHub Release + SPM binary target — not a CocoaPods / Swift Package Index first-class package claim.
- - Kotlin — published
com.traverse-framework:traverse-embedder 0.14.0 on Maven Central; no exact-ref execute yet (#1580).
- - .NET — published
TraverseEmbedder 0.14.0 on nuget.org; no exact-ref execute yet (#1602).
+ - Native Rust — exact-ref execute shipped in the v0.14.0 product cut (
ExactModelHostConnector).
+ - Web — published
traverse-embedder-web@0.14.0 executes exact-ref (ExactModelBrowserHost).
+ - Swift —
ExactModelHost is in the published xcframework swift-host-v0.14.0-4, which Package.swift pins. The first ExactModelHost xcframework was swift-host-v0.14.0-1 (#1579). Distribution is GitHub Release + SPM binary target — not a CocoaPods / Swift Package Index package.
+ - Kotlin —
ExactModelHost is on traverse main (#1580, closed). Maven Central com.traverse-framework:traverse-embedder is still 0.14.0 (0.13.0 and 0.14.0 only; 0.14.0 published 2026-09-29, before the host). That package does not execute exact-ref.
+ - .NET —
ExactModelHost is on traverse main (#1602, closed). nuget.org TraverseEmbedder is still 0.14.0 (0.13.0 and 0.14.0 only). That package does not execute exact-ref.
+ - Next package cuts — #1651. Until those publish, resolving the 0.14.0 Kotlin or .NET package does not run exact-ref.
Signing honesty