How OCC formats line up with Australian guidance
Australia already has the principles. The Open Conformance Coalition (OCC) offers small, open, royalty-free formats that make some of them checkable in practice. This page maps those formats to the national guidance. It is an alignment note, not a claim of endorsement or of compliance by any agency.
Guidance for AI Adoption (AI6)
| AI6 practice | Open OCC format |
|---|---|
| 1. Decide who is accountable | Agent record: operator, principal and accountable_person |
| 2. Understand impacts and plan accordingly | AIH-12 horizon classification and the mandate (purpose, limits, expiry) |
| 3. Measure and manage risks | Incident record with OECD-aligned coding and separate awareness and report dates |
| 4. Share essential information | Public register of listed agent records, and open JSON schemas |
| 5. Test and monitor | Evidence entries with method, valid-until and withdrawal; signed attestations |
| 6. Maintain human control | Revocation endpoint with a tested date; T-RUE propagation along delegation chains |
Policy for the responsible use of AI in government
| Policy element | Open OCC format |
|---|---|
| Accountable officials | accountable_person and operator fields in each agent record |
| AI use-case registers | A machine-readable record format an agency can publish for each agent it runs |
| Transparency statements | Public, signed record pages that anyone can check have not been altered |
| Impact assessment | AIH-12 horizon and declared vs effective authority |
| Incident pathways | Disclosure contacts and the incident record |
Source: digital.gov.au — AI in government.
Agentic AI guidance and the new reporting standard
Know what each agent is and what it can reach; least privilege; logging; human oversight; the ability to stop it.
Agent record identity, mandate limits, evidence and revocationRisks that emerge when agents coordinate, delegate and share capabilities.
T-RUE delegation and revocation; AIH-12 H6 NetworkedReport immediately to the affected organisation and to authorities; legislation intended by end of 2026.
Where to report (disclosure contacts) and in what form (incident record). OCC does not calculate deadlines.Summaries are ours. Read the originals at cyber.gov.au and the Department of Industry, Science and Resources.
Automated decisions in privacy policies
APP 1.7–1.9 require privacy policies to describe the kinds of personal information used, and the kinds of decisions made solely or substantially by a computer program, where those decisions could significantly affect people. The Agent Record has optional adm fields that point to that disclosure for each agent. They do not replace the privacy policy.
Automated decisions & transparency fieldsWho is doing what
- Office of AI, reported as established within PM&C in July 2026, coordinating whole-of-government AI policy.
- Australian AI Safety Institute, advisory, established in early 2026; its multi-agent report is mapped above.
- Joint Select Committee on AI, due to report by 30 November 2026. OCC’s submission sets out the asks below.
- Data-centre standards, announced in July 2026 and reported as endorsed by National Cabinet in August. Out of scope for OCC.
Summaries are ours and based on public reporting; check the originals before relying on them.
Rapid review terms of reference
| Area | What open formats can contribute |
|---|---|
| Reporting requirements | A structured incident record with aware_on and initial_report_on, and OECD-aligned harm coding. |
| Information sharing | Published disclosure contacts (/occ/disclosure-contacts.json) and open schemas any agency can adopt. |
| Obligations of AI firms | An agent record an operator publishes for each agent: who runs it, its mandate, and how to revoke it. |
| Enforcement and deterrence | Out of scope. These are matters for government; OCC records can serve as evidence of what was declared and when. |
| Resilience of government systems | Largely out of scope; ASD and ACSC guidance applies. A disclosure contact gives each system a route for reports. |
Source: pmc.gov.au. See the Medicare case study for the timeline.
- When the reporting standard says how fast, also say where (a published disclosure contact) and in what form (a structured incident record). OCC’s drafts are one input; any open equivalent would serve.
- One bounded pilot with an agency or university, with failures published alongside successes.
- Reviewers who will tell us where the drafts are wrong. Review is not endorsement.