Known Limits

This page indexes the boundaries developers most often plan around. Each boundary is described once, on Scope and Limits.

Reference journeys and live vendor execution: named reference journeys carry evidence only at their recorded scope.
Provider coverage: operation coverage differs by provider. See also Provider Support.
Routing: routing is explicit and recorded. See also Routing.
Replay and idempotency: guarantees are route-dependent. See also Idempotency.
Advanced external-enforcement observation: POST /v1/permits does not dispatch or observe the provider call.
Read/write governance coverage: only actions routed through Keel are governed. See also Read/Write Governance.
Accounting: estimates are reconciled to provider-final usage when it is available.
Content inspection: the Prompt Firewall is deterministic and route-scoped. See also Prompt Firewall.
Integrity proof model: what the evidence stack proves and does not prove. Plan tiers are on Trust & Integrity and Plans & Entitlements.
Public-surface boundaries: realtime sessions and operator internals.
What to rely on: the supported integration surface.

Related pages