A paper series on sovereign digital resilience — data sovereignty, critical digital infrastructure, AI governance, and exit-capable design for systems of public record.
The series follows one chain: intent must stay traceable, decisions must stay answerable, and the evidence must have a fixed comparator.
Independent practitioner. Robotiqa Technologies Ltd. is the author's incorporated consulting practice and research affiliation; it is not a university or academic appointment.
ORCID iD 0009-0003-1677-684X · Google Scholar · SSRN · Zenodo
The AI operating model
what changes when delivery compresses
The AI Gateway Advantage
Value over Spend. Smart Work over Hard Work.
A practitioner’s operating model for scaling enterprise AI without vendor lock-in. Why token spend is the wrong metric, how an org-owned AI gateway turns telemetry into value, how to engineer exit cost toward zero, and why sovereignty is an enforced routing policy rather than a paragraph in a document.
The Intent Bottleneck
When AI Compresses Delivery, Strategy Becomes the Constraint
AI-native delivery compresses the last of six stages between an institution’s covenant and running software. By Amdahl’s law the total gain is bounded by the five it never touches — and cheap construction on an undisciplined intent pipeline just builds the wrong things faster. An operating model for the upper chain, and for intent provenance: the unbroken line from a stated obligation to the test that proves it in production.
Governing Agentic AI
In Systems of Public Record — Governance Is the Accelerant
Agentic AI in systems of public record: a threat model, four principles, an autonomy ladder, and the control plane that makes governance the accelerant.
Who Picked the Model?
Governing Automatic Model Selection in Enterprise AI
Model selection used to be a procurement decision: made once, by named people, with a contract behind it. In 2026 it became a runtime decision, made per request by a router on cost, latency and availability signals, with nothing behind it but a policy nobody owns. This paper separates the rules a router must obey from the signals it may optimize, names the record every call must leave behind — selection provenance — and argues that the router, not the model, is the new concentration point to engineer an exit from.
Long-horizon accountability
what must still be answerable later
Decision Custody
Who Answers for a Decision After the Machine That Made It Is Gone
Who answers for a decision after the machine that made it is gone? Naming decision custody — the missing clock in AI accountability.
The Cold Standard
A Fixed Reference for a Record That Won’t Stop Moving
The Cold Standard — a sealed, human-gated reference for detecting record drift in the AI era. Instrument, not archive; reference, not backup.
Custody-First AI Governance
A Reference Architecture for Canadian Public Bodies
This paper specifies an open-source reference architecture for governing AI systems in Canadian public bodies, and fixes the protocol for validating it at Technology Readiness Level 4. The architecture answers a gap that current governance tooling leaves open: no product carries a clock that runs for as long as the consequences of a decision last. On their publicly documented capabilities, existing tools record that an assessment happened. They do not keep the assessment reviewable after the model, the reference data and the supplier have changed.
Foundations
what long-lived systems owe the record
Short practitioner papers. References are being added on the next revision of Century-Scale Systems and Tokenized Title.
Tokenized Title
Five Governance Questions Every On-Chain Land Registry Must Answer
Dubai has put property title on-chain at scale — tokenized deeds, a regulated secondary market, and what the Dubai Land Department describes as the first Property Token Ownership Certificate. Five governance questions every on-chain land registry must be able to answer in writing, from a registry architecture custodian.
Exit-Capable by Design
Vendor Concentration Is a Sovereignty Risk
Vendor concentration in critical systems is a sovereignty problem wearing a procurement badge. Exit-capability as a tested design requirement — and how four jurisdictions reached three different remedies for the same diagnosis: OSFI Guideline B-10, DORA, the UK critical third parties regime, and Chapter VI of the EU Data Act. What an exit plan needs to be more than theatre, why concentration hides below the vendor count, why none of the switching regimes reaches model behaviour, and five questions for a board.
Century-Scale Systems
What Land Registries Teach Us About Data Sovereignty
Most technology is designed for a product lifecycle. A land registry is designed for a civilization lifecycle. Five lessons on data sovereignty from century-scale systems — why sovereignty is a property of the record rather than the data centre, why every dependency is a future liability, and why trust is the actual product.
Earlier Articles
Selected earlier writing on architecture, platform strategy, and technology leadership.
- Platform Strategy - a PrimerUnderstanding platform strategy and its importance in modern business.July 18, 2017
- IDC SpeakerSpeaking at IDC event on driving business innovation from IT.September 11, 2016
- Change Your Leadership StyleAdapting leadership styles for modern organisations.August 19, 2016
- Democratization of TechnologyHow technology is becoming accessible to everyone.February 10, 2016