The work, in print.
Nine papers shipped since the start of 2026. Each one comes out of a live deployment, not a whiteboard.
- 012026-06-07 · MAIA Research
Escalation that arrives.
Most systems can raise an alarm. Almost none can guarantee it lands somewhere a human will see it, own it, and be able to act. We argue an escalation is a transfer of custody, not a notification — and that it is only real when it survives a reload, reaches a second account, and carries enough to act on. We catalogue the three ways escalations die, describe the spine that makes one durable and owned, and give you the four-step test to run in any procurement.
Read - 022026-05-30 · MAIA Research
Sovereignty is an architecture, not a flag.
Every vendor we audit this year calls itself sovereign. Most of them mean one of three things — their data centre is in the right country, their support staff is cleared, or the customer gets a private VPC. None of those is sovereignty. We lay out the four architectural properties a system actually needs before the word means anything: residency you can prove, keys the customer can revoke without our help, an audit chain that survives the vendor going away, and a learning loop where the customer keeps the deltas.
Read - 032026-05-26 · Mohamed Yousuf
What we got wrong about workforce planning.
Ten years of building rosters for airlines and a film studio, and the tools were never the problem. We had every system money could buy. What we did not have was a way to act on the schedule once it was wrong. A roster gets cut at 0600; by 0700 three operators have pushed back manually in three different systems and nobody has reconciled them. This is the part I have not seen written down — the gap between the planning surface and the operating surface, and why the gap is the actual workload.
Read - 042026-05-19 · MAIA Research
Policy-by-Proof.
Evidence-Bound Autonomy. Every agent action must produce its proof packet — typed inputs, named policy clauses, classification floor, reversibility guarantee, signature — before it executes. The architecture, the trade-offs, and why this is the only honest model for defence-grade AI.
Read - 052026-05-19 · MAIA Research
The Living Ontology.
An operational ontology that evolves continuously from observed operator and agent behaviour, with tamper-evident governance. Phase 1 ships agent-emitted Evolution Proposals, severity-aware HITL routing, reversible patches, federated learning by delta. We describe the architecture, the heuristics, the moat — and why no frozen-ontology platform can catch up.
Read - 062026-04-22 · MAIA Research
The State of Operational Decision-Making, 2026.
A field survey of 217 operating environments across government, defence, and enterprise. We measure the gap between when a decision-relevant signal arrives and when an operator acts on it. The median is 41 hours. The 90th percentile is over a week. We show why dashboards have made this worse, not better, and what an operating substrate has to do to close the gap.
Read - 072026-03-14 · MAIA Research
Decision Latency Benchmark, 2026.
We benchmark seven AI-agent stacks against 1,400 real operational decisions drawn from logistics, healthcare staffing, and energy dispatch. We score on signal-to-draft latency, evidence completeness, and policy-conformance under load. MAIA's reference stack reaches a verified decision in 11 minutes at p50, with full lineage. No competitor closes the loop under one hour without losing provenance.
Read - 082026-02-05 · MAIA Research
Multi-Domain Fusion at Sovereign Scale.
A methodology paper on fusing classified, controlled, and open signals into a single operational picture without leaking provenance across clearance boundaries. We describe a typed fusion graph, a per-edge clearance gate, and a redaction kernel that lets the same agent reason across boundaries while emitting evidence packets distinct to each cleared audience.
Read - 092026-01-18 · MAIA Research
The Operational Ontology.
Operations are not rows in a warehouse. They are sites, crews, assets, jurisdictions, policies, costs, and cadences — with typed relationships, lifecycle states, and authority boundaries. We propose a first-class operational ontology as the lens every agent reads through. We define the type system, the editing surface for operators, and the rules for safe drift.
Read
The next chapters.
Three threads the team is pulling on right now. No release dates — papers ship when the evidence is ready.
- 01
Evidence-bound autonomy.
What changes when an agent cannot act without producing the proof packet first — and what that costs at operational tempo.
- 02
Ontology under load.
How a typed operational model behaves when sites, crews, and jurisdictions drift faster than the schema can be re-blessed.
- 03
Cross-domain fusion at sovereign scale.
Extending the fusion graph to coalitions — multiple sovereigns, multiple clearance regimes, one shared operating picture.
Receive notes when published.
One email per paper. No promotion, no roundups — just the abstract and the link, sent the day it ships.