AI Audit Exchange
Go back

Guide · By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026

SB 813 / AB 1405 and the AI Auditor Registry, Explained

What is the AI Auditor Registry?

The AI Auditor Registry is the state framework reported under California's SB 813 / AB 1405 to stand up by 1 January 2029, alongside 10-year audit-record retention. AI Audit Exchange references the framework as market context, stated at the confidence of law-firm secondary sources, and distinguishes it sharply from the platform's own private vetting workflow, which records a listing decision and is not a state licence or registry entry.

What the framework is reported to do

As reported, SB 813 / AB 1405 does two things that reorganise the audit market. First, it stands up an AI Auditor Registry by 1 January 2029 — a state-level roster around which the independent-audit profession for California's regimes can formalise. Second, it attaches 10-year audit-record retention to the framework, settling the longevity question for audit records at the level of the regime itself. Both moves matter to everyone in this guide's world: auditors gain a formal professional horizon; auditees gain a definite retention planning number; platforms like this one gain a market whose record-keeping expectations are stated in years, plainly. We restate the framework at the confidence level of concordant law-firm secondary sources; primary texts were not opened by us.

What the registry is not

The registry is not this platform, and this platform is not the registry's front door, affiliate or preview. AI Audit Exchange states the disclaimer in its footer, its terms and its product copy: not affiliated with or endorsed by any state registry, agency or government body. Its auditor directory is a private marketplace with a private gate. Any auditor, agency or platform that blurs that line — implying listing here confers state standing — misleads its market in a way the record will eventually correct. Auditees should treat registry-status claims as claims requiring the registry itself as their source, exactly as credential claims require fit conversations as theirs.

Vetting here vs registration there

The platform's vetting is an owner-run workflow deciding whether a registration is listed in its directory: pending, vetted or rejected states, credentials recorded as the auditor states them. Whatever the state registry becomes, its registration will be the state's act under the state's criteria. The two can coexist the way a professional association's directory coexists with a licence: different issuers, different meanings, both legible if nobody inflates either. Auditors building practices now should hold both ideas separately in their own marketing — 'vetted and listed on AI Audit Exchange' says something true and sufficient; anything stronger awaits the registry's own facts. The platform's workflow is detailed in auditor vetting.

The 10-year retention signal

Of the framework's two reported elements, retention may touch more organisations more deeply. Ten years reframes audit records from engagement paperwork into institutional memory: systems must keep records readable, verifiable and governed — retention settings, holds, manifests, hash verification — across staff generations and tool migrations. The Exchange is built to that number: per-room retention up to 10 years on Pro and Team, manifests that print retention and hold status on their face, seals that let a decade-old record prove itself in minutes. Whether or not the framework's final form matches the reports exactly, building to the reported horizon is the prudent read of the signal.

What auditees should do with the registry's approach

Three preparations serve under any final form. Keep your rooms registry-agnostic: period-organised, sealed, manifested records satisfy any examiner the future sends, state-recognised or private. Build auditor relationships before the registry-era concentration: vetted auditors met over prepared rooms in 2027 and 2028 are relationships, not transactions, by 2029. And keep your own status claims as clean as you require auditors' to be: your organisation's readiness is a set of room facts (completeness, freshness, retention), not a posture. When the registry stands up, organisations whose records were already in order will experience it as an administrative event rather than a reckoning.

What auditors should do with it

For auditors, the framework's approach is a practice-building window with a known shape. Establish the listing you can hold today — this platform's vetted directory — with claims stated to survive a decade of fit conversations. Build the record that will matter under any registry: engagements worked in rooms, with sampling discipline and threads that demonstrate method. Watch the registry's own publications for its criteria as they emerge, from primary sources, and treat every secondhand summary (this guide included) as a pointer, not a text. The auditors best positioned at the registry's arrival will be those whose private-market record already reads the way a registrar would want it to.

Five actions to take

  1. Keep the two worlds distinct in every document: state registry (reported, from 1 January 2029) vs this platform's private vetting and directory.
  2. Never market platform vetting as state standing — for yourself or anyone else.
  3. Build retention to the reported 10-year horizon now: settings, manifests, holds and annual reviews.
  4. Meet vetted auditors over prepared rooms before the registry-era demand concentrates.
  5. Follow the registry's own primary publications as they emerge; treat summaries, including this one, as pointers.

Worked example

A fictional audit practice, Hallowed Ground Assurance — a two-partner firm — plans its 2027 around the reported framework without ever blurring it. Its directory listing states its claims plainly and describes its status accurately: vetted on a private platform, full stop. Its internal plan has a page titled 'Registry watch': primary sources to check quarterly, criteria to respond to when published, and a standing rule that no client material will ever describe the firm's platform status as public standing.

By the framework's reported arrival date, the firm has six room-worked engagements behind it, each with sampling records it would be content for any registrar to read. If the registry's criteria reward demonstrated, record-based practice, the firm is ready in the only way that cannot be faked quickly: retrospectively. That positioning — not any claim made in 2027 — is what the framework's approach was actually offering to those who read it early.

Frequently asked questions

Is AI Audit Exchange the AI Auditor Registry?

No. The platform is a private product, not affiliated with or endorsed by any state registry, agency or government body. Its vetting is an owner-run listing decision, not a state licence or registry entry.

When does the registry stand up?

As reported in concordant law-firm secondary sources, by 1 January 2029, under the SB 813 / AB 1405 framework. We state that at the sources' confidence level; consult primary sources and counsel for your position.

Does being vetted here count toward registry status?

The platform makes no such claim and cannot. Registry criteria are the state's to publish. A record of rigorous, room-based engagements is good preparation under any criteria — which is a statement about preparation, not about credit.

Where does the 10-year retention figure come from?

The framework is reported with 10-year audit-record retention attached. The platform's per-room retention up to 10 years on paid plans is built to that reported horizon.

What should I do now, before the registry exists?

Auditees: build period rooms and meet vetted auditors early. Auditors: get listed with defensible claims and build a room-worked record. Both: keep every status claim precisely sourced.

Keep reading

All AI Audit Exchange guides · Auditor directory · About AI Audit Exchange · Security · Pricing · AI Audit Exchange home · Previous: California AI Audit Timeline: 2028–2029, Year by Year · Next: Who Needs a California AI Audit? Working Out Your Position

How to Run an Internal AI Audit Readiness Review · Evidence Room Security: How Access and Accounts Are Controlled · API Keys for Audit Evidence Workflows: A Practical Guide