Deployment assumption
Customer-controlled environments and framework-aware runtime policy hooks.
Technical overview
This page gives a lightweight technical overview without turning the homepage into documentation.
Customer-controlled environments and framework-aware runtime policy hooks.
Repeated steps, invalid tool arguments, lost state handoffs, timeout patterns, and token-spend spikes.
Pause, stop, limited retry, fallback route, schema review, engineering review, or human approval gate.
A typical policy defines what failure was detected, what recovery action is approved, and what non-sensitive event record should be preserved.
Public contact should not include production credentials, API keys, access tokens, PHI, payment data, customer records, regulated data, raw prompts, raw logs, databases, source code, or sensitive production payloads.
View evaluation boundary