ENGINEERING BLOG
Technical research and engineering insights from the team building the operating system for responsible AI operations.
121 articles · Published by MARIA OS
Designing consent, scope, and export gates that enforce data sovereignty before a single word is stored
When an AI bot joins a meeting, the first question is not 'what was said?' but 'who consented to recording?' This paper formalizes the gate architecture behind MARIA Meeting AI — a system where Consent, Scope, Export, and Speak gates form a fail-closed barrier between raw audio and persistent storage. We derive the gate evaluation algebra, prove that the composition of fail-closed gates preserves the fail-closed property, and show how the Scope gate implements information-theoretic privacy bounds by restricting full transcript access to internal-only meetings. In production deployments, the architecture achieves zero unauthorized data retention while adding less than 3ms latency per gate evaluation.
Every decision must cite its source — how MARIA Meeting AI eliminates hallucinated minutes through segment-level evidence linking
Traditional meeting minutes suffer from a fundamental trust problem: the reader cannot verify whether a recorded decision actually occurred in the meeting or was interpolated by the note-taker. MARIA Meeting AI solves this by enforcing mandatory evidence linking — every decision, action item, and summary section must reference specific transcript segments as evidence. This paper formalizes the evidence-linking constraint, presents the incremental summarization algorithm that generates minutes every 15 seconds during live meetings, and proves that the citation coverage metric converges to completeness as transcript length increases. In evaluated Japanese business meetings, the system achieved 94% citation coverage with zero hallucinated decisions.
How a seven-state machine coordinates browser automation, audio capture, speech recognition, and live streaming into a coherent meeting intelligence pipeline
A meeting AI bot is not a single component — it is an orchestra of subsystems that must start, coordinate, and stop in precise sequence. The browser must launch before audio can be captured. Audio must flow before speech recognition begins. Recognition must produce segments before minutes can be generated. And when the meeting ends, all components must shut down gracefully without losing data. This paper presents the state machine design of MARIA Meeting AI's session manager, which coordinates Playwright browser automation, CDP audio capture, Gemini Live Audio ASR, and incremental minutes generation through a seven-state lifecycle with EventEmitter-based real-time streaming to dashboard clients.
AGENT TEAMS FOR TECH BLOG
Every article passes through a 5-agent editorial pipeline. From research synthesis to technical review, quality assurance, and publication approval — each agent operates within its responsibility boundary.
Editor-in-Chief
ARIA-EDIT-01
Content strategy, publication approval, tone enforcement
G1.U1.P9.Z1.A1
Tech Lead Reviewer
ARIA-TECH-01
Technical accuracy, code correctness, architecture review
G1.U1.P9.Z1.A2
Writer Agent
ARIA-WRITE-01
Draft creation, research synthesis, narrative craft
G1.U1.P9.Z2.A1
Quality Assurance
ARIA-QA-01
Readability, consistency, fact-checking, style compliance
G1.U1.P9.Z2.A2
R&D Analyst
ARIA-RD-01
Benchmark data, research citations, competitive analysis
G1.U1.P9.Z3.A1
Distribution Agent
ARIA-DIST-01
Cross-platform publishing, EN→JA translation, draft management, posting schedule
G1.U1.P9.Z4.A1
Complete list of all 121 published articles. EN / JA bilingual index.
121 articles
All articles reviewed and approved by the MARIA OS Editorial Pipeline.
© 2026 MARIA OS. All rights reserved.