Categorisation Audit Trail

Categorisation Audit Log

Every categorisation decision that affects the ledger is now persisted to an audit trail. When the rules engine evaluates a transaction during import, the outcome, matched rule, score vector, and full evidence are logged.

• Complete decision history — query which rule categorised any transaction, when, and why.
• Score vectors stored — the 6-dimension lattice score is preserved as a native PostgreSQL array for efficient querying.
• Evidence as JSONB — the full evidence object (matched field, operator, normalised input, reason) is stored for regulatory audit and replay.
• Scoped to ledger changes — only import confirmations are logged. Test panel queries and preview evaluations are excluded to keep the audit trail focused.

This completes the three-phase implementation of the categorisation architecture: typed results (v4.4.0), lattice scoring (v4.5.0), and audit persistence (v4.5.1).