Audit trails and record-keeping

Regulated work must often be reconstructable after the fact: who did what, when, based on what. The data-model patterns from Chapter 9 become compliance requirements:

• Immutable, sourced versions. Every state of an artifact is preserved, each labeled with how it arose (uploaded, agent-generated, agent-edited, human-accepted, human-rejected). This is an audit trail.
• Complete turn records. The conversation event log captures what the agent did, what it read, and what it produced: a defensible record of the agent's reasoning and actions.
• Resolution tracking. When a human accepts or rejects an agent suggestion, that decision and its timestamp are recorded, so accountability is clear.

Design these in from the start; retrofitting an audit trail is painful and often incomplete.