PreprintCC BY 4.0Zenodo
One Engine, Many Surfaces: Studio Architecture for a Sovereign AI Operating System
- 1Mickai LTD, United Kingdom
Abstract
Most organisations adopting AI end up running a different tool for every task, each with its own idea of authorisation, logging and data handling. This paper describes an alternative architectural pattern: a single permissions, execution and audit substrate, exposed through many purpose-built surfaces (studios) that share one governance layer underneath. We set out the pattern, the problem it solves, where it breaks down, and what we have verified in our own implementation versus what remains to be proven at scale.
Related
- Federated Enterprise Intelligence: an operating model for connecting sovereign domain intelligence into a governed, active enterprise
- Representation, normalization and architecture interact across operating- and hardware-domain shifts in source-only fault diagnosis
- SEKIL OS: An Operating Architecture of Intention, Symbolic Coding, and Adaptive Reality Interaction Within Ash Geometry
- Extending the operating window of scanning electron microscopy through an integrated electron-optical architecture for high-temperature and near-ambient-pressure environments
- HereBot: An Artificial Curiosity Engine for One-Shot Language Learning in a Non-Transformer Cognitive Architecture
BibTeX
@misc{irons2026engine,
title = {{One Engine, Many Surfaces: Studio Architecture for a Sovereign AI Operating System}},
author = {Micky Irons},
howpublished = {Zenodo},
year = {2026},
month = oct,
doi = {10.5281/zenodo.23499471},
url = {https://zenodo.org/records/23499471},
note = {CC BY 4.0},
}
RIS
TY - UNPB
TI - One Engine, Many Surfaces: Studio Architecture for a Sovereign AI Operating System
AU - Micky Irons
PY - 2026
DA - 2026/10/20
PB - Zenodo
DO - 10.5281/zenodo.23499471
UR - https://zenodo.org/records/23499471
AB - Most organisations adopting AI end up running a different tool for every task, each with its own idea of authorisation, logging and data handling. This paper describes an alternative architectural pattern: a single permissions, execution and audit substrate, exposed through many purpose-built surfaces (studios) that share one governance layer underneath. We set out the pattern, the problem it solves, where it breaks down, and what we have verified in our own implementation versus what remains to be proven at scale.
ER -