---
id: ADR-ACC-BKS-014
title: No configuration change stream or revision history
product_area: accounting
module: books
revision: 1
status: proposed
design_intent: proposed
source_sha:
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
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.
constrains:
  - DOM-ACC-BKS-001
  - DOM-ACC-BKS-002
  - DOM-ACC-BKS-003
  - DOM-ACC-BKS-004
  - DOM-ACC-BKS-006
  - SVC-ACC-BKS-books
  - RESP-ACC
origin: OQ-ACC-BKS-004; FND-ACC-BKS-039
alternatives:
  - option: Adopt shared record history.
    why_not: >-
      This remains proposed and is recommended by the existing open question for
      settings that steer financial work.
  - option: Publish configuration change events.
    why_not: >-
      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.
supersedes: []
evidence:
  - >-
    services-accounting at f47cb263: modules/books/** (no change-event or
    history writes)
  - >-
    services-accounting at f47cb263:
    modules/maintenance/services/participants/purge-batches.ts (capture
    suppressed during purge)
---

# 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.