This began as internal tooling. We were building agents for clients and rewriting the same durability layer each time: checkpointing, retries, approval gates, trace capture. The fourth rewrite became a product.
What it does differently
The design premise is that an agent is a long-running workflow, not a chat loop. That reframing solves most of the reliability problems people attribute to models. A workflow can be paused, resumed on another machine, replayed against a new prompt, and audited months later.
Where it fits
It is used in production for order reconciliation, contract review triage, and multi-step ops runbooks. These are cases where a wrong action is expensive and the audit trail is not optional.