Dated evidence ledger · MON-LOCAL-DEMO-001
Freshness is not
the result.
The result remains FAIL. Freshness only tells you how old its evidence is and whether the linked record still resolves.
Evidence is older than 14 days. Re-run before relying on it.
4 PASS · 1 FAIL · 1 BLOCKED
01:33 SAST · local fixture
No automatic schedule configured
Freshness lifecycle
The clock cannot improve the evidence.
A fresh failed result is still a failed result. A stale pass would still need a rerun.
- Observation recorded
One authorized loopback run. This is a baseline, not a trend.
- Becomes stale
The latest evidence is older than the 14-day current window.
- Becomes expired
The linked mark has passed its validity date. Historical evidence remains downloadable.
State rules
Five states. No silent green light.
- CURRENT
- Latest completed evidence is at most 14 days old and every declared link and hash resolves.
- STALE
- Evidence is older than 14 days, but the linked mark has not expired.
- EXPIRED
- The mark is expired or the record has reached its fixed expiry date.
- UNVERIFIABLE
- A record, mark, manifest, bundle or declared hash is missing or mismatched.
- NO RESULT
- No completed observation exists. Scheduled, started or blocked work is not a result.
Observation ledger
One observation, honestly.
LOCAL-HARNESS-20260909-001
Demo Library fixture-2 · contract 1.0.0 · loopback only
Operating boundary
This is not continuous monitoring.
No background agent, alert channel or automatic rerun is configured. The ledger and its rules are real; future observations appear only after another authorized local execution. Nothing here monitors a customer system.
RECORD SHA-256
7f6f84ac8a71d2e82c2309d000577a81096930299172e4661f747820791d1c91