traverse-framework/traverse

Traverse

Define once. Run anywhere.

Traverse is a contract-driven WebAssembly runtime for portable business capabilities. What you get: discover a governed capability → execute known behavior → produce a verifiable trace. You define a piece of business logic once — as a capability with a machine-readable contract — and the same signed WASM binary runs on Linux, macOS, and Windows, on iOS and Android, in the browser, and inside an AI agent.

No reimplementation per environment. No agent free-handing your pricing rules. One behavior, governed, everywhere it needs to run.

---

Why this matters

Business logic no longer lives in one place. The same eligibility check, pricing rule, or approval policy now has to run in a web client, on a server, at the edge, and — increasingly — inside an AI agent that a user is talking to. Teams answer that by reimplementing the rule in each stack. The copies drift. The behavior stops being one thing.

AI coding agents make this sharper, not softer. An agent asked to "add the discount logic" will re-derive that logic from scratch, in prose, every session — unversioned, unreviewed, and authoritative only because it ran last.

Traverse takes the other position: the agent proposes, the runtime decides. A capability is a contract (JSON Schema in, JSON Schema out), an immutable version, a signature, and a WASM artifact. The runtime validates every input against the contract, isolates execution in a WASM sandbox, enforces policy, and emits a trace you can audit. An agent's job is to find and compose the right capabilities — not to be the source of truth for what the business does.

This is the working implementation of Universal Microservices Architecture: write once, run where it makes sense, keep the decisions queryable instead of buried in a framework.

---

Reuse instead of regenerate

The public registry is the catalog to search before you invent a rule — pricing, authorization, escalation, deadline pressure, scoring, classification, summarization, and more. Every record is contract-defined, semver'd, and signed before it merges. Live counts belong on the registry site; they are not the product pitch.

Before an agent (or a developer) writes a rule, it can check whether that rule already exists:

traverse-cli registry sync   --workspace local-default --json   # pull the index locally
traverse-cli registry search price --workspace local-default --json
traverse-cli registry search price --workspace local-default --commercial-use allowed --json
traverse-cli registry list   --workspace local-default --json

Licensing filters (--commercial-use, --redistribution) project Registry spec 025-capability-licensing-metadata fields from the synced index. Declarative only — unknown / conditional / forbidden are never treated as permission.

Find core.calculate-price@1.1.0, compose it into a workflow, done. What you don't spend tokens or review cycles on:

• re-deriving the input/output contract
• re-implementing and re-testing the logic
• re-reviewing a fresh, unverified copy of a rule the org already agreed on