Can an evidence link survive a source change?
ClaimLedger verifies that changed source bytes invalidate a recorded evidence link.
- READY FOR HUMAN REVIEW
- NOT A NOVELTY CLAIM
- SYNTHETIC FIXTURE
THE EPISODE
Question, execution and what it does not mean
Question and protocol
The episode records a bounded question, one short local source fixture, one controlled mutation, one repetition and a deliberately preserved failed run. Timing is descriptive only; no performance claim is made.
Evidence and execution
HowHow revalidates source descriptors, exact character spans, experiment contents, filename and identifier binding, output hashes and review targets. A changed source invalidates the stale link instead of silently keeping a VERIFIED status.
Why this is not a scientific result
The fixture demonstrates product gates and package mechanics. It does not prove a novel method, universal validity, human peer review or eligibility for arXiv. The synthetic data is test-only.
VERIFICATION
What the fixture actually established
- Evidence re-read
- Exact bytes matched
- Failure retained
- Negative control preserved
- Novelty
- Not established
- Publication
- Human decision required
VERIFIED
RECORDED
UNKNOWN
NOT SUBMITTED
ARTIFACTS
What the package contains
- Append-only event history
- Source and evidence manifests
- Success and failure experiment records
- Claim and review records
- Generated figure and table
- LaTeX source package with checksums
- Clean-room rebuild report
STATUS LANGUAGE
Why the labels look like this
VERIFIED is reserved for evidence the product re-read from the exact source bytes and matched against the exact locator. Fixture and imported data stay separately labelled, and a record with a missing version, licence or locator stays incomplete rather than quietly becoming evidence.
READY FOR HUMAN REVIEW means a person can inspect a complete package. It does not mean the result is novel, correct, accepted, peer reviewed or eligible for arXiv.