AgentOps

Durable state before orchestration theatre

Runs are persisted with idempotency at the project boundary. Each step and state transition becomes an ordered event, so the worker can resume database-backed work and the API can reconstruct a run without relying on process memory. This is also why I do not describe the current execution path as Temporal-backed: Temporal appears in planning and local compose material, but the public worker is database-backed.

Versioned configuration publication makes a completed run explainable later. A run points to the configuration that actually executed instead of a mutable draft that may have changed since.

One event history, two delivery paths

The database is the durable source of truth. Append-only run events and an outbox capture committed changes; a relay publishes them through Redis for low-latency delivery. Authenticated WebSocket clients can receive the live path, then reconnect with sequence information and catch up from persisted history when they miss messages.

This separates delivery speed from correctness: Redis can accelerate updates, but a transient relay or connection failure does not erase the run record.

Trust boundaries are part of the feature

Tenant and project scope are carried through authentication, API keys, and persisted records. External tool execution validates inputs and outputs, applies timeout and retry rules, normalizes responses, and includes safeguards against server-side request forgery. Usage, pricing snapshots, redaction, approvals, evaluation results, child runs, and handoffs remain inspectable as part of the trace rather than disappearing into logs.

The current trade-off is intentional: the platform demonstrates the control-plane model and durable data flow, but it does not claim production operations, comprehensive coverage, or a migration to a workflow engine that the public runtime does not yet use.