Skip to content
Rutger Hemrika
Menu

Writing

#Agent platform field notes

8 pieces with this tag.

· written up 19 October 20265 min read

The rules my AI coding agents work under, and why validators detect but never prevent

Declared write sets, forbidden decision fields, a required not-established answer, named human sign-off. The operating contract for the agents that build a governed platform. Field note eight.

· written up 19 October 20265 min read

Evidence against enthusiasm: the ledger behind a build-versus-buy decision

How a hundred frameworks and four hundred sources became a decision-grade ledger, and why its first act was to downgrade every claim about my own work. Field note seven.

· written up 17 October 20266 min read

Connected is not sovereign: what it takes to qualify a frontier model route

Most "sovereign AI" claims fail at the first outage, when the system quietly phones out. Here is the contract I wrote to keep two assurance classes honest. Field note two.

· written up 18 October 20267 min read

What agent frameworks actually govern, and what they leave to you

Six agent frameworks compared on one axis: which of the five governance decisions they take, and which land on your desk. Field note three.

· written up 19 October 20265 min read

The run is the unit of governance: why durable execution belongs under every agent

Temporal, DBOS and Restate solve reliability. For a regulated agent platform they solve governance first: without a durable run, nothing can be approved, audited or stopped. Field note five.

· written up 19 October 20265 min read

Prove or hope: what evaluation and guardrail tooling can actually establish

Inspect AI, NeMo Guardrails and Langfuse each answer a different question. Confusing them is how teams end up with a dashboard where a control should be. Field note six.

· written up 16 October 20266 min read

The trust-root question: who is allowed to be the thing you cannot question?

Every agent platform has a trust root. If it is your model provider, your runtime or your cloud, you have outsourced the one decision you are accountable for. Field note one.

· written up 18 October 20266 min read

When every tool is a server: where MCP gateways really enforce policy

MCP turned tool access into a network problem. Eight gateways read at source, four ideas worth taking, and the question of what a gateway can and cannot govern. Field note four.

← Writing