The Local Government Association published its AI principles for English councils. The principles are clear, well-drafted, and broadly endorsed: AI in council services has to be transparent to the resident, accountable to the elected member, lawful under data-protection law, and proportionate to the harm the use case can cause. Three hundred and forty-three councils across England are now expected to procure to that standard.
The structural problem the principles do not solve is that each council asks the procurement question alone, of a market that sells vertically integrated stacks. The vendor will sell the model, the hosting, the audit, the consultancy, the integration, and the support together. The audit primitive the LGA principles imply does not exist as a separable component the council can purchase, run, and own.
This article sets out what the primitive looks like, why it has to be vendor-neutral, and why the substrate to ship it is already filed at the UK IPO.
The procurement reality across the 343
A district council in the East Midlands procures a planning-assistance AI from a vendor whose hosting sits on a foreign hyperscaler tenancy. A metropolitan borough in the North West runs a social-care triage assistance tool inside a managed service provider's environment. A county council in the South West uses an AI-enhanced revenues-and-benefits product that ships with its own audit module the council does not have read access to.
Each of the three is in compliance with the LGA principles as the principles are written. None of the three holds the audit record under its own key. None of the three can re-verify a decision the AI made independently of the vendor that supplied the AI. The Information Commissioner cannot recover the controller-side evidence from any of the three without engaging the vendor.
When the next ICO inquiry, the next public-inquiry referral, or the next ombudsman referral hits one of the three, the council answers from the vendor's records. That is not the structural posture the LGA principles describe.
What the council actually needs
The council needs an audit primitive that is, by construction, independent of the model vendor, the hosting provider, and the managed service partner. The primitive has to record the AI's decision, the input the decision was made against, the policy gate the decision passed, the operator's signed concurrence where relevant, and the inverse action available if the decision is later retracted.
The primitive has to be vendor-neutral. The council should be able to adopt it on Tuesday and continue to procure model, hosting, and support from the existing vendors on Wednesday. The audit primitive should not require ripping out the vendor stack.
The primitive has to be operator-side. The audit record has to live in the council's perimeter, under the council's keys, in a form the council can present to an inspector without involving any of the suppliers.
The primitive has to be durable. A record sealed under classical cryptography in 2026 is a record whose evidential weight degrades as the post-quantum transition approaches. The signing scheme has to be FIPS 204 ML-DSA-65 from inception.
The Open Audit Record as the answer
The Open Audit Record is the engineering primitive the LGA principles imply. It is filed at the UK Intellectual Property Office under GB2610413.3 as part of the Mickai portfolio. It is a vendor-neutral, post-quantum signed, hardware-bound, browser-verifiable audit record format.
The council adopts it by deploying the lightweight verifier and the operator-side signing harness on hardware the council controls. The signing harness sits between the council's existing AI vendors and the council's audit retention. Every action the vendor's AI takes is written through the harness, signed under the council's key, and retained in the council's perimeter. The vendor stack continues to operate. The audit record lives where the LGA principles imply it should live.
The verifier is browser-resident WebAssembly. An ombudsman, an ICO inspector, or a councillor can verify any record against the council's published key, offline, in a browser, without engaging any vendor.
The Mickai Sovereign Intelligence Operating System for councils that want the full substrate
For a council that procures to a tighter spec, the full Mickai Sovereign Intelligence Operating System ships the audit primitive alongside the 50-brain cooperative, the runtime perimeter on every agent, the policy-as-code engine, the inverse-action ontology, the federated fleet protocol, and the hardware-attested identity arrangement.
A council on the SIOS does not need a separate planning-assistance product, a separate social-care triage product, and a separate revenues-and-benefits product. The use case is configured against the substrate. The audit chain is uniform. The verifier is uniform. The data residency is uniform. The procurement document is shorter.
Federation across councils is then a primitive, not an integration project. Two councils with the SIOS can cooperate on a regional planning case, a regional safeguarding case, or a regional procurement decision under signed federation records the LGA can audit centrally.
The case the LGA, the DLUHC, and the Crown Commercial Service can put
A central procurement frame that names the Open Audit Record as the audit primitive for council AI, that names the SIOS as the substrate for councils that want the full structural posture, and that uses Crown Commercial Service to underwrite the deployment cost across the 343, would land the LGA principles as structural reality rather than as a policy expectation.
The substrate is on the public register. The 101 filed UK patent applications cover the primitives. The procurement vehicle is in place under RM6263. The councils are asking the question. The answer can be supplied centrally rather than three hundred and forty-three times.
The LGA principles are the right principles. The Mickai Sovereign Intelligence Operating System is the substrate that satisfies them. The Open Audit Record is the primitive a council can adopt without changing its current stack.
The next step is procurement, not policy.
