SHA-256 chain
Changes that stay inspectable.
A chronological, machine-readable history of evidenced releases, corrections and retractions. Earlier event bytes remain addressable and linked by hash.
Freshness is not one timestamp.
Effective date, source publication, retrieval, recording and review due dates describe different events. This log never converts a retrieval timestamp into a content-freshness claim.
- 2026-09-03 · dataset revisionPublished a reproducible r0056 signal package and bounded comparison workbench.metatron-living-signal-compatibility-snapshot · b9679f060d1f3bb9…
- 2026-09-03 · feature releasePublished the evidence-quality ledger and official-product benchmark.metatron-evidence-quality · c761051fb6b909bc…
Scope and limitations
- This log begins with the evidenced Wave 75 release; it is not a reconstruction of every earlier publication.
- Zero correction events means none are recorded in this log, not that all published statements are necessarily correct.
- A valid hash chain detects changed event bytes but does not independently prove the truth of an editorial claim.
- Git and immutable production releases are the retention layers; this public projection is regenerated deterministically.