Access boundary: Read-only assessment.
Implemented partial validation; neither acceptance nor delivery is executed.
Surfaces: REST GET and MCP, plus bounded operator runner; current read authority only.
Read the engineering guide · All features
Capabilities
- Validate an existing dispatch within authenticated-workshop and current document authority
- Read preparation guards, absence of attempts, quote validity and channel restrictions
- Partial/blocked result; acceptance and delivery are never executed and simulation stays separate
- Create, renew and consume no quote; preserve expiry; no approval, reservation, outbox or provider attempt
- REST GET/MCP automation with dispatches:read grants no preparation or approval authority
- Business read-only semantics remain distinct from HTTP counters and persisted MCP connection activity
- The test:prod:dry-run runner reads 1–10 existing dispatches sequentially on the canonical origin using an injected read token and emits recent redacted partial evidence
REST operations
GET /api/dispatches/{id}/dry-run
Read the REST integration guide for authentication, errors and contract discovery.
MCP tools
dry_run_dispatch
Read the MCP integration guide for scope, approval and host boundaries.