11 pages
Specs
The capability specifications the implementation is written against.
The spec-driven workflow — scenario to test to code — and why the archived change history is the evidence for it.
- Wire schemasStable
The protobuf messages that define every wire and state format the runtime uses.
- Proto codersStable
Deterministic protobuf coders for keyed state and pipeline elements — the reason state is never pickled.
- Tool registryStable
The @tool decorator, argument schemas, and the side-effect guard that makes ctx.act the only effect path.
- Memory facadeStable
Working memory: scalars, bounded rings, staging, and the caps that keep per-key state bounded.
- Model clientStable
The LLMClient protocol, request and response types, and the provider error taxonomy.
- Model facadeStable
Retry, circuit breaking, output schemas, usage accounting, and tracing around provider calls.
- LLM replay cacheStable
Keyed-state memoization of model calls — what makes a bundle retry cost zero additional provider calls.
- Fake LLMStable
The deterministic in-process model double every test and example on this site runs against.
- Repository scaffoldingStable
The environment, quality gates, service topology, and CI workflow contracts every other capability relies on.
- Capability spec indexPartial
The capability specifications promoted at 1.0 that have no dedicated page here yet, each with where it lives in the repository.