Questions
Answers to common questions.
Contracts, capabilities, the runtime, AI agent integration, and how Traverse compares to what you already know.
Getting started
Contracts and capabilities
- What is a contract in Traverse?
- What does "contract-driven" mean in Traverse?
- How do I write a capability contract?
- What are preconditions in a Traverse contract?
- What are postconditions in a Traverse contract?
- What is a governing spec in Traverse?
- What is contract versioning in Traverse?
- What is the contract lifecycle in Traverse?
- What is a WASM capability in Traverse?
- What happens when a capability fails?
- How does constraint validation work in Traverse?
Runtime and architecture
- How does Traverse execute WASM?
- Can Traverse run without WASM?
- What is the capability registry?
- How do placement targets work in Traverse?
- What is a trace artifact in Traverse?
- What is the Traverse execution state machine?
- What is the browser adapter?
- What crates make up Traverse?
- What is the Traverse CLI?
- How does Traverse handle errors?
- How does Traverse handle events?
- Does Traverse support streaming?
AI agents and MCP
How Traverse compares
- How is Traverse different from function calling?
- How is Traverse different from microservices?
- How is Traverse different from serverless functions?
- How is Traverse different from WASI?
- How is Traverse different from a plugin system?
- Is Traverse a replacement for REST APIs?
- What is UMA (Universal Microservices Architecture)?
Use cases