
Blog


A Skill Description Is an Agent Routing Policy

An Asynchronous Tool Call Needs a Work Receipt

A Multi-Agent Budget Needs Cost Attribution Beyond a Limit

Agent Evaluation Must Test Revalidation Beyond Completion

Treat an Agent's Tool Catalog as Mutable State

Effect Claims Help Multi-Agent Work Avoid Collisions

Causal History Makes Multi-Agent Work Reviewable

A Completed Agent Task Needs an Acceptance Contract

Treat User Corrections as Task-State Changes

Data Minimization Is an Agent Design Constraint

A Policy Snapshot Keeps Long-Running Agents Accountable

A Cached Agent Result Is a Claim With an Expiry

Agent Previews as Proposals with Explicit Effect Contracts

Treat Prompt Injection as an Agent Trust-Boundary Failure

Reliable Recurring Agents Start with a Run Contract

Explicit Change Ownership for Multi-Agent Coding

Agent Abstention Is a Safety Capability

Progress Updates Are an Agent Control Surface

Isolation Beyond Git Branches for Coding-Agent Workspaces

An Honest Shutdown Contract for Long-Running Agent Cancellation

Run Manifests Give Long-Running Agents Durable Records

The Evidence Package Behind a Strong Coding-Agent Handoff

Tool Discovery Is a Context-Engineering System

Safe Agent Retries Require Intent and Effect Identity

Replayable Event Feeds Turn Live Agent Updates into History

The Verification Loop for Reliable Computer-Use Agents

Evaluate Coding Agents as Complete Execution Environments

Parallel Agents Work Best on Search-Shaped Tasks

Recovery Completes the Agent Tool Contract

One API, Several Clients: When SDK Generators Benefit From a Contract IR

Design Tool Results as Stable Agent Interfaces

When Task-Scoped Subagents Should Forget: Choosing Memory Scope in Multi-Agent Systems

Queue, Steer, or Interrupt? Delivery Semantics for Long-Running Agents

An MCP Client Model: Context, Capability, and Consent

Context Epochs: A Better Mental Model Than “Just Keep the Chat History”

Separate Durable Intent from Replaceable Agent Execution

Model Routing Belongs in the Agent Policy Layer

Context Compaction Requires a Fidelity Contract

Queue Before Fan-Out: Admission Control for Multi-Agent Systems

Evidence Cards Add Provenance to Retrieved Context

A Model Upgrade Is an Agent Behavior Change

A Plan Is a Perishable Artifact

Plugin Trust Starts with Evidence Beyond the Directory Listing

