Guard execution host
api-reference / v1
Runtime vocabulary
The execution contract uses modes observe / repair / strict; decisions ok / repaired / degraded / bypassed / blocked. Writes and conservative unknown operations require an upstream-enforced idempotency_key. The default guest has no selective repair output. A completed response halt is not permission to replay a write.
Authentication and errors
Credentials and runtime policy have distinct owners. The surface uses MCP transport errors; the guard runtime taxonomy is separate.