Reconciliation Keeps Its Own Append-Only Audit Trail

Context

Reviewers need financial decisions and eligible refusals with their responsible actors.

Decision

Retain reconciliation activity in its own append-only store and expose that history through module reads.

Alternatives Considered

Use only generic record history. The current module has not adopted it, and row changes alone do not capture refused approvals.

Publish lifecycle change events to consumers. Current consumers read within Accounting; notification-based reactions are not implemented.

Consequences

Activity retains actors, reasons, request context and bounded details rather than banking credentials. Guard refusals are recorded, while later request-write failures can leave no attempt event. Any shared-history migration must preserve access to existing financial evidence.