Briefing
Reference 0 · Primer · About 7 minutes
Download the MP3 · Leonard, an AI voice, reads a script written from the sources below.
Written from public sources, checked on 10 October 2026 and updated on 11 November 2026. The standards are paraphrased, not reproduced. 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.
Three layers, from the data underneath, through the governance of AI itself, to the rules that apply. For government, a fourth piece now sits between the rules and each agency's own design: the DTA's AI Reference Architecture. Each episode in this series covers one piece.
These are Agile Insights AI Strategy & Governance offerings.
Sign up for our podcast at agile-insights.com.au.
Leonard There are dozens of standards, laws and frameworks that claim to govern AI, and nobody has time to read them all. This episode is a map. By the end you will know how they fit together in three layers, which ones matter first for your role, and where to start listening. This is as at November 2026.
Leonard First, what the series is. It is a set of short reference episodes from Agile Insights, each about five or six minutes, each covering one standard, framework or rule. Every episode follows the same pattern: what it is, the problem it solves, who uses it, what is in it, how to get started, and where it stands today. Each one is checked against the publisher's or regulator's own pages before it goes out, and each says plainly that the current text must be checked before you rely on it.
Leonard The problem the map solves is a familiar one. A board asks, are we compliant with AI regulation? An executive hears four names in one meeting, a standard, a framework, a law and a guidance note, and they all sound like the same thing. They are not. Some are laws you must follow. Some are standards you can be certified against. Some are voluntary guidance. Some are bodies of knowledge. Knowing which kind you are looking at is half of the answer.
Leonard Who is it for? Directors, chief executives, and the risk, privacy, security, data and technology leaders who brief them. It is written for people who need to make decisions and ask good questions, not for people who will implement every clause.
Leonard Now the map itself, in three layers. Think of a swimming pool. The bottom layer is the water. That is your data foundations. AI is only as trustworthy as the data under it. Two episodes cover this layer: the data management frameworks D A M A D M B O K and D C A M, and the I S O, I E C, 5259 series on data quality for machine learning.
Leonard The middle layer is the swimmer. That is AI governance itself: how an organisation owns, runs, checks and improves its AI. Six episodes sit here. I S O, I E C, 42001 is the management system standard you can be certified against. The N I S T AI Risk Management Framework gives you a shared language for risk. I S O, I E C, 23894 is guidance on how to manage AI risk. I S O 27001 and 27701 are the security and privacy standards that many organisations already hold, and that give you a head start. Then two episodes on agents: governing AI agents in general, and the Microsoft Agent Governance Toolkit, a tool that enforces rules at runtime.
Leonard The top layer is the pool rules. That is the law and regulation that applies where you operate. Here you will find the Privacy Act duty on automated decisions that starts on the tenth of December 2026, Australia's national AI guidance and its six essential practices, the European Union AI Act, the sector rules for industries such as government, finance and health, and work health and safety duties for digital work systems. For the Commonwealth, two more episodes sit here. One covers its own AI rulebook: the responsible use policy, the AI technical standard and the plan for the public service. The other covers security for government AI: the protective security framework and the Information Security Manual. Rules are the layer that can change quickly, so check these episodes first for currency.
Leonard Between the pool rules and the swimmer, government now has a fourth piece: the lane ropes. That is the D T A's AI Reference Architecture, called AIRA, published in October 2026. It turns the rules above into a shared design that every agency's AI system can follow. It mandates no products or designs. But agency architectures are expected to be in line with it. Reference 12 covers it.
Leonard There is one more episode that sits outside the layers: a balanced look at the environmental footprint of AI, in the briefing series under the title, are data centres evil.
Leonard How does this connect to AI in your organisation? Each layer answers a different question. The rules layer asks, what must we do? The governance layer asks, how do we run AI so that we can show we did it? The data layer asks, can we trust what goes in? An organisation that only studies the rules ends up with paperwork. One that only builds governance may miss a legal deadline. One that ignores the data finds out the hard way.
Leonard Where should you start? Four paths. If you are on a board or in the executive team, start with the rules: the Privacy Act episode, then Australia's national guidance, then the European Union AI Act if you have European exposure. If you run risk, security or privacy, start with the governance layer: 42001, then the NIST framework, then the agent episodes. If you own data, start at the bottom with the two data episodes, then listen to 42001 to see where your work plugs in. If you work in government, or sell to it, take the fourth path. Start with Reference 13, the Commonwealth rulebook. Then Reference 12 on AIRA, then Reference 14 on security. Reference 15 is coming next, on the quieter duties: records, data ethics, digital experience and cloud. Wherever you start, the show notes for each episode link to the primary sources.
Leonard A word on currency, as at November 2026. Most of these episodes were written in October 2026 from public sources. The government episodes followed in November. The standards themselves change slowly. The rules and the agent guidance change fast. We plan to review the series each quarter, and the show notes for each episode carry the date it was checked. Always check the current text before relying on anything you hear.
Leonard To recap: data is the water, governance is the swimmer, and the rules are the pool. For government, AIRA is the lane ropes. 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