Logs and Request Diagnostics
Structured logs, correlation IDs, levels, and redaction.
Search by request ID and timestamp, then redact before sharing evidence.
Source boundary
Source boundary: AutoCore current main 7a504f6e430c16d4fcb03ebdea3cc3fb7816df60, checked against immutable v1.0.0-rc.1 at 9edfb109f44cc80385784c694b96392cfc04e70f.
Pino structured logs correlate requests and redact authorization, cookies, and set-cookie headers. Production uses JSON; development may use readable output. x-request-id is the support join key.
| Check | Source-backed expectation |
|---|---|
| Scope | Do not raise log level or disable redaction in production as a first response. |
| Evidence | Use placeholders, timestamps, release identity, route, status, and request ID where relevant. |
| Safe action | jq 'select(.requestId == "phase6-demo")' logs/api.json |
| Stop condition | Unknown authorization, destructive impact, secret exposure, or conflicting evidence. |
Verification
Run the safe check, record its result, and compare the outcome with the documented contract. If the result depends on external configuration or provider availability, mark it as configuration-dependent rather than claiming a product guarantee.
jq 'select(.requestId == "phase6-demo")' logs/api.json
Safety boundary
Examples are non-production and use placeholders. Do not deploy, reset, force a migration, create secrets, activate providers, replay sensitive work, or expose private data from this page.