Expand description
Dispatch pipeline — the request processing chain.
Pipeline order:
- Effect check — brain-wave compatibility (zero-cost, inline)
- Dharma gate — ethical governance verdict
- Resource rules — write/spawn/network budgets, novelty, human review
- Rate limit — sliding window per-tool + global
- Circuit breaker — fault tolerance, fast-fail on repeated errors
- Tool call — execute the tool (optionally bounded by a dispatch timeout). Secret-scan sampling (6b) runs right after a successful call: warn-only credential-shape scan, deterministic 1-in-N, content never logged (P-PROV-5/B(c)).
- Karma record + write-audit journal — declared vs actual effects (confirm-gated dispatches record the confirm — the delete-confirm audit)
- Stats — success/failure and latency tracking
Between 4 and 5 sits the firebreak (fix-queue P1.4+P1.6): the explicit
confirm: true gate for destructive tools, the promoted Jan-11
forbidden-command veto, the bulk-scope law, and advisory disclosure.
Structs§
- Authority
Dispatch - Evidence passed to the authority-seam hook after a destructive dispatch.
- Dispatch
Pipeline - The dispatch pipeline processes tool calls through governance, rate limiting, circuit breaking, and karma tracking before and after the actual tool execution.
- Pass
Budget - Optional spend budget carried by a pass.
- Pass
Evidence - Verified gate-lite pass evidence handed to the authority-seam hook.
- Pass
Quotas - Verified gate-lite pass evidence (S2) — plain data, no verifier dependency.
Enums§
- Pass
Mode - Pass enforcement mode (
WM_MANDALA_PASS).
Constants§
- DEFAULT_
DISPATCH_ TIMEOUT - Default dispatch timeout (300s) applied by [
DispatchPipeline::from_env] whenWM_DISPATCH_TIMEOUT_MSis unset.
Traits§
- Pass
Gate - Offline pass verifier injected by the deployment (wm-receipts in wm-mcp).
- Receipt
Dispatch Hook - Optional post-dispatch receipt hook (S1 receipts core).