Inspect, reproduce, evaluate

Proof with a stated boundary.

Different evidence answers different questions. No browser simulation establishes production durability, throughput or universal exactly-once execution.

Browser simulation

Illustrates the decisions. No SDK, provider writes or persistent state.

Explore decisions

Installed SDK

Local fake provider and separate journal. Verify first effect, replay, conflict, fresh process and UNKNOWN blocking.

Run current quickstart

Real provider example

GitHub issue recovery with bounded authoritative lookup and explicit correlation assumptions.

Inspect integration

Framework crash/retry labs

LangGraph and CrewAI examples use controlled simulated provider ledgers and the SQLite reference backend. They test hard process termination and fresh-process resume/redispatch. Inspect each lab’s methodology before generalising its result.

Routing conformance

Published fixed-suite results describe the evaluated model sessions and cases, not universal model reliability or production routing correctness.

Routing methodology and integrity trail

Hosted and historical evidence

Hosted playground evidence and its scope. Stripe staging proof is a specifically scoped staging experiment, not a blanket live payment/refund adapter guarantee.

Historical reproducibility fixture — v0.1.9. Frozen versions remain pinned intentionally. For a current-package consumer, use the maintained quickstart.

Review the source and safety tests

Local safety depends on one stable logical intent, complete effect binding, durable same-machine state and every consequential call traversing the protected boundary. Authoritative confirmation may resolve UNKNOWN; local absence does not cause automatic ambiguous redispatch.
Verify your first action