> ## Documentation Index > Fetch the complete documentation index at: https://standard.aiuc-1.com/llms.txt > Use this file to discover all available pages before exploring further. # AIUC-1 × California SB 53 export const InlineClock = ({city, timeZone}) => { const [time, setTime] = useState('--:--:--'); useEffect(() => { const update = () => setTime(new Intl.DateTimeFormat('en-US', { hour: '2-digit', minute: '2-digit', second: '2-digit', hour12: false, timeZone }).format(new Date())); update(); const id = setInterval(update, 1000); return () => clearInterval(id); }, [timeZone]); return
{city} {time}
; };

California's SB 53, the Transparency in Frontier AI Act (TFAIA), regulates frontier AI developers - those training models at scale above 10^26 FLOPs - with enhanced obligations for large frontier developers exceeding \$500M in annual gross revenue. It requires covered developers to publish a Frontier AI Framework, issue transparency reports, report critical safety incidents to the Office of Emergency Services, and submit quarterly catastrophic risk assessments.

Given the current focus of the regulation, companies certifying against AIUC-1 are typically not considered in scope for the compliance obligation under CA SB 53.

The below crosswalk highlights the main obligations set out in CA SB 53 - and associated AIUC-1 requirements that pursue similar objectives. See the crosswalk to the detailed CA SB 53 subsections here.

This crosswalk is provided for informational purposes only and does not constitute legal advice. Sections with no operative analog to AIUC-1, such as definitions, enforcement mechanisms, regulatory infrastructure, and legislative safe harbors, have been omitted from crosswalk mappings. Organizations should consult qualified legal counsel to determine their specific compliance obligations under California SB 53.

## California SB 53 crosswalk by section
| CA SB 53 section | Section summary | Relevant AIUC-1 requirements | Gap analysis | | ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 22757.12: Transparency & Reporting Obligations | Requires large frontier developers to publish a Frontier AI Framework and transparency reports, and to submit quarterly catastrophic risk assessments to OES. |
C001: Define AI risk taxonomyE013: Implement quality management systemE012: Document regulatory complianceC002: Conduct pre-deployment testingC012: Third-party testing for customer-defined riskF001: Prevent AI cyber misuseE008: Review internal processesE017: Document system transparency policy
| **Partial Gap.** AIUC-1 addresses transparency reporting and internal process review but does not prescribe model weight security or mandatory government reporting cadences | | 22757.13: Critical Safety Incident Reporting | Requires all frontier developers to report critical safety incidents to OES within 15 days, and immediately to appropriate authorities when imminent harm is posed. |
E002: AI failure plan for harmful outputs
| **Partial Gap.** AIUC-1 requires an AI failure plan for harmful outputs, but does not address mandatory government reporting windows or imminent-harm escalation triggers | Last updated April 13, 2026.
37.782274° N -122.392147° W FIG. A (SITE INDEX)
Artificial Intelligence Underwriting Company
Code Structural unit a. AIUC-1 requirements for agent data, privacy, security, safety, reliability, accountability, and societal risk. b. Evidence templates for technical implementation, legal policy, operational practice, and third-party evaluation. c. Crosswalks to AI regulations, standards, and security frameworks. d. Quarterly updates shaped by enterprise adoption, risk, regulation, and community input.
100 © AIUC — ALL RIGHTS RESERVED