In plain English
An audit trail records events such as a status change, user action, or approval. Decision traceability connects those events to source identity, semantic meaning, governing versions, human authority, decision-time chronology, and explicit limitations. An audit trail may be sufficient for event accountability; richer traceability is needed when a reviewer must reconstruct why the retained context supports a decision path.
A simple example
An audit trail may show that a person approved an exception. Decision traceability asks what evidence, version and authority surrounded that approval and what remains missing.
When an audit trail is sufficient
An audit trail is often the right control when the question is who changed a field, when a state transitioned, which account performed an action, or whether a required approval event occurred. It should not be dismissed because it does not answer a different question.
The gap appears when review requires evidence meaning and authority beyond the event itself. A timestamped override event does not necessarily identify the source evidence, policy version, delegated authority, or limitations that surrounded it.
Seven dimensions of the comparison
The same decision can be evaluated through event history and through reconstructable context. The two records can complement one another.
Audit trail and decision traceability
Worked synthetic use case: a manual payment exception
An illustrative synthetic payment is referred after a risk threshold is met. An operations reviewer records an exception, and the source payment system later records the outcome. The audit trail shows the referral, reviewer action, approval event, and outcome transition.
Decision traceability adds the payment identity, authentication and authorization records, risk-rule version, threshold configuration, human-certified exception rationale, approver role, decision-time sequence, and an unavailable delegation record.
Synthetic example
Same action, different review depth
The event history is complete enough to prove that the override occurred, while the authority dimension remains Ambiguous because the retained approver role does not resolve the missing delegation version.
- Audit-trail answer: the override and approval events occurred.
- Traceability answer: evidence, version, rationale, and source outcome are linked.
- Proof gap: delegation version is Missing/unverifiable.
What a later reviewer asks
The reviewer asks whether the retained rule and threshold match the event time, whether the authentication and authorization records share the payment identity, whether the reviewer held the required authority, and whether evidence acquired after the outcome was kept out of the decision-time set.
A reviewable record can support a challenge or defense where the retained evidence permits. It does not guarantee defensibility or replace the institution's control and legal analysis.
What RecordArc reconstructs and does not do
RecordArc can organize retained events and context into classifications, chronology, proof conditions, and limitations. It preserves the audit trail as evidence rather than competing with it.
RecordArc does not change the audit record, infer unapproved causal relationships, validate the payment outcome, or decide whether an exception should have been granted.