updown move enter open esc close matheesan.ca / index

    CASE 01 · LLM agents

    The production voice agent

    Empty repo to live, multi-turn agent — and the defects that nearly shipped.

    empty repo → liveauth + booking3 launch blockers caught
    LLM agentsstate machineOAuth2evalsproduction

    problem

    An enterprise voice agent had to authenticate callers, validate eligibility and write multi-step transactions against a legacy API — with no room for a wrong-record change.

    approach

    Built the core in a YAML state-machine DSL: atomic multi-step transactions, client-side eligibility checks, OAuth2 integration, and a fallback auth path when a planned endpoint did not ship. Turned a readiness audit into a delivery backlog and ran releases through go-live.

    the hard part

    Three defects would have reached callers: an authentication bypass, a confirmation path that could act on the wrong record, and a default that blocked first-time users. I proved the last one with a single-variable test against the live API and found the unit test that had encoded the bug.

    result

    Launched and handed over to hypercare. Took the launch-critical auth suite from never-executed to fully passing, cut validation violations to zero across thousands of tests, and reached full measurable component coverage.

    what I’d do differently

    I would make “did the test actually execute?” a first-class assertion from day one, not something I discover during a launch audit.