Operations
Troubleshoot by boundary
Use failure codes, logs, and bounded checks to diagnose the correct layer without masking an integration failure.
Common failures
| Symptom | Check first |
|---|---|
| CONFIG_INVALID | Run worker:config and inspect only variable presence and public addresses. |
| MODEL_UNAVAILABLE | Check model base URL, key presence, timeout, and provider response status. |
| EVIDENCE_MISSING | Confirm the packet is LIVE_VERIFIED and the evidence ID matches registry read-back. |
| PROCESS_BUSY_RETRYABLE | Another worker lease owns the same source event; wait for expiry or inspect the process. |
| UPSTREAM_UNAVAILABLE | Check worker status API reachability from the web server, not only from your browser. |
| INVALID_SIGNATURE | Confirm the quote domain, chain ID, RiskGuard address, and signer key match. |
Diagnostic sequence
- Check the boundary label in the response or UI: LOCAL_FIXTURE_ONLY, LIVE_VERIFIED, or a failure boundary.
- Run the smallest local reproducer: API curl, worker status query, or agent quote command.
- Inspect the durable worker stage and last error without printing secrets or proof bytes.
- Retry only retryable network/provider failures; do not retry terminal receipt or signature mismatches blindly.
- Re-run submission preflight before claiming a release gate is complete.
Safe support bundle
corepack pnpm worker:config
curl -s http://localhost:3000/api/health
curl -s http://127.0.0.1:8787/v1/orders
corepack pnpm submission:preflightDocumentation is generated from the current repository contract. For the recorded testnet evidence, inspect the live proof console.