Architectural reference · concept DOI 10.5281/zenodo.20117025

~MILO™ — Modular Intelligent Learning Orchestrator

Patent pendingProvisional #63/993,825 · confidential during pendency ~MILO™Trademark Serial 99706004 6 DOIs1 concept + 5 articles · Zenodo CC BY 4.0open license, prior-art record

Abstract

MILO (Modular Intelligent Learning Orchestrator) is an adaptive AI orchestration architecture engineered around one structural commitment: human authority is preserved as an architectural property, not a deployment policy. The system composes independent learning modules behind an audit-first command bus; consequential outputs are deferred to an authorization layer with latency-aware semantics; failure of any single learning component reroutes traffic to a peer without operator intervention. The reference described here, together with five companion articles, establishes a public, reproducible, and citable basis for adaptive AI systems whose authority structure can be inspected and verified.

This page is the persistent public landing for that reference. Each linked artifact (article, DOI, repository commit, patent filing) is the canonical record; the page itself is not authoritative when in tension with the linked record.

The five companion articles

Each article has an independent DOI, is mirrored as HTML, plain text, Markdown, and PDF, and is licensed CC BY 4.0. Together they constitute the published, citable basis for MILO. A BibTeX collection is at the end of this page.

Article 01

Independence as an Architectural Property

Why module independence has to be designed in at the level of the message bus and audit substrate, not retrofitted at the deployment layer. Defines a thermodynamic notion of independence based on entropy of inter-module signal traffic.

DOI: 10.5281/zenodo.20117647

HTML Text Markdown PDF

Article 02

Latency-Aware Authentication

An adaptive authentication discipline for industrial control and human-in-the-loop AI environments where authorization decisions arrive on millisecond timescales. Treats latency as an input to the authentication function rather than a constraint on it.

DOI: 10.5281/zenodo.20117651

HTML Text Markdown PDF

Article 03

Supervisory Primacy

How human authority can be represented as an architectural property — a measurable invariant — rather than as a policy layer that can be removed or downgraded. The conceptual core of the MILO commitment to human-in-the-loop AI.

DOI: 10.5281/zenodo.20117662

HTML Text Markdown PDF

Article 04

Eight Structural Principles for Adaptive AI

Engineering constraints — audit-first command flow, persist-before-deliver, bounded recovery, reviewed-outcome learning, preserved operator authority, and three more — that together yield a system designed for viability under unforeseen operational futures rather than predictive accuracy on familiar ones.

DOI: 10.5281/zenodo.20117703

HTML Text Markdown PDF

Article 05

Adaptive Resilience

A treatment of resilience as the system property that emerges when independence (Article 01), latency-aware authentication (02), supervisory primacy (03), and the structural principles (04) compose. Includes a working definition of operational viability under tail-event load.

DOI: 10.5281/zenodo.20117716

HTML Text Markdown PDF

Architectural primitives

The reference describes the architecture in terms of seven primitives. Each is independently realizable and independently testable; together they realize the published commitment to adaptive AI under human authority.

  1. Audit-first command bus. Every consequential command is persisted to the audit substrate before it is delivered to any executor. Delivery without persistence is structurally impossible, not merely discouraged.
  2. Pre-execution authorization gate. Consequential outputs wait at a gate whose decision function admits three outcomes — allow, hold, recommend — and emits an evidence record on every transition.
  3. Independent learning modules. Each adaptive subsystem owns its own representation, training, and update cycle. There is no shared latent state that would couple their failures.
  4. Reflex predicates on the signal substrate. Real-time predicates evaluate on the audit stream itself, so reflexive responses are observable in the same record as the decisions they triggered.
  5. Bounded recovery pathways. Every consequential action has a precomputed reversal path bounded in time, scope, and authority. Recovery is a first-class operation, not an exception handler.
  6. Reviewed-outcome learning. Adaptation consumes only outcomes that have been reviewed and labeled. Unreviewed outcomes accumulate in the audit substrate but do not enter the learning function.
  7. Preserved operator authority. The operator's authority over any module is an architectural invariant — observable in the audit record, enforceable at every gate, and not delegable to a learning component.

Standards-grounding

