docs(site): Fri SEO Q&As — embedder pin, I/O boundary, digits-mlp

public/llms.txt

@@ -16,6 +16,7 @@ Current packages: crates.io at 0.14.0 (pin `traverse-registry` at `=0.25.0` if y
 - [What is real today](https://traverse-framework.com/what-is-real-today.html): citeable snapshot — skill-first, one shared `runtime.wasm`, honest consumers, pre-1.0, no invented customers.
 - [What does discover → execute → trace mean?](https://traverse-framework.com/questions/what-does-discover-execute-trace-mean.html): the value loop in plain language — agent proposes, runtime decides.
 - [Where does business logic live?](https://traverse-framework.com/questions/where-does-business-logic-live-in-traverse.html): capabilities = non-UI domain rules; hosts = UI + I/O; one concern per package; “apps not ready” ≠ leave logic in the host; utilities teach the pipe, not the ceiling. Narrative: [Where business logic lives (hosts stay thin)](https://traverse-framework.com/blog/where-business-logic-lives.html).
+- [What I/O boundary do capabilities use today?](https://traverse-framework.com/questions/what-io-boundary-do-capabilities-use-today.html): stdin/stdout JSON through the host; no ambient filesystem; hosts stay thin; discover → execute → trace.
 - [What does “apps are not ready” mean?](https://traverse-framework.com/questions/what-does-apps-not-ready-mean.html) · [Is Traverse only for tiny utilities?](https://traverse-framework.com/questions/is-traverse-only-for-tiny-utilities.html): help-wanted door phrase (no product-shell PRs); utilities teach the pipe, not a size ceiling; domain packs in scope.
 - [What is the print-support capability pack?](https://traverse-framework.com/questions/what-is-the-print-support-capability-pack.html): living domain pack (registry#596 · #597–#604 · Discussion #1540); apps-not-ready ≠ no packs; none of the print.* capabilities published yet. Narrative: [Domain packs are in scope: print-support](https://traverse-framework.com/blog/print-support-domain-pack.html).
 - [What does “the agent proposes; the runtime decides” mean?](https://traverse-framework.com/questions/what-does-agent-proposes-runtime-decides-mean.html): boundary in one page — agents search/plan/suggest; runtime validates, executes or denies, leaves a trace.
@@ -62,6 +63,8 @@ Current packages: crates.io at 0.14.0 (pin `traverse-registry` at `=0.25.0` if y
 - [What is exact-ref model execution?](https://traverse-framework.com/questions/what-is-exact-ref-model-execution.html): signed schema `2.0.0` + `model.sig.json`; host-owned trust; `digits-mlp-1.0.0` (test-only key; prod signing #1567); native+web+Swift ExactModelHost execute (swift-host-v0.14.0-1 / #1579); Kotlin/.NET not yet (first landed in v0.12.0). Embedder notes: [v0.14.0: what changed for embedders](https://traverse-framework.com/blog/traverse-0-14-0-what-changed-for-embedders.html) · [Release](https://github.com/traverse-framework/traverse/releases/tag/v0.14.0) · [Announcement #1576](https://github.com/orgs/traverse-framework/discussions/1576).
 - [How do hosts trust signed models?](https://traverse-framework.com/questions/how-do-hosts-trust-signed-models.html): host-owned trust roots gate `register_package`; pin by digest + `model.sig.json`; test-only digits-mlp key; exact-ref execute native+web+Swift ExactModelHost; Kotlin/.NET not yet — no claimed ONNX generic runner.
 - [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): honest matrix (native+web+Swift ExactModelHost; Kotlin/.NET #1580/#1602); test-only key ≠ prod (#1567).
+- [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 currently pins `^0.13.0` while npm ships `0.14.0`; `/discover` still uses `insertVerified`; 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.
 
 ## Optional

src/pages/questions/can-traverse-capabilities-call-native-os-apis.astro

@@ -16,6 +16,7 @@ const jsonLd = JSON.stringify({
 
 const relatedLinks = [
   { href: '/questions/what-is-the-wasm-sandbox.html', label: 'What is the WASM sandbox?' },
+  { href: '/questions/what-io-boundary-do-capabilities-use-today.html', label: 'What I/O boundary do capabilities use today?' },
   { href: '/questions/what-is-a-contract-in-traverse.html', label: 'What is a contract in Traverse?' },
   { href: '/questions/what-framework-runs-business-logic-on-any-os.html', label: 'What framework lets me write business logic once and run it on any OS?' },
   { href: '/questions/what-is-traverse-security-model.html', label: "What is Traverse's security model?" },

src/pages/questions/does-the-website-use-the-latest-traverse-embedder.astro

@@ -0,0 +1,46 @@
+---
+import QuestionLayout from '@layouts/QuestionLayout.astro';
+
+const jsonLd = JSON.stringify({
+  '@context': 'https://schema.org',
+  '@type': 'FAQPage',
+  mainEntity: [{
+    '@type': 'Question',
+    name: 'Does the Traverse website use the latest traverse-embedder-web?',
+    acceptedAnswer: {
+      '@type': 'Answer',
+      text: 'Not always. The public website currently pins traverse-embedder-web at ^0.13.0 while npm publishes 0.14.0 with Traverse v0.14.0. The /discover generate panel still calls ExactModelBrowserHost.insertVerified (the 0.13 API); 0.14 replaced that with registerPackage(manifestBytes, wasm, signatureBytes) for signed Spec 138 packages. Treat published npm/crates versions and what-is-real-today as the product line — do not assume the website pin equals the latest shipped embedder.',
+    },
+  }],
+});
+
+const relatedLinks = [
+  { href: '/questions/what-does-the-discover-page-do.html', label: 'What does the /discover page do?' },
+  { href: '/what-is-real-today.html', label: 'What is real today' },
+  { href: '/questions/what-is-exact-ref-model-execution.html', label: 'What is exact-ref model execution?' },
+  { href: '/blog/traverse-0-14-0-what-changed-for-embedders.html', label: 'v0.14.0: what changed for embedders' },
+  { href: '/questions/how-do-i-embed-traverse-in-a-web-app.html', label: 'How do I embed Traverse in a web app?' },
+];
+---
+<QuestionLayout
+  title="Does the Traverse website use the latest traverse-embedder-web?"
+  description="Not always — the site currently pins ^0.13.0 while npm ships 0.14.0. /discover still uses insertVerified; 0.14 uses registerPackage. Pin published packages, not the website demo."
+  canonical="https://traverse-framework.com/questions/does-the-website-use-the-latest-traverse-embedder.html"
+  category="Runtime and architecture"
+  relatedLinks={relatedLinks}
+  jsonLd={jsonLd}
+>
+  <p><strong>Short answer:</strong> <strong>not always.</strong> The marketing site can lag the published package line. That is honesty, not a secret second runtime.</p>
+
+  <h2>What is pinned today</h2>
+  <p>On <code>traverse-framework/website</code> main, <code>package.json</code> depends on <code>traverse-embedder-web</code> at <code>^0.13.0</code>. npm’s current published line for that package is <strong>0.14.0</strong>, lockstep with <a href="https://github.com/traverse-framework/traverse/releases/tag/v0.14.0">Traverse v0.14.0</a> crates. Cite <a href="/what-is-real-today.html">what is real today</a> for the consumer list apps should build against.</p>
+
+  <h2>Why /discover can lag</h2>
+  <p>The public <a href="/discover.html">/discover</a> generate panel (<code>discover-generate.js</code>) still constructs an <code>ExactModelBrowserHost</code> and calls <strong><code>insertVerified(...)</code></strong> — the <strong>0.13</strong> admission path. In <strong>0.14</strong>, that host admits packages through <strong><code>registerPackage(manifestBytes, wasm, signatureBytes)</code></strong> so signed Spec 138 manifests and <code>model.sig.json</code> are verified before execute. Migrating the demo is separate eng work; until it lands, the site pin stays on 0.13 so the demo keeps working.</p>
+
+  <h2>What you should pin</h2>
+  <p>If you are building a product host, depend on the <strong>published</strong> npm / crates.io versions (today <code>traverse-embedder-web@0.14.0</code> / <code>traverse-embedder@0.14.0</code>), not on whatever the website happens to ship in its demo bundle. The site is a citeable demo surface; it is not the version authority for your app.</p>
+
+  <h2>Related</h2>
+  <p>What the page is for: <a href="/questions/what-does-the-discover-page-do.html">What does the /discover page do?</a>. Signed exact-ref surface: <a href="/questions/what-is-exact-ref-model-execution.html">What is exact-ref model execution?</a>. Embedder delta notes: <a href="/blog/traverse-0-14-0-what-changed-for-embedders.html">v0.14.0: what changed for embedders</a>.</p>
+</QuestionLayout>

src/pages/questions/index.astro

@@ -59,6 +59,9 @@ const groups = [
       ['which-hosts-run-signed-exact-ref-models.html', 'Which hosts run signed exact-ref models?'],
       ['is-production-model-signing-ready.html', 'Is production model signing ready?'],
       ['can-kotlin-or-dotnet-embedders-run-exact-ref-yet.html', 'Can Kotlin or .NET embedders run exact-ref yet?'],
+      ['what-is-digits-mlp.html', 'What is digits-mlp in Traverse?'],
+      ['does-the-website-use-the-latest-traverse-embedder.html', 'Does the website use the latest traverse-embedder-web?'],
+      ['what-io-boundary-do-capabilities-use-today.html', 'What I/O boundary do capabilities use today?'],
       ['what-does-the-discover-page-do.html', 'What does the Traverse /discover page do?'],
       ['how-do-placement-targets-work.html', 'How do placement targets work in Traverse?'],
       ['what-is-a-trace-artifact.html', 'What is a trace artifact in Traverse?'],

src/pages/questions/is-production-model-signing-ready.astro

@@ -18,6 +18,7 @@ const relatedLinks = [
   { href: '/questions/how-do-hosts-trust-signed-models.html', label: 'How do hosts trust signed models?' },
   { href: '/questions/which-hosts-run-signed-exact-ref-models.html', label: 'Which hosts run signed exact-ref models?' },
   { href: '/questions/what-is-exact-ref-model-execution.html', label: 'What is exact-ref model execution?' },
+  { href: '/questions/what-is-digits-mlp.html', label: 'What is digits-mlp?' },
   { href: '/questions/how-do-i-verify-a-signed-capability-artifact.html', label: 'How do I verify a signed capability artifact?' },
   { href: '/blog/traverse-0-14-0-what-changed-for-embedders.html', label: 'v0.14.0: what changed for embedders' },
 ];

src/pages/questions/what-does-the-discover-page-do.astro

@@ -3,6 +3,7 @@ import QuestionLayout from '@layouts/QuestionLayout.astro';
 
 const relatedLinks = [
   { href: '/blog/what-discover-proves.html', label: "What /discover proves — and what it doesn't" },
+  { href: '/questions/does-the-website-use-the-latest-traverse-embedder.html', label: 'Does the website use the latest embedder?' },
   { href: '/questions/what-is-governed-composition.html', label: 'What is governed composition?' },
   { href: '/questions/what-is-the-difference-between-an-ai-agent-and-the-traverse-runtime.html', label: 'Agent vs Traverse runtime' },
   { href: '/questions/how-do-ai-agents-discover-capabilities.html', label: 'How do AI agents discover capabilities?' },

src/pages/questions/what-io-boundary-do-capabilities-use-today.astro

@@ -0,0 +1,51 @@
+---
+import QuestionLayout from '@layouts/QuestionLayout.astro';
+
+const jsonLd = JSON.stringify({
+  '@context': 'https://schema.org',
+  '@type': 'FAQPage',
+  mainEntity: [{
+    '@type': 'Question',
+    name: 'What I/O boundary do Traverse capabilities use today?',
+    acceptedAnswer: {
+      '@type': 'Answer',
+      text: 'Today Traverse capabilities exchange structured input and output as stdin/stdout JSON through the host. There is no ambient filesystem inside the capability. Non-UI business logic stays in the WASM capability under discover → execute → trace; hosts and embedders supply UI and I/O only. Declared host calls may exist when a contract names them, but ambient WASI filesystem access is not the current shipped boundary.',
+    },
+  }],
+});
+
+const relatedLinks = [
+  { href: '/questions/where-does-business-logic-live-in-traverse.html', label: 'Where does business logic live?' },
+  { href: '/questions/can-traverse-capabilities-call-native-os-apis.html', label: 'Can capabilities call native OS APIs?' },
+  { href: '/questions/what-is-the-wasm-sandbox.html', label: 'What is the WASM sandbox?' },
+  { href: '/questions/what-does-discover-execute-trace-mean.html', label: 'What does discover → execute → trace mean?' },
+  { href: '/questions/what-is-the-print-support-capability-pack.html', label: 'What is the print-support capability pack?' },
+  { href: '/blog/where-business-logic-lives.html', label: 'Where business logic lives (hosts stay thin)' },
+];
+---
+<QuestionLayout
+  title="What I/O boundary do Traverse capabilities use today?"
+  description="stdin/stdout JSON through the host — no ambient filesystem. Capabilities hold non-UI logic under discover → execute → trace; hosts supply UI and I/O only."
+  canonical="https://traverse-framework.com/questions/what-io-boundary-do-capabilities-use-today.html"
+  category="Runtime and architecture"
+  relatedLinks={relatedLinks}
+  jsonLd={jsonLd}
+>
+  <p><strong>Short answer:</strong> capabilities talk to the outside world as <strong>stdin/stdout JSON</strong> mediated by the host. There is <strong>no ambient filesystem</strong> inside the capability today.</p>
+
+  <h2>Why that shape</h2>
+  <p>Value is still <strong>discover → execute → trace</strong>. The capability owns non-UI business rules — pricing, eligibility, codecs, scorers, export gates — as a sandboxed WASM artifact with a contract. The host owns UI, session, persistence, and how bytes get into or out of that sandbox. Keeping the default I/O channel narrow is what makes the same package behave the same way on every honest host.</p>
+
+  <h2>What “stdin/stdout JSON” means in practice</h2>
+  <p>Callers (CLI, embedder, MCP façade) stage a JSON payload the contract accepts, run the package, and read a JSON result (or a structured failure) back. Mesh bytes, tables, and other payloads ride inside that governed JSON shape (often structured IR and/or size-capped encodings). Fail closed over documented limits. The traverse repo documents the contract surface in <code>docs/wasm-io-contract.md</code>.</p>
+
+  <h2>What this is not</h2>
+  <ul>
+    <li>Not “the capability can <code>open()</code> arbitrary paths.” Ambient WASI filesystem is <strong>not</strong> the current shipped boundary for registry capabilities.</li>
+    <li>Not “leave domain logic in the host forever.” Hosts stay thin on purpose — see <a href="/questions/where-does-business-logic-live-in-traverse.html">Where does business logic live?</a>.</li>
+    <li>Not a ban on declared host calls. A contract may name a specific host call the host implements; that is still host-owned I/O, not ambient OS reach from inside the guest. See <a href="/questions/can-traverse-capabilities-call-native-os-apis.html">Can capabilities call native OS APIs?</a>.</li>
+  </ul>
+
+  <h2>Living example</h2>
+  <p>The <a href="/questions/what-is-the-print-support-capability-pack.html">print-support capability pack</a> (registry initiative #596; none of the <code>print.*</code> capabilities published yet) uses this same stdin/stdout JSON boundary for mesh codecs, scorers, generators, and export gates. Apps are not the ask — capabilities are.</p>
+</QuestionLayout>

src/pages/questions/what-is-digits-mlp.astro

@@ -0,0 +1,47 @@
+---
+import QuestionLayout from '@layouts/QuestionLayout.astro';
+
+const jsonLd = JSON.stringify({
+  '@context': 'https://schema.org',
+  '@type': 'FAQPage',
+  mainEntity: [{
+    '@type': 'Question',
+    name: 'What is digits-mlp in Traverse?',
+    acceptedAnswer: {
+      '@type': 'Answer',
+      text: 'digits-mlp-1.0.0 is the first trained exact-ref model package shipped with Traverse v0.14.0: a 64→32→10 MLP on the UCI Optical Recognition of Handwritten Digits dataset (CC BY 4.0), scoring 96.10% on the held-out split and bit-identical across trainer, native, and browser hosts. It is signed with a test-only key for CI and demos — not a production trust root, and not a general-purpose LLM.',
+    },
+  }],
+});
+
+const relatedLinks = [
+  { href: '/questions/what-is-exact-ref-model-execution.html', label: 'What is exact-ref model execution?' },
+  { href: '/questions/is-production-model-signing-ready.html', label: 'Is production model signing ready?' },
+  { href: '/questions/which-hosts-run-signed-exact-ref-models.html', label: 'Which hosts run signed exact-ref models?' },
+  { href: '/questions/how-do-hosts-trust-signed-models.html', label: 'How do hosts trust signed models?' },
+  { href: '/blog/traverse-0-14-0-what-changed-for-embedders.html', label: 'v0.14.0: what changed for embedders' },
+];
+---
+<QuestionLayout
+  title="What is digits-mlp in Traverse?"
+  description="digits-mlp-1.0.0 is v0.14.0’s first trained exact-ref model package: a small UCI-digits MLP (96.10% held-out), bit-identical across hosts, signed with a test-only key — not a general LLM."
+  canonical="https://traverse-framework.com/questions/what-is-digits-mlp.html"
+  category="Runtime and architecture"
+  relatedLinks={relatedLinks}
+  jsonLd={jsonLd}
+>
+  <p><strong>Short answer:</strong> <code>digits-mlp-1.0.0</code> is the first <strong>trained</strong> exact-ref model package in <a href="https://github.com/traverse-framework/traverse/releases/tag/v0.14.0">Traverse v0.14.0</a>. It proves the signed Spec 138 path with a real small model — not a chat LLM.</p>
+
+  <h2>What it is</h2>
+  <p>A 64→32→10 multilayer perceptron trained on the UCI Optical Recognition of Handwritten Digits dataset (<strong>CC BY 4.0</strong>). Held-out accuracy is <strong>96.10%</strong>. The guest runs bit-identically in the trainer, on the native host, and in the browser embedder — same pinned bytes, same scores.</p>
+
+  <h2>How it fits the product</h2>
+  <p>Exact-ref means the app pins the package by digest and signature and calls governed <code>model.execute</code> — never a naked URL. See <a href="/questions/what-is-exact-ref-model-execution.html">What is exact-ref model execution?</a>. Hosts that execute that path today: native Rust, web, and Swift <code>ExactModelHost</code> (<code>swift-host-v0.14.0-1</code>). Kotlin and .NET do not execute exact-ref yet.</p>
+
+  <h2>Honest limits</h2>
+  <ul>
+    <li><strong>Test-only signing.</strong> The package is signed so CI and demos can exercise the path. It is <strong>not</strong> a production trust root. Production custody, rotation, and revocation: <a href="https://github.com/traverse-framework/traverse/issues/1567">traverse#1567</a> · <a href="/questions/is-production-model-signing-ready.html">Is production model signing ready?</a>.</li>
+    <li><strong>Not a general LLM.</strong> Fixed digit classification guest. Do not invent tool-use, chat, or Hub-download claims from this package alone.</li>
+    <li><strong>Not “every host.”</strong> Matrix: <a href="/questions/which-hosts-run-signed-exact-ref-models.html">Which hosts run signed exact-ref models?</a>.</li>
+  </ul>
+</QuestionLayout>

src/pages/questions/what-is-exact-ref-model-execution.astro

@@ -16,6 +16,7 @@ const jsonLd = JSON.stringify({
 
 const relatedLinks = [
   { href: '/questions/can-kotlin-or-dotnet-embedders-run-exact-ref-yet.html', label: 'Can Kotlin or .NET run exact-ref yet?' },
+  { href: '/questions/what-is-digits-mlp.html', label: 'What is digits-mlp?' },
   { href: '/questions/is-production-model-signing-ready.html', label: 'Is production model signing ready?' },
   { href: '/questions/which-hosts-run-signed-exact-ref-models.html', label: 'Which hosts run signed exact-ref models?' },
   { href: '/questions/how-do-hosts-trust-signed-models.html', label: 'How do hosts trust signed models?' },