Architecture guide outlines principles for safe, durable backend log aggregation

A technical guide outlines key principles for designing a log aggregation API for backend applications. It emphasizes creating a durable, queryable evidence stream separate from the application runtime. The architecture prioritizes rollback safety, allowing operators to reconstruct events after an application deployment is reverted. It defines core invariants including schema continuity, event correlation using stable IDs, and honest acknowledgement of data acceptance. The design treats logs as immutable evidence, not business truth, with clear ownership boundaries defined for different system components.