Patterns
Audit trail & provenance
Compliance lives on "who did what, when — and prove it." Every consequential action is recorded as an immutable, attributed entry: a person or Argus, a target, a timestamp, and (for AI) the grounding behind it. The trail is filterable and exportable straight into the exam binder.
Append-only by design. Entries can't be edited or
deleted — each carries a content hash chained to the prior one, so tampering is detectable. This is what makes
the log admissible as exam evidence.
The log
Today · June 5, 2026
2:14 PM
Argus drafted the Exam Readiness Report for First State Bank of Lometa.
- Grounding
- BSA/AML Policy v7 · 31 CFR 1010.311
- Confidence
- 88%
- Reviewed by
- Dana Reyes (BSA Officer) · accepted with edits
11:02 AM
Dana Reyes filed a CTR for member transaction #44120.
9:48 AM
M. Okafor assigned 1071 Small-Business to the Fair Lending program.
Yesterday · June 4, 2026
4:30 PM
Argus escalated a SAR question to a Compliance Alliance specialist — low confidence on a filing decision.
1:15 PM
T. Nguyen updated the Flood (Reg H) evidence binder — added 2 documents.
Anatomy of an entry
Five fields, always. AI entries add a provenance block; human entries carry the actor's role.
| Field | Meaning |
|---|---|
| Actor | The person (with role) or Argus — never anonymous. |
| Action · target | A plain-language verb and the object it touched (filed, drafted, assigned, escalated). |
| Timestamp | To the minute, in the institution's timezone; tabular figures. |
| Provenance | For AI: grounding sources, confidence, and the human who reviewed it. The trust contract, logged. |
| Hash | A content hash chained to the prior entry — the tamper-evidence seal. |