Briefing
Reference 12 · Primer · About 6 minutes
Download the MP3 · Linda, an AI voice, reads a script written from the sources below.
Written from the DTA's published documents and checked on 11 November 2026. AIRA is paraphrased, not reproduced (CC BY 4.0). Check the current text before relying on it.
Before we record, every claim the hosts make is checked against the sources (this table was last updated 11 November 2026). Confirmed means a primary source or two independent reports; Reported means one party says so; Partly right, Disputed, Unverified and Not yet known mean what they say, and the hosts say so on air. This is the table as we left it.
The rules that apply to AI in Australia and for Australian organisations with European exposure, and the practical work each one calls for.
These are Agile Insights AI Strategy & Governance offerings. Which of them you need depends on where your organisation starts.
Sign up for our podcast at agile-insights.com.au.
Linda The federal government now has one blueprint for how every AI system in the Commonwealth should be designed, bought and governed. It is called the AI Reference Architecture. By the end of this episode, you will know what it asks of agencies. You will also know what it means for suppliers, and where it stops.
Linda First, what it is. The Digital Transformation Agency, the D T A, published the AI Reference Architecture in October 2026. People call it AIRA. It is a reference architecture, which means a shared structure and vocabulary, not a product list. It mandates no products, platforms or designs. But the agency says agency architectures "should be in line with" it. So it is not a law, and it is not optional in the casual sense either. It is the expected shape. A companion guide with four worked scenarios comes with it.
Linda The problem it solves is fragmentation. A department running a chatbot must satisfy the responsible use of AI policy, the Privacy Act and the Archives Act. Then come the protective security framework and the Information Security Manual. Until now, each agency read those rules on its own and drew its own conclusions. AIRA translates them into one set of reusable patterns. Picture two agencies buying the same call centre product. Without a common frame, each writes its own assessment from scratch. With one, they can compare like with like.
Linda Who uses it? Chief AI officers and executives use it to frame strategy and investment. Architects use it to design and review systems. Procurement teams use it to compare vendors. Risk, audit and cyber teams use it as a common baseline. That matters when an architecture board meets, or a system needs its authority to operate. The timing matters too. By the fifteenth of December 2026, Commonwealth agencies need a register of their AI use cases and named owners. They also need staff training, and impact assessments under way. AIRA gives them a way to describe the systems they are assessing.
Linda So what is in it? Four ideas carry it. The first is a functional stack of five layers. They are experience, application and orchestration, intelligence and analytics, data and metadata, and platform and infrastructure. Every AI system touches all five. The second is nine trustworthiness and assurance domains. They include fairness, privacy, safety, traceability and sustainability, and they are designed in, not bolted on afterwards. Sustainability here includes how dependent you are on one vendor, and how you would leave.
Linda The third idea is human agency, oversight and control. AIRA is clear that this does not mean a person approving every action. It means automation running inside limits that people can watch, pause, revise and revoke in time. The fourth idea is control points. For each part of a system, an agency either only governs it, configures it, or designs it. For a product like Microsoft 365 Copilot, more of the system is govern only than anything else. So the real work is evidence, contract terms and the few settings you actually control.
Linda How does it connect to the rest of the stack? AIRA sits between policy and solution design. Above it sit the AI Ethics Principles, the responsible use policy and the AI technical standard, whose requirements AIRA traces into architecture. Below it sits each agency's own solution. For security and privacy, it says it will defer to existing guidance, such as the Information Security Manual and the privacy regulator's advice. It never mentions I S O, I E C, 42001, the AI management system standard. So any link to that standard is one you draw yourself.
Linda Getting started. First, list your AI use cases and draw each one on the five layers. Second, for each part, mark whether you govern, configure or design it, and be honest about how much is govern only. Third, check that you can roll back models, data and settings. And make sure people who cannot or will not use AI still have another way in. The primary sources are the AI Reference Architecture and its companion guide on the digital dot gov dot A U website. Both are linked in the show notes.
Linda Now, currency. As at November 2026, AIRA is at version one point zero, published in October. The D T A says its capability groups and components are expected to evolve, and agency experience feeds back into it. Expect revisions, and more detailed patterns. Check the current text before you rely on any detail here.
Linda In short, AIRA is the shape every Commonwealth AI system is now expected to take. Industry commentators expect its language in government tenders. If you'd like to know more, sign up for our podcast at agile-insights.com.au.
All of the reference series (16) · Follow AI Governance Reference in Apple Podcasts or any podcast app
Everything from Agile Insights: briefings, Making You Think and the reference series