Audit

Audit

Audit — FinKore specification text, requirements, and related reading.

On this page

Status

FinKore Core 2.0.4 stable.

Purpose

Audit history records financially relevant occurrences so a reviewer can understand what happened, when, and who was responsible. A Business Event is the occurrence itself; an Audit Event records it. The two may carry related information but must not be assumed to be identical.

Requirements

  • An Audit Event must identify what occurred, when it occurred, and the affected Financial Entity.
  • An Audit Event must identify the responsible Actor when one is known.
  • Committed logical audit history must be append-only.
  • Sensitive content must follow the declared redaction policy.

Documents

Start with events, actors, and changes to understand the evidence in one record. Continue with append-only history before reading relationships and redaction.

DocumentWhat you will learn
EventsEssential evidence of an occurrence
ActorsAttribution, including unknown or absent actors
ChangesDifferences between prior and resulting values
Append-Only HistoryPreservation of committed logical history
RelationshipsEvidence linking related events
RedactionWithholding protected content while preserving evidence
ErrorsPortable failure codes and their priority

Invariants

Committed logical audit history must preserve the existence and meaning of its Audit Events and every explicitly recorded ordering relationship, subject only to declared redaction.

Non-Goals

This domain does not define operational logs, storage technology, database triggers, monitoring, analytics, event delivery, event-sourced reconstruction of domain state, or Entity Evolution operation semantics. Audit Relationships record evidence links for correction, reversal, void, and supersession without defining those operations.

Back to the top ↑