Agent Engineering
The practical craft of building agents that survive contact with real work: tool design, context, evaluation, failure modes and the boundaries worth enforcing.
Page 1/5

The AI Platform Team Is an Enablement Layer
How AI platform teams can provide reusable harnesses, evaluation systems, source governance, capability controls, and operational patterns without owning every product decision.- Published on

When Agents Should Refuse to Continue
A practical guide to refusal as an operational state for AI agents when evidence, authority, safety, budget, or task coherence breaks down.- Published on

Human Handoffs Are Part of the System
How AI workflows should treat human review, escalation, approval, correction, and ownership as designed transitions rather than interruptions.- Published on

The Prompt Is Not the Policy
Why AI policy must live in enforceable rules, source governance, tools, approvals, and evaluators rather than being reduced to instruction text.- Published on

Design AI Workflows Around Failure Modes
Why reliable AI products should begin with expected failure classes, containment paths, and recovery states instead of only optimizing the happy path.- Published on

Evidence Manifests for Agent Work
How agents can make completion auditable by recording required sources, artifacts, checks, decisions, exclusions, and unresolved uncertainty in one durable manifest.- Published on

Shadow Mode for AI Releases
Why AI features should run beside existing workflows before taking authority, and how shadow mode exposes behavior, cost, evidence, and failure classes safely.- Published on

Capability Tokens for AI Agents
A practical model for granting AI agents narrow, temporary, auditable authority to use tools, touch data, and perform consequential actions.- Published on

Agent Queues Need Backpressure
How AI work queues should control intake, priority, concurrency, retries, and human review so autonomous systems do not turn demand into uncontrolled motion.- Published on