Developers

Keep identity, authority, budgets, tool permissions, memory, output requirements, and trace behavior in versioned contracts rather than hiding them in prompt text.

Developer Guide

Implementation boundaries, adapters, routing, validation, streaming, state, and tests.

Runtime Request Contract

A versioned request envelope with actor, tenant, risk, authority, route, budget, and output constraints.

Tool Contract

Typed tool inputs and outputs, side effects, permissions, retries, idempotency, approvals, and compensation.

Evidence Schema

Minimized, correlated proof of requests, versions, decisions, effects, failures, and recovery.

Trace Schema

Separate infrastructure, model, tool, policy, outcome, and evaluation telemetry.

Examples

Runnable validation, routing, permission, approval, idempotency, evidence, and recovery examples.


Keep the source visible

Help others find this page

If this page was useful, link to it from a website, blog, public newsletter archive, resource page, documentation page, or social post. A public link helps the work remain discoverable after the feed moves on.

Get sharing text
Learn why links matter