MILO is grounded in established standards rather than asserted as a novel framework de novo. The reference is consistent with, and cites where appropriate, the following:

  • NIST SP 800-82r3 — operational-technology security baseline.
  • NIST SP 800-90B — entropy sources used for cryptographic authorization material.
  • NIST AI RMF 1.0 — AI risk management framework, particularly govern / measure / manage.
  • ISA/IEC 62443 — industrial automation and control systems security.
  • EU AI Act, Article 14 — human oversight obligations for high-risk AI systems.

Lineage: the architecture draws on Beer (Viable System Model), Ashby (requisite variety), Shannon (information), Lyapunov (stability), Hollnagel (resilience engineering), Taleb (antifragility under tail load), and Clauset (heavy-tailed event statistics).

Intellectual-property and federal record

  • USPTO Provisional Patent #63/993,825 — adaptive AI orchestration architecture, filed by Jorge Enrique Flores Montano. Pending; not granted. Provisional applications remain confidential at USPTO during their 12-month pendency window — the application number is not externally verifiable on Patent Center until a non-provisional or PCT filing matures and publishes. The public preprint articles (CC BY 4.0) and concept DOI predate any commercial assertion and serve as the independently verifiable priority artifacts.
  • ~MILO™ — USPTO Trademark Serial 99706004, filed 2026-03-16, intent-to-use, International Class 009.
  • U.S. Department of Energy — Genesis Mission RFI response (Executive Order 14363, November 2025): submitted as a public response to the DOE Request for Information. This is a unilateral RFI submission — it confers no endorsement, partnership, contract, or selection by DOE. The submission record is retained in the public evidence trail at /record.
  • Concept DOI 10.5281/zenodo.20117025 resolves across versions and is the persistent citation handle for the architecture.

How to cite

Cite the concept DOI for the architecture as a whole; cite per-article DOIs when referring to specific findings. The repository commit hash may be cited when referring to a particular implementation snapshot.

@misc{milo_architectural_reference,
  author    = {Flores Montano, Jorge Enrique},
  title     = {{MILO} -- {Modular Intelligent Learning Orchestrator}: A Public Architectural Reference},
  year      = {2026},
  publisher = {Zenodo},
  doi       = {10.5281/zenodo.20117025},
  url       = {https://www.jmautomated.com/architectural-reference},
  note      = {Patent pending, USPTO Provisional 63/993,825 (confidential during pendency). License CC BY 4.0.}
}

@article{milo_article_01_independence,
  author = {Flores Montano, Jorge Enrique},
  title  = {Independence as an Architectural Property},
  year   = {2026}, publisher = {Zenodo},
  doi    = {10.5281/zenodo.20117647}
}

@article{milo_article_02_latency_auth,
  author = {Flores Montano, Jorge Enrique},
  title  = {Latency-Aware Authentication},
  year   = {2026}, publisher = {Zenodo},
  doi    = {10.5281/zenodo.20117651}
}

@article{milo_article_03_supervisory_primacy,
  author = {Flores Montano, Jorge Enrique},
  title  = {Supervisory Primacy},
  year   = {2026}, publisher = {Zenodo},
  doi    = {10.5281/zenodo.20117662}
}

@article{milo_article_04_structural_principles,
  author = {Flores Montano, Jorge Enrique},
  title  = {Eight Structural Principles for Adaptive {AI}},
  year   = {2026}, publisher = {Zenodo},
  doi    = {10.5281/zenodo.20117703}
}

@article{milo_article_05_adaptive_resilience,
  author = {Flores Montano, Jorge Enrique},
  title  = {Adaptive Resilience},
  year   = {2026}, publisher = {Zenodo},
  doi    = {10.5281/zenodo.20117716}
}

A guidance page is also available at /cite, and machine-readable formats (txt, markdown, RSS, sitemap, llms.txt, well-known/ai.txt) are linked from /formats.

For non-specialists

If you arrived here from outside the research literature, here is the same statement in plain terms. Most AI systems are deployed under the assumption that the operator will catch mistakes after the fact. MILO is built on the opposite assumption: that mistakes should be caught before the fact, that every action should leave a record, and that the human responsible for a decision should never be displaced by the system that recommended it. The five companion articles each take one piece of that commitment and develop it carefully enough to be reviewed, cited, and (where applicable) refuted. They are open to read in full, in any format, at no cost.

If you are a researcher, the concept DOI is the place to start. If you are a journalist or a policy reader, the supervisory-primacy article is the conceptual core. If you are a practitioner, the structural-principles article is the implementation contract.