Error Logging

The error log becomes the single source of truth for support, operations, and development teams. Logging is essential for diagnosing and fixing errors after the fact. Support staff can use the log to guide users to the relevant entry and forward technical details to the appropriate team without reconstructing the event from memory. Users cannot reliably be counted on to accurately write down and report error messages even when displayed directly on screen. Errors must be logged persistently to a durable store so the record survives after the screen is closed, the session ends, or the user forgets what they saw. Good error logs provide enough context to understand what went wrong and where, without being so verbose that the relevant information is buried. The error log should contain not just the error description but also timestamps, context, and state sufficient for the receiving team to understand and act. The goal of error logging is to produce a clear breadcrumb trail rather than an exhaustive diary entry.