Generate authorization decision receipts

A receipt records evaluated permission, not execution or observed success.

01 / The operating case

What changes in a real workflow?

An auditor asks why a remediation agent was allowed to isolate H-7.

Trace the authority boundary
  1. 01Authority origin
  2. 02Task and grant
  3. 03Current decision
  4. 04Observed outcome

02 / Decision contract

What the executor must check

Emit a stable decision ID, trusted principal and grant references, task, normalized request digest, policy version, context timestamp, verdict and reason.

InputPrincipal · task · action · target
DecisionGrant ancestry · policy · current state
ResultEnforce · record · verify outcome

03 / Failure and evidence

What goes wrong, and what can be proven?

Failure mode

A bare ALLOW log cannot explain target, origin or rule version.

Evidence to retain

Retain receipt integrity and correlation to executor and observation records.

04 / Canonical scope

Why this reference stands alone

Execution receipts record attempted effect; this guide owns permission evidence.

Illustrative implementation artifact

Decision receipt fields

{decisionId, timestamp, principalId, taskId,
 originGrantId, evaluatedGrantPath, action, immutableTarget,
 requestDigest, policyVersion, contextVersion,
 verdict, reasonCode, expiresAt}

Primary references

Read the underlying material

Architecture discussion

Choose one consequential action and make its boundary explicit.

Request a Conversation