Define once. Run anywhere.
Traverse is a contract-driven WebAssembly runtime and a governed registry for portable business capabilities. You write a rule — pricing, eligibility, authorization, escalation — once, as a capability with a machine-readable contract, and the same signed WASM artifact runs on Linux, macOS, and Windows, on iOS and Android, in the browser, on a server, and inside an AI agent — producing a verifiable execution trace every time.
No reimplementation per environment. No agent free-handing your business rules. One behavior, governed, everywhere it needs to run. It's the working implementation of Universal Microservices Architecture: the agent proposes, the runtime decides.
→ traverse-framework.com ·
start in traverse
| Repo | What it is |
|---|---|
traverse |
Core runtime, CLI, contracts, and MCP surface. Rust, v0.10.0, 134 approved specs, 6 crates on crates.io, ~660 commits. |
registry |
The public capability registry — a git-based, CI-validated, PR-published catalog. 46 capabilities across 24 domains (117 signed versions) live at registry.traverse-framework.com. |
reference-apps |
Real example apps — one set of Traverse capabilities behind many UI shells: Web, macOS, iOS, Android, Windows, Linux, CLI, plus MCP façades for Claude, Cursor, ChatGPT, and Grok. |
claude-skills |
Claude Skills for building on Traverse — check the registry before authoring, compose capabilities, validate against the real CLI. |
website |
The public site and documentation. |
.github |
(this repo) Org-wide governance — constitution, NFRs, quality standards, CI gates, CLA, and AI-agent hardening rules shared by every repo above. |
repo-template |
Starting point for a new org repo — compliant with governance from the first commit. |
Platform reach: five embedder SDKs on one embedder-api/1.0.0 contract and
one CI conformance suite — Rust and Web/TypeScript published (crates.io / npm);
Swift (iOS/macOS, WasmKit), Kotlin (Android, Chicory), and .NET (Windows,
Wasmtime) shipping from traverse/packages/. Cloud and edge placement targets
are specified and on the roadmap, not yet shipped.
The same business rule now has to run in a web client, on a server, at the edge, and inside an AI agent a user is talking to. Teams answer that by rewriting the rule in each stack; the copies drift and the behavior stops being one thing.
AI coding agents make this sharper: an agent asked to "add the discount logic" re-derives it from scratch every session — unversioned, unreviewed, and authoritative only because it ran last. Traverse's position is the opposite: a capability is a contract, an immutable version, a signature, and a WASM artifact; the runtime validates every input, isolates execution in a sandbox, enforces policy, and emits an auditable trace. The agent's job is to find and compose existing capabilities — not to be the source of truth for what the business does. The registry already holds 46 of them, so that logic is a lookup, not a regeneration.
Every repo in this org follows the same spec-driven governance model: approved specs are versioned, immutable, and merge-gating; contracts are the source of truth for runtime behavior; core logic holds 100% automated coverage; a deterministic spec-alignment gate runs on every PR.
See constitution.md for the full rules,
GOVERNANCE.md for the ownership and decision model, and
each repo's own CLAUDE.md / AGENTS.md for what's specific to it. One CLA
signature covers every repo in the org.