No configuration change stream or revision history

Context

The current configuration stores modification details and versions, but no reconstructable sequence of changes. History remains an open product question.

Decision

Books emits no configuration change events and writes no revision history. Accounting consumers read shared records; each record retains only its current values and latest modification details.

Alternatives Considered

Adopt shared record history. This remains proposed and is recommended by the existing open question for settings that steer financial work.

Publish configuration change events. The examined code supplies no event contract, and external consumer requirements remain unknown.

Consequences

Staff cannot reconstruct earlier default, method or policy changes from these records alone.

External consumers have no configuration change-event contract to subscribe to.

Purge suppresses change capture; that suppression does not establish the absence of other lifecycle audit records.