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.
Policy and Approval Contract
Deterministic decisions, reason codes, approval authority, expiry, override, and evidence.
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.
Integration Checklists
Release gates for runtime artifacts, APIs, security, observability, and rollback.