25+ years
public-sector technology leadership
BagelTech
BagelTech helps institutions design AI and operational systems that know when to act, when to escalate, and when to stop. The work spans governance architecture, transformation oversight, and products built for environments where confident mistakes are expensive.
Operating doctrine
Separate the operational decision from the raw prompt, request, or ticket.
Use role-separated review rather than one model quietly generating, judging, and approving its own output.
Execute when scope is clear, escalate when consequence rises, and defer when evidence is missing.
Capture rationale, artifacts, and follow-up obligations so people can inspect the process later.
25+ years
public-sector technology leadership
$15M+
ERP implementation programs directed
Zenodo + ORCID
published work on AI governance and intelligence pluralism
Runtime first
systems designed around escalation, evidence, and human authority
Services
BagelTech is strongest where governance, operations, and product design intersect. The work is less about glossy demos and more about building systems that remain legible when the stakes rise.
Design the controls that matter after the model responds: authority boundaries, escalation logic, audit trails, and human review checkpoints.
Translate policy, compliance, and operational reality into workflows that teams can actually run under pressure.
Bring program discipline to large operational change efforts where procurement, implementation, and adoption failure carry real cost.
Shape domain-specific tools that need judgment, traceability, and a credible path from prototype to institutional use.
Method
BagelTech approaches consequential systems as operating models, not just interfaces. That means clear authority, deliberate escalation, and human accountability built into the path of execution.
01
A system should not act just because it can. Permission, accountability, and institutional role all matter.
02
Useful systems escalate, defer, or request review instead of covering ambiguity with confidence theater.
03
If a consequential system cannot explain what happened, why it happened, and who approved it, the design is incomplete.
01
Separate the operational decision from the raw prompt, request, or ticket.
02
Use role-separated review rather than one model quietly generating, judging, and approving its own output.
03
Execute when scope is clear, escalate when consequence rises, and defer when evidence is missing.
04
Capture rationale, artifacts, and follow-up obligations so people can inspect the process later.
Current work
BagelTech is not one product pretending to solve everything. It is a set of related programs built around governable decision-making, institutional traceability, and operational realism.
Governance engine
Core framework
A runtime governance engine for consequential AI systems built around rights-based reasoning, escalation, and controlled execution under uncertainty.
Applied product
Active development
A lecture transcription and study companion for health-professions education, built to handle uncertainty honestly rather than smoothing it away.
Framework
Shipping
A reusable ensemble engine for running specialist AI roles across tasks, pull requests, workflows, and domain-specific operating packs.
Domain intelligence
Pilot
A contractor-side intelligence workflow for agreement review, obligation tracking, and compliance analysis across the contract lifecycle.
Publications
The governance direction behind BagelTech is grounded in published work on runtime oversight, intelligence pluralism, constitutional governance, and uncertainty routing.
Journal article
2026
A case for reliability through structured, role-separated intelligence rather than a single synthetic authority pretending to do every kind of reasoning well.
2025
Preprint
A formal framing of runtime governance grounded in rights-based reasoning, interpretive oversight, and controlled execution.
2025
Report
An argument that uncertainty is an operational routing signal, not a cosmetic confidence score.
2025
Specification
A technical specification for the architecture behind execution, escalation, evidence capture, and governable model behavior.
About
BagelTech sits at the intersection of governance research, product design, and operational delivery. The through-line is practical: translate serious ideas into systems that institutions can actually adopt, inspect, and trust.
Start here
Engagements usually begin with a focused scoping conversation: what decisions matter, what authority exists today, where uncertainty goes, and what must be reviewable later.