Dispatch Agent Guidance#

Dispatch is a provider-neutral policy and execution layer.

• Keep all policy explicit in execution-plan inputs.
• Never place credential values in plans, candidates, receipts, logs, or tests.
• Keep configuration, capability evidence, and runtime implementations behind narrow ports with deterministic fakes.
• Every retry, fallback, and budget decision must be receipt-visible.
• Do not add domain prompt or response-interpretation semantics.
• Install dependencies with pnpm install. The pnpm version is pinned in package.json (packageManager). Dependency install scripts are blocked by default; the only packages allowed to run one are listed under allowBuilds in pnpm-workspace.yaml, pinned by version.
• Run npm run verify before pushing. Scripts stay on npm run … — that only invokes package.json scripts and does not depend on which tool installed node_modules.
• Docs are published with docs-kit: docs-kit.json lists the published docs and the MCP topics, and npm run docs:check is the gate. When you change code that a document covers, update that document.

This repo uses Veritas for AI governance. Read .veritas/GOVERNANCE.md before making changes. After changes, run veritas readiness and address any FAIL lines before finishing.