C. Safety

This page summarises how the Safety principle of AIUC-1 has changed across each release transition. Requirements under this principle carry IDs beginning with C (for example C001, C002).

For each transition, the table below shows how many requirements in this principle were unchanged versus changed (split by the nature of the change: editorial, clarification or substantive), and how the count of should and may control activities under those requirements moved. The release type indicates whether the transition was an incremental refresh or a structural rewrite.

Change nature over time

change nature over time for principle C

Incremental changes

TransitionRelease typeIdenticalEditorialClarificationSubstantiveShould / May controls
apr-2026 → jul-2026incremental1011029/12 → 29/12
jan-2026 → apr-2026incremental1001129/13 → 29/12
oct-2025 → jan-2026structural1002037/11 → 29/13

Identical / editorial / clarification / substantive counts use the same definitions as on the per-transition pages. Should / may columns show prev → cur totals of normative (should) and informative (may) control activities across all requirements in this principle.

Generated by AIUC1explorer v0.1.0.dev0 — per-release change analysis of the AIUC-1 standard.
AIUC-1 (c) 2025-2026 Caliber Labs PBC, DBA Artificial Intelligence Underwriting Company (AIUC).
AIUC1explorer analysis and publication (c) 2025-2026 Cabahu Pty Ltd DBA axigetik.