+ Short answer: not in a published release. In Traverse v0.14.0, governed exact-ref models run on the wasm-cpu path inside the one shared runtime. Hardware acceleration is being built on traverse main, and the part that has landed is the policy and evidence layer, not a working GPU or Neural Engine adapter.
+
+ What is on main today (unreleased)
+ As of October 13, 2026, traverse-runtime on main has a generic native accelerator adapter framework (Decision 112, Spec 138 FR-060 to FR-065, traverse#1667). It is not in any published crate or package yet.
+
+ - The host chooses, in policy. The execution policy lists placements in order. An empty list means
wasm-cpu only. An unknown or repeated placement id is policy_denied.
+ - A placement has to earn its turn. The runtime takes the first listed placement that the host supports, that the signed package carries a variant for, that passed its device self-check, that fits the host memory ceiling, and that meets
require_fuel_metering when the host asks for it.
+ - The self-check is real. The variant's conformance vector runs on the device and is compared under the variant's declared tolerance. The result is cached per variant digest, adapter, platform version, and compute units, so an OS update re-runs it. A failed check makes that variant unavailable.
+ - It fails closed. If nothing qualifies, the call fails with
placement_unavailable before the input is consumed. A late adapter result after cancel or deadline is discarded.
+ - The trace says where it ran. Every result carries placement evidence: the placement, the compute units, and whether fuel metering applied.
+
+
+ What is not done yet
+ No real accelerator adapter has landed. The first one planned is Core ML on Apple devices, called from Rust. An earlier converter wrapped ONNX in a way Core ML could only run on the CPU, so it is being replaced through a spike-gated ONNX to Core ML route (#1663), with on-device iPhone timing evidence tracked in #1630. There is no GPU adapter for the web, Android, or desktop, and no date for one.
+
+ Why it is built this way
+ An accelerator is an implementation detail of the host, not a second runtime. The contract, the signed package, and discover → execute → trace stay the same. The adapter only runs a variant the package already signed, only after it matched the wasm-cpu reference on that device, and the trace records which path produced the answer. An agent or app can ask for speed, but the runtime decides whether the faster path is trustworthy on this hardware.
+
+ This is a different thing from capability placement targets (local, browser, and so on), which decide where a capability can be placed. Model placements decide which compute path runs a signed model inside a host.
+
diff --git a/src/pages/questions/index.astro b/src/pages/questions/index.astro
index a1920b1..51ab71c 100644
--- a/src/pages/questions/index.astro
+++ b/src/pages/questions/index.astro
@@ -58,6 +58,7 @@ const groups = [
['what-is-one-shared-runtime-wasm.html', 'What is one shared runtime.wasm in Traverse?'],
['does-the-rust-embedder-use-the-same-runtime-wasm.html', 'Does the Rust embedder use the same runtime.wasm?'],
['what-is-exact-model-host.html', 'What is ExactModelHost?'],
+ ['can-traverse-run-models-on-a-gpu-or-neural-engine.html', 'Can Traverse run models on a GPU or the Apple Neural Engine?'],
['how-does-traverse-execute-wasm.html', 'How does Traverse execute WASM?'],
['can-traverse-run-without-wasm.html', 'Can Traverse run without WASM?'],
['what-is-the-capability-registry.html', 'What is the capability registry?'],
diff --git a/src/pages/questions/what-is-exact-model-host.astro b/src/pages/questions/what-is-exact-model-host.astro
index 986c9d0..b9cdd0b 100644
--- a/src/pages/questions/what-is-exact-model-host.astro
+++ b/src/pages/questions/what-is-exact-model-host.astro
@@ -20,6 +20,7 @@ const relatedLinks = [
{ href: '/questions/how-do-hosts-trust-signed-models.html', label: 'How do hosts trust signed models?' },
{ href: '/questions/is-production-model-signing-ready.html', label: 'Is production model signing ready?' },
{ href: '/questions/can-kotlin-or-dotnet-embedders-run-exact-ref-yet.html', label: 'Can Kotlin or .NET run exact-ref yet?' },
+ { href: '/questions/can-traverse-run-models-on-a-gpu-or-neural-engine.html', label: 'Can Traverse run models on a GPU or Neural Engine?' },
];
---