Agents on Jamal Yusuf

Validating Agent Outputs in Go Before They Touch Production

Sun, 14 Jun 2026 00:00:00 +0000

An agent that sounds right is the most dangerous kind of wrong.

I have seen it in healthcare workflows — confident JSON, clean prose, a downstream system that accepts the payload and only screams twenty minutes later when reconciliation fails. The model did its job. The system failed to treat probability like probability.

In Go, I fix that with a boring layer between the model and the world: validate before side effects. Always.

Context Is the Kill Switch: Go, Cancellation, and LLM Timeouts

Wed, 10 Jun 2026 00:00:00 +0000

The first time I watched an agent runaway eat a month’s inference budget in an afternoon, nobody blamed the model. They should have blamed the missing kill switch.

The model kept going because nothing told it to stop. Tool calls chained. Retries compounded. Goroutines — or their equivalent — waited politely for a provider that had already left the building.

In Go, the kill switch has a name: context.Context. And I think it is the most underrated tool in production LLM orchestration.

Building Production-Grade AI Agents at Enterprise Scale

Mon, 18 May 2026 00:00:00 +0000

An agent that cannot reach production systems is not an agent. It is a demo with ambition — and in healthcare, ambition without integration is just risk in a nicer font.

I learned this leading multi-agent platforms wired into claims, membership, and payment flows — real latency SLAs, real audit requirements, real members on the other end of every invocation.

Integration over isolation

The value was never “another tab with a chat box.” Experts wanted help inside the flow of work — grounded in operational context, historical data they could defend, and APIs that did not lie.