Skip to content

You are currently viewing documentation for0.1.0-alpha.1

Guard execution host

Unavailable on the agent surface

POST /v1/guard belongs to a separate execution host. The local sidecar and Worker implement it; this signed document does not publish its schema. Endpoint fields are therefore not reproduced as a parallel schema here.

Guard operation on the agent surface — unavailable

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.