Go CLI Errors and Observability

Design failures for recovery first, then add the minimum safe evidence needed to diagnose them. Keep internal detail out of the normal user contract.

Core Workflow

1. Classify failures by user action, dependency, cancellation, and internal defect.
2. Preserve machine-checkable causes with wrapping, types, or sentinels.
3. Map causes to concise user messages and stable exit behavior at the boundary.
4. Assign one terminal owner to render, log, and map each failure.
5. Preserve material cleanup failures without hiding the primary cause.
6. Add opt-in verbosity and structured logs on stderr or a dedicated sink.
7. Allowlist and redact diagnostic evidence; require consent before collection or upload.
8. Test recovery guidance, output separation, redaction, and cancellation.

Read Next