The foundational UK sovereign-AI patents are filed
21 UK patent applications. 675 cryptographically signed claims. One inventor (Micky Irons). One filing reference (UK00004373277).
Ten of those twenty-one are load-bearing for any vendor building sovereign AI infrastructure for UK government, healthcare, defence, finance, or regulated enterprise.
## The load-bearing ten
1. **Trust Agent (Patent 01)** — privacy router and tamper-evident audit ledger
2. **Sovereign Security Framework (Patent 03)** — egress firewall, injection detection, per-tool rate limits
3. **Adaptive Multi-Tenant OS (Patent 04)** — cryptographic tenant isolation with voice-gated switching
4. **Privacy-Preserving Sovereign RAG (Patent 05)** — clearance-ceiling retrieval; absence indistinguishable from nonexistence
5. **Quantum-Safe Attestation, ML-DSA-65 (Patent 08)** — FIPS 204 signed audit ledger
6. **Typed-Action Ontology (Patent 12)** — hardware-bound actor identity, inverse-action schema
7. **First-Class Actions with Compensating Rollback (Patent 14)** — regulator-issued retroactive undo
8. **Decision Lineage and PQ-Signed Audit Ledger (Patent 16)** — causal DAG, regulator-verifiable
9. **Granular Row/Column ACL (Patent 18)** — per-voiceprint revocation with retroactive flagging
10. **Sentinel (Patent 21)** — universal AI-agent action interceptor + signed audit (91 new claims)
## An open invitation to collaborate
We would rather build with you than around you. The portfolio above was filed to make sovereign AI in the UK structurally British and structurally auditable. It was not filed to shut anyone out.
We are explicitly open to:
- Licensing collaborations with vendors building sovereign AI for UK government, NHS, defence, financial regulators, or regulated enterprise
- Joint architecture work with primes tendering for UK sovereign-AI contracts
- Engineering partnerships to integrate specific Mickai primitives (clearance-ceiling RAG, Sentinel, post-quantum signed audit) into existing platforms
- Defensive cross-licensing with peer sovereign-AI vendors to keep the substrate open for British operators
The contact is **press@mickai.co.uk**. The licensing path is direct, from the inventor.
[Read the full article on mickai.co.uk](https://mickai.co.uk/articles/twenty-one-uk-sovereign-ai-patents-collaboration-open)
*Originally published at [mickai.co.uk](https://mickai.co.uk/articles/twenty-one-uk-sovereign-ai-patents-collaboration-open).*
The foundational UK sovereign-AI patents are filed. The collaboration door is open.
Dev.to / 5/3/2026
📰 NewsDeveloper Stack & InfrastructureSignals & Early TrendsIndustry & Market MovesModels & Research
Key Points
- The UK has filed “foundational sovereign-AI” patent applications, including 21 filings and 675 cryptographically signed claims tied to a single inventor, Micky Irons.
- Ten key “load-bearing” patents are positioned as essential building blocks for vendor-grade sovereign AI infrastructure supporting UK government, healthcare, defense, finance, and regulated enterprises.
- The core technical themes include privacy-preserving routing and tamper-evident audit ledgers, cryptographic multi-tenant isolation, secure egress/firewalling with injection detection, and clearance-ceiling retrieval for sovereign RAG.
- Additional pillars cover quantum-safe/post-quantum attestation and signed audits, hardware-bound actor identity and typed ontologies, rollback/compensation mechanisms for regulator-issued retroactive undo, and universal AI-agent action interception (“Sentinel”).
- The inventor explicitly invites collaboration via direct licensing, joint architecture work for UK sovereign-AI tenders, engineering partnerships to integrate specific primitives, and defensive cross-licensing to keep the substrate open for British operators.
Related Articles
Black Hat USA
AI Business
Building a Shopify app with Claude Code — spec-driven development and pricing design
Dev.to
From Chaos to Clarity: AI-Powered Client Portals for Designers
Dev.to
Stuck in the Mud (and Loops!) - Kiwi-chan Devlog #7
Dev.to
I Used to Treat AI Like a Search Engine. Then I Realized I Was Doing It Wrong.
Dev.to
