Decision History (Visibility & Audit)

Decision history is how you prove what happened: what intent was evaluated, what ASG returned, and whether execution was allowed.

What you must persist

Persist these values in your system for every evaluated action:

Field	Why it matters
decision_id	Primary identifier for the ASG decision.
status	The enforceable outcome (`PASS` / `WARN` / `BLOCK`).
request_id	Correlates the decision to your request logs and traces.
idempotency_key	Proves dedupe behavior and prevents double-execution.
action_kind / action_type	Documents exactly what real-world action was evaluated.
actor_user_id / account_id	Attribution for auditors and incident response.

What you should log

The exact request you sent to ASG (redacting secrets).
The full ASG response.
Whether execution occurred and when.

Human approval trace

If you implement approvals for WARN:

Record who approved.
Record when approval happened.
Record the approval rationale.
Record the exact decision_id that was approved.

Retention

Keep decision history for at least as long as your compliance requirements require.

Legal & Responsibility Notice

Summary

Informational only

Provided for general guidance. Not legal, compliance, security, or professional advice.

You control implementation

You are responsible for policies, prompts, integrations, workflows, and regulatory requirements.

Liability limitation

To the maximum extent permitted by law, the company disclaims liability for losses arising from use of this documentation or implementations based on it.