Golden Traces¶
Status¶
Evidence required. No golden trace dataset or replay harness was found in the inspected snapshot.
Required Trace Families¶
- Vault deployment through deposit acceptance.
- Healthy reward receipt through claim payout.
- Dust and reserve-backed smoothing.
- Stale oracle and same-epoch conflict.
- Slashing to exit to settlement.
- Failed deposit and failed claim examples.
- Governance proposal, queue, cancel, and execute.
Production Evidence To Archive¶
Input events, transactions, expected state snapshots, replay command, actual output, diffs, source commit, and owner of each trace family.
Review Rule¶
Golden traces should include both success and failure paths. A trace that proves a deposit succeeds should have a paired trace for stale readiness, consumed intent, or bad credentials. A trace that proves claims work should have paired stale, capped, and cancelled pending-claim traces.
Evidence Model¶
| Field | Requirement |
|---|---|
| Purpose | stable examples for expected economic and deposit flows. |
| Expected location | trace fixtures and generated outputs. |
| Current local evidence status | Evidence required unless the named artifact is present in this repository or the Solidity source snapshot and has been inspected in the current run. |
| What it proves | that known scenarios still produce the expected state deltas. |
| What it does not prove | coverage for unlisted edge cases. |
| How to regenerate | Run the documented tool from a clean environment, archive command, commit/source hash, config, stdout/stderr, and result files. |
| Production requirement | Results must be tied to the exact source manifest lock, compiler version, dependency lock, and deployment artifact under review. |
| Owner responsible | Protocol engineering owns source/test correctness; security review owns independent challenge; governance owns accepting residual risk. |
| Failure meaning | A failure blocks release, launch, upgrade, or operation until root cause is fixed or explicitly accepted with documented risk. |
Review Notes¶
Do not write “pass” for Golden traces without current evidence. If evidence is missing, stale, or tied to a different source snapshot, write Evidence required and keep the gap visible in the release or operations checklist.