Operating manualRead before use

Matthew
Kyawmyint

Pronounced “Jaw-me-int”.

Disclosure: copy drafted with a model from his résumé, review pending.

Founding engineer. Builds AI agents for regulated industries, most recently as the only engineer taking a voice and chat agent from zero to production with universities.

Location: Davis, California. Operates remotely.

Signal flow of a call through the agent A caller connects to an agent, then a safety gate, then a human handoff. Callout 1 marks the human handoff, callout 2 marks the ship gate under the agent, callout 3 marks the safety gate. CALLER AGENT SAFETY GATE HUMAN HANDOFF SHIP GATE 123 FIG. 1 SIGNAL FLOW

Features

  1. Voice agents with a human in the loop

    A phone agent on OpenAI Realtime and Twilio that hands callers to a university contact center by attended transfer, and plays its disclosure before any call proceeds.

  2. Evals as a ship gate

    Mutation-tested evals (each check proven to catch a planted regression), a bot-to-bot voice eval, and a deploy gate that blocks changes to safety-critical paths without a passing receipt.

  3. Safety that fails closed

    Crisis detection that pages a person, guards on regulated figures, cross-tenant redaction, and governance rules wired into every prompt with a CI check. Passed a HECVAT security review.

Self-test

Planted regressions must turn a check red. That is how a check proves it works.

Self-test results
CheckResultMeasured
Not yet run–Press the run button.

Revision history

Rev.Change
2025 – nowProtagonist. Founding Engineer
2025Contract engineering, early-stage startups
2024 – 2025Workmaps. Founding Software Engineer
2022 – 2024Everest AI. Senior Software Engineer
2022Ethos Life. Software Engineer
2018 – 2022Amazon Web Services. Software Development Engineer
EarlierJapa. Cofounder (smart parking, UC Davis)

Operating procedure: working with Matthew

  1. Send the problem in writing

    Written context comes first. State the problem, the constraints and what has been tried.

  2. Define success and failure before building

    Scope the success metric. List the failure modes. Both are agreed before work starts.

  3. Ship the smallest live version

    Release behind evals. Expand only after the evals hold.

  4. Fail closed on safety-critical paths

    A safety-critical path that cannot decide stops, and pages a human.

  5. Hand off with documentation

    The system is documented so that it runs without him.

Support

hi@matthewkyawmyint.com

linkedin.com/in/matthewkyawmyint