Would this action be allowed, and what decides
REAL and PURE — no side effect, no ledger row, nothing enqueued, nothing metered, and side_effects: [] on the wire so a caller does not have to take the documentation’s word for it. The primitive tier is the GOVERNOR’s own verdict, over the same client the gate uses and with the same strict flag the gate would set for that primitive. The capability and approval tiers are re-derived, because the governor evaluates those inside a guarded evaluation that PERSISTS an approvals row when it freezes: an explain that called it would write one every time somebody asked a question. tiers names which is which, and which tiers (budget, freeze, connections, revocation, the actor test) this answer does not consult at all. A governor that is unreachable yields verdict: "unavailable" rather than the gate’s 403, because the endpoint you run to find out why you were refused cannot itself be refused.
Authorizations
Workspace API key. Create one via the dashboard or POST /v1/auth/keys.
Query Parameters
Tenant user id. Absent, the caller's own subject answers.
Body
Response
The verdict, and the layer and rule that produced it.
The ENGINE's verdict vocabulary. approve is what a rule author writes; it folds to park.
allow, deny, park, attest, unavailable Which tiers this answer consulted (consulted), which it re-derived rather than asked the governor for (reimplemented), and which it did not evaluate at all (not_consulted). A caller that cannot tell those apart cannot judge how much to trust the verdict.