Provenance, validity, and currentness
Trace research claims to exact immutable inputs without confusing history with current selection.
Provenance connects a claim revision to exact evidence: block revision, execution, output, artifact, dataset digest, variable version, environment, and producing attempt where applicable. A message or search result is not evidence merely because it sounds conclusive.
Three separate questions
- Review status: has a human or policy accepted this claim revision?
- Validity: is it supported for its pinned inputs, invalidated, or retracted?
- Currentness: does it match the project's selected live inputs now?
A newer dataset can make an old claim outdated while the old result remains valid for its pinned dataset. A failed replication can invalidate it. Neither case permits rewriting historical evidence.
Current checkpoint
The deterministic story creates one accepted, current, valid-for-pinned-inputs claim backed by one immutable artifact. Reverse invalidation, live anchors, validators, and report revalidation activate in the knowledge slice.