Shared configuration with explicit writing responsibilities

Context

Posting, document production and settlement need the same accounting setup. Accounting consumers read the shared database and import configuration helpers within their own transactions.

Decision

Books maintains configuration and supplies shared records and helpers. Close maintains period standing, Reconciliation maintains settlement fields, and maintenance performs provisioning and erasure.

Alternatives Considered

Require a separate query or read facade. This is a proposed alternative. Adopting it would require preserving the transactional reads on which posting depends and changing the existing consumers.

Replicate configuration into each consuming module. No configuration change stream currently supports replication. A delayed copy could retain an unavailable destination.

Consequences

Committed changes become available according to each reader’s isolation and read timing.

Consumers depend on the shared schema and helpers; these reads are not separate service operations.

Declared restricting references protect records that other modules use.