traverse-framework/traverse

Traverse

Your business logic runs in the browser, on your server, and in a cloud function. They drift. You maintain three versions of the same behavior. Traverse keeps it in one contract and runs it anywhere — with a full execution trace every time.

Traverse is the working implementation of Universal Microservices Architecture.

---

Current State & Roadmap

Traverse is pre-1.0 (v0.8.1) and evolving under spec-driven governance — every capability below is real, running code, not a plan.

• 8 crates in this repo plus the capability registry (now its own repo, see below) — 7 of these 9 are published on crates.io: runtime, contracts, registry, CLI, MCP server, embedder SDK, and the expedition WASM example. traverse-native-bridge and traverse-swift-host are newer, not yet published.
• 87 approved, immutable specs govern the runtime, contracts, registry, MCP surface, WASM execution, native embedding, and durable local storage. Full list: jq -r '.specs[].id' specs/governance/approved-specs.json (or see Governance below).
• 100% coverage enforced on core logic, spec-alignment and supply-chain gates on every PR, 5-platform CI matrix (Linux x8664/aarch64, macOS x8664/arm64, Windows x8664).
• Capability registry was extracted into its own repo, traverse-framework/registry, so capabilities can be published, versioned, and consumed independently of the runtime.
• Reference apps for multiple platforms (web, iOS, macOS, Android, Windows, Linux, CLI) live in traverse-framework/reference-apps.

Where this is going: v1.0.0

v1.0.0 is gated, not a date — governed by spec 049-v1-milestone-gate and checkable locally with bash scripts/ci/v1gatecheck.sh. It signals stable public API surfaces, every published crate live on crates.io, and the runtime stress-tested on every supported platform. Full gate conditions: docs/v1-milestone.md.

Explicitly not required for v1.0.0: a reference app in this repo (that's reference-apps), an HTTP admin API, a cloud deployment surface, or worker-isolation message passing (planned for v2).

---

Quick Start

Requirements: Rust 1.94+

git clone https://github.com/traverse-framework/traverse.git
cd traverse
cargo build
cargo run -p traverse-cli-rs -- bundle inspect examples/expedition/registry-bundle/manifest.json

Expected output:

bundle_id: expedition.planning.seed-bundle
version: 1.0.0
capabilities: 6
events: 5
workflows: 1

You just inspected a live capability bundle — 6 capabilities, 5 events, 1 workflow, all defined in contracts that the runtime validates and executes.

Ready to run the full browser demo? → quickstart.md