# Sample DecisionTrace Explainer

## Purpose
Explain the fields in the sample decision trace and why they matter for governance, audit, and operational review.

## Audience
- Security and risk reviewers
- Platform teams
- Buyers evaluating SDE evidence quality

## Field Notes
- `traceId`: unique identifier for the decision event
- `contractId`: identifies which governed decision contract was evaluated
- `contractVersion`: records the contract version in force for the decision
- `policyPackVersion`: identifies the policy or logic package used at runtime
- `decision`: the governed outcome returned by SDE
- `reasonCode`: stable machine-readable explanation for the outcome
- `confidenceState`: summary of reliability or confidence posture used in the decision
- `request`: relevant request context used to evaluate the decision
- `constraints`: restrictions returned to the caller instead of a simple allow
- `evidence`: governance metadata such as escalation or review path
- `timestampUtc`: event timestamp for ordering and audit review

## Why This Matters
A useful decision trace does more than state the final outcome. It ties the outcome back to:
- the contract in force
- the reason code set
- the constraint posture
- the review or escalation path

That is what makes a decision explainable, reviewable, and replay-friendly.