ISO 42001 Platform Statements
Platform Statements are the platform-default capability narratives that pre-fill every tenant's ISO/IEC 42001:2023 Annex A coverage. They tell the truth about which controls the RAIC platform itself partially or fully discharges on behalf of the customer — but they are always marked auto-suggested until a human reviewer in the tenant accepts them.
Why we separate auto-suggested from reviewed
The Annex A report's primary Full Coverage % KPI counts only rows that a human inside the tenant has reviewed. Auto-suggested rows are surfaced in a separate Including auto-suggested metric and wear a pill on the control card so auditors can distinguish platform-prefilled evidence from tenant-confirmed evidence.
Editing a statement
From Super Admin → Account Tools → ISO 42001 Statements:
- Click any control row to open the editor.
- Adjust the default status (Full / Partial / Gap / N/A) and write the evidence summary in plain English.
- Save Draft records the change without bumping the version (audit code
ISO_42001_PLATFORM_STATEMENT_EDITED). - Publish bumps the version, sets
published_at, and emitsISO_42001_PLATFORM_STATEMENT_PUBLISHED.
Re-seeding tenants
Re-seed all tenants calls the reseed-iso42001-platform-statements edge function. It updates every tenant row where auto_suggested = true AND the row's storedauto_suggested_version is older than the platform statement's current version.
Reviewed rows (auto_suggested = false) are never overwritten. The action is audited at the platform level (ISO_42001_PLATFORM_STATEMENTS_RESEEDED) and mirrored into each affected tenant's activity log.
Version history
Every save and publish writes a row to iso_42001_platform_statement_history via aSECURITY DEFINER trigger. Re-seed actions append a synthetic reseeded row per affected control. Click the history icon on any row in the editor to view the last 50 entries.
