From 31b2542502a8eeadc3b7677f6f5fc9130d06aa38 Mon Sep 17 00:00:00 2001 From: Enrico Piovesan Date: Fri, 21 Aug 2026 21:59:12 -0600 Subject: [PATCH 1/2] feat: link the discover demo from global nav, footer, and homepage The live workflow-discovery page was only reachable from the Registry and Agents CTAs. Add it to the top-level nav (desktop + mobile), the footer's Product column, and a new homepage CTA band pointing at it. Co-Authored-By: Claude Sonnet 5 --- src/components/Footer.astro | 1 + src/components/Nav.astro | 2 ++ src/pages/index.astro | 2 +- 3 files changed, 4 insertions(+), 1 deletion(-) diff --git a/src/components/Footer.astro b/src/components/Footer.astro index 6332695..41b3216 100644 --- a/src/components/Footer.astro +++ b/src/components/Footer.astro @@ -26,6 +26,7 @@
  • Platforms
  • The System
  • Registry
    • +
  • Discover
  • Compare
  • Changelog
  • Roadmap
    • diff --git a/src/components/Nav.astro b/src/components/Nav.astro index 9f5f394..f643362 100644 --- a/src/components/Nav.astro +++ b/src/components/Nav.astro @@ -70,6 +70,7 @@ const { currentPath = '' } = Astro.props;
  • Platforms
  • Agents
  • Registry
    • +
  • Discover
  • @@ -164,6 +165,7 @@ const { currentPath = '' } = Astro.props; Platforms Agents Registry + Discover Quickstart Docs All Questions diff --git a/src/pages/index.astro b/src/pages/index.astro index fc3266f..a419128 100644 --- a/src/pages/index.astro +++ b/src/pages/index.astro @@ -1,7 +1,7 @@ --- import BaseLayout from '@layouts/BaseLayout.astro'; -const _body = "\n
    \n
    \n
    \n
    \n \n v0.8.1 · Apache 2.0 · Open source\n
    \n

    \n Define once.
    Run anywhere.\n

    \n

    \n Traverse is a contract-driven WASM runtime. Write business logic once with a machine-readable contract, run it natively or in the browser today, and let AI agents call it safely over MCP.\n

    \n
    \n Get started →\n Read the docs\n
    \n
    \n
    \n\n\n
    \n
    \n
    \n \n
    \n
    \n
    \n
    \n pricing.toml\n
    \n
    \n 
    [capability]\nname    = \"calculate-price\"\nversion = \"1.2.0\"\nwasm    = \"pricing.wasm\"\n\n[governing_spec]\ntitle   = \"Pricing Policy v3\"\nsource  = \"docs/pricing-policy.md\"\n\n[input]\ntype = \"object\"\nproperties.sku      = \"string\"\nproperties.quantity = \"integer\"\nproperties.region   = \"string\"\nrequired = [\"sku\", \"quantity\"]\n\n[output]\ntype = \"object\"\nproperties.total    = \"number\"\nproperties.currency = \"string\"\nrequired = [\"total\", \"currency\"]
    \n
    \n
    \n
    \n
    \n
    \n
    \n terminal\n
    \n
    \n
    $traverse run pricing --input '{\"sku\":\"PRO\",\"quantity\":5}'
    \n
    ✓ Contract validated
    \n
    ✓ WASM executed (2.1ms)
    \n
    → {\"total\": 249.95, \"currency\": \"USD\"}
    \n
    \n
    \n
    \n
    \n\n \n
    \n
    How Traverse works
    \n

    \n Write a contract.
    Ship a capability.\n

    \n

    \n Three steps from idea to a portable, contract-governed piece of business logic running in any environment.\n

    \n
    \n
    \n
    01
    \n
    \n

    Define the contract

    \n

    Write a TOML file with your capability name, the WASM binary path, and JSON Schema definitions for inputs and outputs. Link it to the governing spec document your team actually works from.

    \n
    \n
    \n
    \n
    02
    \n
    \n

    Compile to WASM

    \n

    Implement the logic in Rust and compile to wasm32-wasi. The same binary runs on every placement target without recompilation.

    \n
    \n
    \n
    \n
    03
    \n
    \n

    Register and run

    \n

    Add the capability to the registry with traverse add. Call it from the CLI, from an AI agent via MCP, or from your app directly. Every call is validated and traced.

    \n
    \n
    \n
    \n
    \n
    \n
    \n
    \n\n\n
    \n
    \n
    \n
    Features
    \n

    Everything business logic needs

    \n

    From contract validation to AI agent discovery, Traverse handles the entire lifecycle.

    \n
    \n
    \n
    \n
    \n \n
    \n

    Contract-first validation

    \n

    Every capability call validates inputs against a JSON Schema precondition before execution. Postconditions validate the output. Bad data never reaches your logic.

    \n
    \n
    \n
    \n \n
    \n

    WASM sandbox isolation

    \n

    Each capability runs in its own Wasmtime WASM instance with linear memory isolation. A capability cannot access host resources it was not explicitly granted.

    \n
    \n
    \n
    \n \n
    \n

    AI agent integration

    \n

    Expose your entire capability registry to AI agents via the MCP stdio server. Claude, GPT-4, and any MCP-compatible agent can discover and call capabilities safely.

    \n
    \n
    \n
    \n \n
    \n

    Cross-platform portability

    \n

    One WASM binary runs on the native target today, and directly in the browser via the Web embedder SDK. Edge and cloud placement are on the roadmap, not yet shipped.

    \n
    \n
    \n
    \n \n
    \n

    Trace artifacts

    \n

    Every execution produces a trace artifact: the input, the output, the contract version, and a timestamp. Audit any past run without re-executing anything.

    \n
    \n
    \n
    \n \n
    \n

    Governing specs

    \n

    Every contract links to the governing spec document it implements. When the policy changes, you update the spec and bump the contract version. The paper trail is built in.

    \n
    \n
    \n
    \n
    \n\n\n
    \n
    \n
    \n
    By the numbers
    \n

    One runtime. Any environment.

    \n
    \n
    \n
    \n
    1
    \n
    WASM binary runs identically on every placement target that has actually shipped — see the honest status on Platforms.
    \n
    \n
    \n
    0
    \n
    Logic rewrites when moving between environments. Same contract, same binary, same behavior everywhere.
    \n
    \n
    \n
    2ms
    \n
    Typical contract execution time on the local target. WASM startup is fast. Contract validation adds negligible overhead.
    \n
    \n
    \n
    \n
    \n\n\n
    \n
    \n
    \n
    Use cases
    \n

    Built for real business logic

    \n

    Pricing rules, eligibility checks, compliance logic — any deterministic computation that needs to run reliably everywhere.

    \n
    \n
    \n
    \n
    \n \n
    \n

    Pricing and discount logic

    \n

    Encode complex pricing rules as a contract with a link to your pricing policy document. The same capability runs in your frontend, your backend, and inside AI agent pipelines with identical results.

    \n Learn more →\n
    \n
    \n
    \n \n
    \n

    Eligibility and access rules

    \n

    Run eligibility logic as a sandboxed WASM capability so an AI agent can check a user's eligibility for a product, service, or feature without risk of hallucinating the answer.

    \n Learn more →\n
    \n
    \n
    \n \n
    \n

    Compliance and audit logic

    \n

    Capture regulatory and compliance rules in versioned contracts with governing spec links. Every execution is traced. Auditors can replay any historical decision from the trace artifact.

    \n Learn more →\n
    \n
    \n
    \n \n
    \n

    AI agent guardrails

    \n

    Give your AI agents a set of contract-governed capabilities to call. The agent cannot exceed the contract's boundaries. Postcondition checks block invalid outputs before they propagate.

    \n Learn more →\n
    \n
    \n
    \n
    \n\n\n
    \n
    \n
    \n

    Start building with Traverse

    \n

    Install the CLI, write your first contract, and run it in under five minutes.

    \n
    \n Get started →\n View on GitHub\n
    \n
    \n
    \n\n"; +const _body = "\n
    \n
    \n
    \n
    \n \n v0.8.1 · Apache 2.0 · Open source\n
    \n

    \n Define once.
    Run anywhere.\n

    \n

    \n Traverse is a contract-driven WASM runtime. Write business logic once with a machine-readable contract, run it natively or in the browser today, and let AI agents call it safely over MCP.\n

    \n
    \n Get started →\n Read the docs\n
    \n
    \n
    \n\n\n
    \n
    \n
    \n \n
    \n
    \n
    \n
    \n pricing.toml\n
    \n
    \n 
    [capability]\nname    = \"calculate-price\"\nversion = \"1.2.0\"\nwasm    = \"pricing.wasm\"\n\n[governing_spec]\ntitle   = \"Pricing Policy v3\"\nsource  = \"docs/pricing-policy.md\"\n\n[input]\ntype = \"object\"\nproperties.sku      = \"string\"\nproperties.quantity = \"integer\"\nproperties.region   = \"string\"\nrequired = [\"sku\", \"quantity\"]\n\n[output]\ntype = \"object\"\nproperties.total    = \"number\"\nproperties.currency = \"string\"\nrequired = [\"total\", \"currency\"]
    \n
    \n
    \n
    \n
    \n
    \n
    \n terminal\n
    \n
    \n
    $traverse run pricing --input '{\"sku\":\"PRO\",\"quantity\":5}'
    \n
    ✓ Contract validated
    \n
    ✓ WASM executed (2.1ms)
    \n
    → {\"total\": 249.95, \"currency\": \"USD\"}
    \n
    \n
    \n
    \n
    \n\n \n
    \n
    How Traverse works
    \n

    \n Write a contract.
    Ship a capability.\n

    \n

    \n Three steps from idea to a portable, contract-governed piece of business logic running in any environment.\n

    \n
    \n
    \n
    01
    \n
    \n

    Define the contract

    \n

    Write a TOML file with your capability name, the WASM binary path, and JSON Schema definitions for inputs and outputs. Link it to the governing spec document your team actually works from.

    \n
    \n
    \n
    \n
    02
    \n
    \n

    Compile to WASM

    \n

    Implement the logic in Rust and compile to wasm32-wasi. The same binary runs on every placement target without recompilation.

    \n
    \n
    \n
    \n
    03
    \n
    \n

    Register and run

    \n

    Add the capability to the registry with traverse add. Call it from the CLI, from an AI agent via MCP, or from your app directly. Every call is validated and traced.

    \n
    \n
    \n
    \n
    \n
    \n
    \n
    \n\n\n
    \n
    \n
    \n
    Features
    \n

    Everything business logic needs

    \n

    From contract validation to AI agent discovery, Traverse handles the entire lifecycle.

    \n
    \n
    \n
    \n
    \n \n
    \n

    Contract-first validation

    \n

    Every capability call validates inputs against a JSON Schema precondition before execution. Postconditions validate the output. Bad data never reaches your logic.

    \n
    \n
    \n
    \n \n
    \n

    WASM sandbox isolation

    \n

    Each capability runs in its own Wasmtime WASM instance with linear memory isolation. A capability cannot access host resources it was not explicitly granted.

    \n
    \n
    \n
    \n \n
    \n

    AI agent integration

    \n

    Expose your entire capability registry to AI agents via the MCP stdio server. Claude, GPT-4, and any MCP-compatible agent can discover and call capabilities safely.

    \n
    \n
    \n
    \n \n
    \n

    Cross-platform portability

    \n

    One WASM binary runs on the native target today, and directly in the browser via the Web embedder SDK. Edge and cloud placement are on the roadmap, not yet shipped.

    \n
    \n
    \n
    \n \n
    \n

    Trace artifacts

    \n

    Every execution produces a trace artifact: the input, the output, the contract version, and a timestamp. Audit any past run without re-executing anything.

    \n
    \n
    \n
    \n \n
    \n

    Governing specs

    \n

    Every contract links to the governing spec document it implements. When the policy changes, you update the spec and bump the contract version. The paper trail is built in.

    \n
    \n
    \n
    \n
    \n\n\n
    \n
    \n

    See it compose a real workflow, live.

    \n

    Watch an AI agent fetch the live capability registry in your browser and chain real capabilities into a working pipeline -- no fixtures, no mockups.

    \n Watch the live demo →\n
    \n
    \n\n\n
    \n
    \n
    \n
    By the numbers
    \n

    One runtime. Any environment.

    \n
    \n
    \n
    \n
    1
    \n
    WASM binary runs identically on every placement target that has actually shipped — see the honest status on Platforms.
    \n
    \n
    \n
    0
    \n
    Logic rewrites when moving between environments. Same contract, same binary, same behavior everywhere.
    \n
    \n
    \n
    2ms
    \n
    Typical contract execution time on the local target. WASM startup is fast. Contract validation adds negligible overhead.
    \n
    \n
    \n
    \n
    \n\n\n
    \n
    \n
    \n
    Use cases
    \n

    Built for real business logic

    \n

    Pricing rules, eligibility checks, compliance logic — any deterministic computation that needs to run reliably everywhere.

    \n
    \n
    \n
    \n
    \n \n
    \n

    Pricing and discount logic

    \n

    Encode complex pricing rules as a contract with a link to your pricing policy document. The same capability runs in your frontend, your backend, and inside AI agent pipelines with identical results.

    \n Learn more →\n
    \n
    \n
    \n \n
    \n

    Eligibility and access rules

    \n

    Run eligibility logic as a sandboxed WASM capability so an AI agent can check a user's eligibility for a product, service, or feature without risk of hallucinating the answer.

    \n Learn more →\n
    \n
    \n
    \n \n
    \n

    Compliance and audit logic

    \n

    Capture regulatory and compliance rules in versioned contracts with governing spec links. Every execution is traced. Auditors can replay any historical decision from the trace artifact.

    \n Learn more →\n
    \n
    \n
    \n \n
    \n

    AI agent guardrails

    \n

    Give your AI agents a set of contract-governed capabilities to call. The agent cannot exceed the contract's boundaries. Postcondition checks block invalid outputs before they propagate.

    \n Learn more →\n
    \n
    \n
    \n
    \n\n\n
    \n
    \n
    \n

    Start building with Traverse

    \n

    Install the CLI, write your first contract, and run it in under five minutes.

    \n
    \n Get started →\n View on GitHub\n
    \n
    \n
    \n\n"; const _jsonLd = "{\"@context\":\"https://schema.org\",\"@type\":\"SoftwareApplication\",\"name\":\"Traverse\",\"description\":\"A contract-driven Rust and WASM runtime for device-independent business capabilities. Capabilities run on any client by default; the client can heuristically delegate a subset of execution to the server when it decides to.\",\"url\":\"https://traverse-framework.com\",\"author\":{\"@type\":\"Person\",\"name\":\"Enrico Piovesan\"},\"license\":\"https://www.apache.org/licenses/LICENSE-2.0\",\"applicationCategory\":\"DeveloperApplication\",\"softwareVersion\":\"0.9.1\",\"codeRepository\":\"https://github.com/traverse-framework/traverse\"}"; --- Date: Fri, 21 Aug 2026 22:13:55 -0600 Subject: [PATCH 2/2] fix: stop overselling the discover demo as an AI agent Feedback from an outside read: the hero framing ("Watch an AI agent build a workflow", "real, working pipeline") claimed more than the page delivers. The registry data and composition are genuinely live, but the composer is a deterministic client-side heuristic, not a hosted model, and the execution animation is simulated, not a real WASM invocation -- the "How this is actually built" section already said so, just not until the bottom of the page. Rewrites the hero, meta title/description, and CTA link copy on discover.astro, index.astro, registry.astro, and agents.astro to lead with that distinction instead of burying it, and adds an upfront "Heuristic, not an AI model" badge next to "Live registry data". Co-Authored-By: Claude Sonnet 5 --- src/pages/agents.astro | 2 +- src/pages/discover.astro | 13 +++++++------ src/pages/index.astro | 2 +- src/pages/registry.astro | 2 +- 4 files changed, 10 insertions(+), 9 deletions(-) diff --git a/src/pages/agents.astro b/src/pages/agents.astro index 9afebe0..924f542 100644 --- a/src/pages/agents.astro +++ b/src/pages/agents.astro @@ -146,7 +146,7 @@ const _body = `

    The MCP setup guide walks through configuring Claude or any MCP-compatible client against a local server.

    diff --git a/src/pages/discover.astro b/src/pages/discover.astro index f579960..09ef6b3 100644 --- a/src/pages/discover.astro +++ b/src/pages/discover.astro @@ -5,10 +5,11 @@ const _body = `
    Live demo -

    Watch an AI agent build a workflow out of real capabilities.

    -

    This isn't a mockup. Your browser fetches the live Traverse capability registry, picks a group of related capabilities, and chains them into a real, working pipeline -- the same kind of workflow you could compose today with traverse-cli. Nothing on this page is precomputed or faked.

    +

    Watch a workflow get composed, live, from what's actually published.

    +

    The data is real: your browser fetches the live Traverse capability registry and a client-side heuristic -- not a hosted AI model -- groups related capabilities and orders them into a plausible pipeline, the shape of what an AI agent could compose over MCP. Nothing is precomputed; only the WASM execution afterward is simulated, not actually run. Full breakdown of what's real and what's not in how this is actually built, below.

    Live registry data + Heuristic, not an AI model querying registry.traverse-framework.com…
    @@ -43,7 +44,7 @@ const _body = `
    -

    How to read it: your Goal is the request that starts everything. The Traverse system -- the AI agent, its MCP connection, and the runtime -- discovers and validates a matching workflow along the dashed line. The runtime then chains together the right capabilities to do the actual work, producing a Result along the solid line. Watch each step light up as it runs, and click any capability to open its real, published contract in the registry.

    +

    How to read it: your Goal is the request that starts everything. The Traverse system -- the AI agent, its MCP connection, and the runtime -- is the architecture a real agent would talk to, discovering and validating a matching workflow along the dashed line. The runtime then chains together the right capabilities to do the actual work, producing a Result along the solid line. Click any capability to open its real, published contract in the registry. The step-by-step animation shows execution order; it doesn't run the WASM.

    @@ -52,7 +53,7 @@ const _body = `
    -
    +
    How this is actually built
    @@ -64,8 +65,8 @@ const _body = `
    `; --- diff --git a/src/pages/index.astro b/src/pages/index.astro index a419128..147d019 100644 --- a/src/pages/index.astro +++ b/src/pages/index.astro @@ -1,7 +1,7 @@ --- import BaseLayout from '@layouts/BaseLayout.astro'; -const _body = "\n
    \n
    \n
    \n
    \n \n v0.8.1 · Apache 2.0 · Open source\n
    \n

    \n Define once.
    Run anywhere.\n

    \n

    \n Traverse is a contract-driven WASM runtime. Write business logic once with a machine-readable contract, run it natively or in the browser today, and let AI agents call it safely over MCP.\n

    \n
    \n Get started →\n Read the docs\n
    \n
    \n
    \n\n\n
    \n
    \n
    \n \n
    \n
    \n
    \n
    \n pricing.toml\n
    \n
    \n 
    [capability]\nname    = \"calculate-price\"\nversion = \"1.2.0\"\nwasm    = \"pricing.wasm\"\n\n[governing_spec]\ntitle   = \"Pricing Policy v3\"\nsource  = \"docs/pricing-policy.md\"\n\n[input]\ntype = \"object\"\nproperties.sku      = \"string\"\nproperties.quantity = \"integer\"\nproperties.region   = \"string\"\nrequired = [\"sku\", \"quantity\"]\n\n[output]\ntype = \"object\"\nproperties.total    = \"number\"\nproperties.currency = \"string\"\nrequired = [\"total\", \"currency\"]
    \n
    \n
    \n
    \n
    \n
    \n
    \n terminal\n
    \n
    \n
    $traverse run pricing --input '{\"sku\":\"PRO\",\"quantity\":5}'
    \n
    ✓ Contract validated
    \n
    ✓ WASM executed (2.1ms)
    \n
    → {\"total\": 249.95, \"currency\": \"USD\"}
    \n
    \n
    \n
    \n
    \n\n \n
    \n
    How Traverse works
    \n

    \n Write a contract.
    Ship a capability.\n

    \n

    \n Three steps from idea to a portable, contract-governed piece of business logic running in any environment.\n

    \n
    \n
    \n
    01
    \n
    \n

    Define the contract

    \n

    Write a TOML file with your capability name, the WASM binary path, and JSON Schema definitions for inputs and outputs. Link it to the governing spec document your team actually works from.

    \n
    \n
    \n
    \n
    02
    \n
    \n

    Compile to WASM

    \n

    Implement the logic in Rust and compile to wasm32-wasi. The same binary runs on every placement target without recompilation.

    \n
    \n
    \n
    \n
    03
    \n
    \n

    Register and run

    \n

    Add the capability to the registry with traverse add. Call it from the CLI, from an AI agent via MCP, or from your app directly. Every call is validated and traced.

    \n
    \n
    \n
    \n
    \n
    \n
    \n
    \n\n\n
    \n
    \n
    \n
    Features
    \n

    Everything business logic needs

    \n

    From contract validation to AI agent discovery, Traverse handles the entire lifecycle.

    \n
    \n
    \n
    \n
    \n \n
    \n

    Contract-first validation

    \n

    Every capability call validates inputs against a JSON Schema precondition before execution. Postconditions validate the output. Bad data never reaches your logic.

    \n
    \n
    \n
    \n \n
    \n

    WASM sandbox isolation

    \n

    Each capability runs in its own Wasmtime WASM instance with linear memory isolation. A capability cannot access host resources it was not explicitly granted.

    \n
    \n
    \n
    \n \n
    \n

    AI agent integration

    \n

    Expose your entire capability registry to AI agents via the MCP stdio server. Claude, GPT-4, and any MCP-compatible agent can discover and call capabilities safely.

    \n
    \n
    \n
    \n \n
    \n

    Cross-platform portability

    \n

    One WASM binary runs on the native target today, and directly in the browser via the Web embedder SDK. Edge and cloud placement are on the roadmap, not yet shipped.

    \n
    \n
    \n
    \n \n
    \n

    Trace artifacts

    \n

    Every execution produces a trace artifact: the input, the output, the contract version, and a timestamp. Audit any past run without re-executing anything.

    \n
    \n
    \n
    \n \n
    \n

    Governing specs

    \n

    Every contract links to the governing spec document it implements. When the policy changes, you update the spec and bump the contract version. The paper trail is built in.

    \n
    \n
    \n
    \n
    \n\n\n
    \n
    \n

    See it compose a real workflow, live.

    \n

    Watch an AI agent fetch the live capability registry in your browser and chain real capabilities into a working pipeline -- no fixtures, no mockups.

    \n Watch the live demo →\n
    \n
    \n\n\n
    \n
    \n
    \n
    By the numbers
    \n

    One runtime. Any environment.

    \n
    \n
    \n
    \n
    1
    \n
    WASM binary runs identically on every placement target that has actually shipped — see the honest status on Platforms.
    \n
    \n
    \n
    0
    \n
    Logic rewrites when moving between environments. Same contract, same binary, same behavior everywhere.
    \n
    \n
    \n
    2ms
    \n
    Typical contract execution time on the local target. WASM startup is fast. Contract validation adds negligible overhead.
    \n
    \n
    \n
    \n
    \n\n\n
    \n
    \n
    \n
    Use cases
    \n

    Built for real business logic

    \n

    Pricing rules, eligibility checks, compliance logic — any deterministic computation that needs to run reliably everywhere.

    \n
    \n
    \n
    \n
    \n \n
    \n

    Pricing and discount logic

    \n

    Encode complex pricing rules as a contract with a link to your pricing policy document. The same capability runs in your frontend, your backend, and inside AI agent pipelines with identical results.

    \n Learn more →\n
    \n
    \n
    \n \n
    \n

    Eligibility and access rules

    \n

    Run eligibility logic as a sandboxed WASM capability so an AI agent can check a user's eligibility for a product, service, or feature without risk of hallucinating the answer.

    \n Learn more →\n
    \n
    \n
    \n \n
    \n

    Compliance and audit logic

    \n

    Capture regulatory and compliance rules in versioned contracts with governing spec links. Every execution is traced. Auditors can replay any historical decision from the trace artifact.

    \n Learn more →\n
    \n
    \n
    \n \n
    \n

    AI agent guardrails

    \n

    Give your AI agents a set of contract-governed capabilities to call. The agent cannot exceed the contract's boundaries. Postcondition checks block invalid outputs before they propagate.

    \n Learn more →\n
    \n
    \n
    \n
    \n\n\n
    \n
    \n
    \n

    Start building with Traverse

    \n

    Install the CLI, write your first contract, and run it in under five minutes.

    \n
    \n Get started →\n View on GitHub\n
    \n
    \n
    \n\n"; +const _body = "\n
    \n
    \n
    \n
    \n \n v0.8.1 · Apache 2.0 · Open source\n
    \n

    \n Define once.
    Run anywhere.\n

    \n

    \n Traverse is a contract-driven WASM runtime. Write business logic once with a machine-readable contract, run it natively or in the browser today, and let AI agents call it safely over MCP.\n

    \n
    \n Get started →\n Read the docs\n
    \n
    \n
    \n\n\n
    \n
    \n
    \n \n
    \n
    \n
    \n
    \n pricing.toml\n
    \n
    \n 
    [capability]\nname    = \"calculate-price\"\nversion = \"1.2.0\"\nwasm    = \"pricing.wasm\"\n\n[governing_spec]\ntitle   = \"Pricing Policy v3\"\nsource  = \"docs/pricing-policy.md\"\n\n[input]\ntype = \"object\"\nproperties.sku      = \"string\"\nproperties.quantity = \"integer\"\nproperties.region   = \"string\"\nrequired = [\"sku\", \"quantity\"]\n\n[output]\ntype = \"object\"\nproperties.total    = \"number\"\nproperties.currency = \"string\"\nrequired = [\"total\", \"currency\"]
    \n
    \n
    \n
    \n
    \n
    \n
    \n terminal\n
    \n
    \n
    $traverse run pricing --input '{\"sku\":\"PRO\",\"quantity\":5}'
    \n
    ✓ Contract validated
    \n
    ✓ WASM executed (2.1ms)
    \n
    → {\"total\": 249.95, \"currency\": \"USD\"}
    \n
    \n
    \n
    \n
    \n\n \n
    \n
    How Traverse works
    \n

    \n Write a contract.
    Ship a capability.\n

    \n

    \n Three steps from idea to a portable, contract-governed piece of business logic running in any environment.\n

    \n
    \n
    \n
    01
    \n
    \n

    Define the contract

    \n

    Write a TOML file with your capability name, the WASM binary path, and JSON Schema definitions for inputs and outputs. Link it to the governing spec document your team actually works from.

    \n
    \n
    \n
    \n
    02
    \n
    \n

    Compile to WASM

    \n

    Implement the logic in Rust and compile to wasm32-wasi. The same binary runs on every placement target without recompilation.

    \n
    \n
    \n
    \n
    03
    \n
    \n

    Register and run

    \n

    Add the capability to the registry with traverse add. Call it from the CLI, from an AI agent via MCP, or from your app directly. Every call is validated and traced.

    \n
    \n
    \n
    \n
    \n
    \n
    \n
    \n\n\n
    \n
    \n
    \n
    Features
    \n

    Everything business logic needs

    \n

    From contract validation to AI agent discovery, Traverse handles the entire lifecycle.

    \n
    \n
    \n
    \n
    \n \n
    \n

    Contract-first validation

    \n

    Every capability call validates inputs against a JSON Schema precondition before execution. Postconditions validate the output. Bad data never reaches your logic.

    \n
    \n
    \n
    \n \n
    \n

    WASM sandbox isolation

    \n

    Each capability runs in its own Wasmtime WASM instance with linear memory isolation. A capability cannot access host resources it was not explicitly granted.

    \n
    \n
    \n
    \n \n
    \n

    AI agent integration

    \n

    Expose your entire capability registry to AI agents via the MCP stdio server. Claude, GPT-4, and any MCP-compatible agent can discover and call capabilities safely.

    \n
    \n
    \n
    \n \n
    \n

    Cross-platform portability

    \n

    One WASM binary runs on the native target today, and directly in the browser via the Web embedder SDK. Edge and cloud placement are on the roadmap, not yet shipped.

    \n
    \n
    \n
    \n \n
    \n

    Trace artifacts

    \n

    Every execution produces a trace artifact: the input, the output, the contract version, and a timestamp. Audit any past run without re-executing anything.

    \n
    \n
    \n
    \n \n
    \n

    Governing specs

    \n

    Every contract links to the governing spec document it implements. When the policy changes, you update the spec and bump the contract version. The paper trail is built in.

    \n
    \n
    \n
    \n
    \n\n\n
    \n
    \n

    Watch a workflow get composed, live.

    \n

    Your browser fetches the real capability registry and a client-side heuristic -- not a hosted AI model -- chains matching capabilities into a workflow. No fixtures, no precomputed data.

    \n Watch the live demo →\n
    \n
    \n\n\n
    \n
    \n
    \n
    By the numbers
    \n

    One runtime. Any environment.

    \n
    \n
    \n
    \n
    1
    \n
    WASM binary runs identically on every placement target that has actually shipped — see the honest status on Platforms.
    \n
    \n
    \n
    0
    \n
    Logic rewrites when moving between environments. Same contract, same binary, same behavior everywhere.
    \n
    \n
    \n
    2ms
    \n
    Typical contract execution time on the local target. WASM startup is fast. Contract validation adds negligible overhead.
    \n
    \n
    \n
    \n
    \n\n\n
    \n
    \n
    \n
    Use cases
    \n

    Built for real business logic

    \n

    Pricing rules, eligibility checks, compliance logic — any deterministic computation that needs to run reliably everywhere.

    \n
    \n
    \n
    \n
    \n \n
    \n

    Pricing and discount logic

    \n

    Encode complex pricing rules as a contract with a link to your pricing policy document. The same capability runs in your frontend, your backend, and inside AI agent pipelines with identical results.

    \n Learn more →\n
    \n
    \n
    \n \n
    \n

    Eligibility and access rules

    \n

    Run eligibility logic as a sandboxed WASM capability so an AI agent can check a user's eligibility for a product, service, or feature without risk of hallucinating the answer.

    \n Learn more →\n
    \n
    \n
    \n \n
    \n

    Compliance and audit logic

    \n

    Capture regulatory and compliance rules in versioned contracts with governing spec links. Every execution is traced. Auditors can replay any historical decision from the trace artifact.

    \n Learn more →\n
    \n
    \n
    \n \n
    \n

    AI agent guardrails

    \n

    Give your AI agents a set of contract-governed capabilities to call. The agent cannot exceed the contract's boundaries. Postcondition checks block invalid outputs before they propagate.

    \n Learn more →\n
    \n
    \n
    \n
    \n\n\n
    \n
    \n
    \n

    Start building with Traverse

    \n

    Install the CLI, write your first contract, and run it in under five minutes.

    \n
    \n Get started →\n View on GitHub\n
    \n
    \n
    \n\n"; const _jsonLd = "{\"@context\":\"https://schema.org\",\"@type\":\"SoftwareApplication\",\"name\":\"Traverse\",\"description\":\"A contract-driven Rust and WASM runtime for device-independent business capabilities. Capabilities run on any client by default; the client can heuristically delegate a subset of execution to the server when it decides to.\",\"url\":\"https://traverse-framework.com\",\"author\":{\"@type\":\"Person\",\"name\":\"Enrico Piovesan\"},\"license\":\"https://www.apache.org/licenses/LICENSE-2.0\",\"applicationCategory\":\"DeveloperApplication\",\"softwareVersion\":\"0.9.1\",\"codeRepository\":\"https://github.com/traverse-framework/traverse\"}"; ---

    Check the registry before authoring a new capability — something close enough to reuse or extend might already exist.