Skip to main content
IORP II requires that all regulated actions are traceable and attributable. This page documents how AI-generated content is audited throughout its lifecycle — from generation to broker approval to execution.

Audit Trail Overview

Change Proposals Table

The change_proposals table is the primary AI audit record:

Advice Record Linkage

SoS drafts generated by AI are linked to advice records in advice_records:

What Is NOT Logged

AI prompt content is deliberately not stored in audit logs:
  • System prompts are code — versioned in git, not in the database
  • User message content is not persisted (may contain personal data)
  • AI response content is captured only through the structured proposedChanges delta and the sosDocument
This prevents audit logs from becoming a secondary store of personal data sent to AI providers.

Model Version Tracking

change_proposals.modelId records the exact model used for each generation. This enables:
  • Retrospective review if a model version is found to have produced non-compliant output
  • Support for model deprecation audits — find all proposals generated by a deprecated model
  • Compliance reporting on AI usage across the platform

Regulatory Compliance

The AI audit trail satisfies the following regulatory requirements:

SuperAdmin Audit Access

SuperAdmin users can query the full AI activity across all tenants for platform-level compliance reviews. All such accesses are themselves audit-logged.