About OBEXGATE
Governance that proves itself under pressure.
OBEXGATE is runtime enforcement of governance, not governance after the fact. It is a Niti Logic LLC platform, co-built by Amelie Kingsbury Barry and Felix Montanez.
What we built
Outputs treated as claims, not as truth.
Most AI systems fail in production for a simple reason: they accept outputs without verifying them. OBEXGATE was built around a different premise. Outputs are claims. Claims must be validated before they are allowed to become real.
This is not enforced through prompts or behaviour. It is enforced through topology. A non-bypassable execution boundary. A runtime-owned commit authority. No state mutation outside the verification gate. No path where invalid states can influence future outcomes.
In practice, that means no agent can mark work complete without verification, no output is accepted without being checked against the rule that applies, and no failed attempt leaves residual influence in the system. The same invariant runs across every framework OBEXGATE covers, from the EU AI Act and DORA to HIPAA, NIST AI RMF, and SOC 2.
→ The invariant
Only states that are admissible at time t are allowed to become real. Inadmissible states are non-executable, non-influential, and non-realisable.
→ The boundary
A non-bypassable execution boundary, runtime-owned. No mutation outside the verification gate.
→ The evidence
Tamper-evident audit lineage. Article-mapped evidence packs. Decision provenance produced continuously.
Founders
Built by people who have lived inside the systems they govern.
Felix Montanez
Co-Founder · Runtime Architecture
Most AI systems fail in production for a simple reason: they accept outputs without verifying them. I have been focused on a different approach, building AI systems where outputs are treated as claims, and must be validated before they are allowed to become real.
Over the past year I designed and validated InnerLight OS, a verification-constrained execution runtime that enforces this at the system level. The core invariant is simple:
- Only states that are admissible at time t are allowed to become real
- Inadmissible states are non-executable, non-influential, and non-realisable
This is not enforced through prompts or behaviour. It is enforced through topology: a non-bypassable execution boundary, a runtime-owned commit authority, no state mutation outside the verification gate, no path where invalid states can influence future outcomes.
I have implemented this as a working multi-agent runtime that executes full software life-cycles, from architecture to implementation to QA to verification, with enforced structure and deterministic outcomes.
My background spans distributed systems, full-stack engineering, and building production systems across teams and environments. Most recently I have been focused on making AI systems reliable under real-world conditions, not just capable in isolation.
Amelie Kingsbury Barry, PhD EE, PhD CS
Co-Founder · Managing Director, Niti Logic
I work across systems that most people encounter only from one side.
I watched my mother lose to systems she did not understand before I had words for what I was seeing. She immigrated legally from Thailand speaking almost no English, brilliant and resourceful, and completely unprepared for what it meant to exist inside bureaucracy. By the time I was in school I was the one making phone calls, translating not just language but logic. I could not always get her through. But I paid attention.
The question I have spent my career answering is the same one I could not answer for her as a child: what does this system actually require, and what do you do next?
Nearly thirty years later, that question runs through all of it. Boolean retrieval and early NLP at Pubnetics and RealLegal. Seventeen years on satellite power systems. The administrative and financial architecture of US healthcare across payer, provider, and IPA layers. Two PhDs, in Electrical Engineering and Computer Science.
The common thread is not the domain. It is how rule-based systems behave when decisions must translate into real-world outcomes. If a decision is not traceable, transparent, and defensible at the point of impact, governance has failed.
I solve for that boundary.
OBEXGATE is the product expression: a deployed runtime governance enforcement product, built because advisory governance does not survive contact with deployment. Niti Logic is the parallel deployment, applying the same architecture (PRISM) to healthcare decision logic.
I do not build advisory models. I build systems that can be used.
See what applies to you, and what it could cost.
Six questions. Personalised regulatory map, deployment cost estimate, statutory exposure. To your inbox. Or book a 30-minute call.