Informational Fresh jira_story: GOV-151

Lesson 2 of 4 — Audit logging on every state change

Cross-Cutting & Hardening · Source: Jira Story GOV-151 (3 pts) · Authority: Informational (the Jira story is authoritative).

Purpose

Record every state change immutably.

Why it matters

An immutable audit trail is the backbone of defensible governance.

Where this lives

Runs in the Customer AI Governance platform (components: platform). Every state transition writes an append-only AuditLog row. Learn teaches this read-only.

Workflow

Given any state transition
When it occurs
Then an immutable AuditLog row is written

Worked example

A finding's status changes but no audit row appears. What's wrong?

Every state change must write an immutable AuditLog row — the trail can't have gaps.

Acceptance criteria (authoritative — GOV-151)

Given any state transition, when it occurs, then an immutable AuditLog row is written.

Common pitfalls

Mutable or missing audit entries on some transitions.

Knowledge check

Scenario: A finding's status changes but no audit row appears. What's wrong?
Look for: Every state change must write an immutable AuditLog row — the trail can't have gaps.

Key concepts

immutable audit log
state transitions
append-only

For the AI Tutor

Summary: Record every state change immutably.
When to use: teaching or answering questions about "audit logging on every state change".
When NOT to use: task-level evidence hashing (that is GOV-132).
Key concepts: immutable audit log, state transitions, append-only.

Completion criteria

Learner passes the scenario knowledge check and can point to the system state that satisfies GOV-151's acceptance criterion.

Module: LEARN-MOD-005 (Cross-Cutting & Hardening)
Provenance: LEARN-MAP-001 · Generation standard: LEARN-STD-002
Next: LEARN-LSN-030