Skip to main content

Verified provenance

A revision trail you can inspect, not a silent freshness claim.

Every verified dataset release keeps its own evidence date and immutable files. Automated monitoring can flag a page for review, but it cannot rewrite a journal requirement or create a new version by itself.

01Observe

Check the exact official URL with conditional requests and a content fingerprint.

02Review

Treat redirects, blocks, and content movement as signals requiring a second source review.

03Verify

Reconcile the changed claim, sibling sources, owner guide, and downstream decision cells.

04Publish

Issue a new immutable version and keep the superseded release addressable.

Release ledger

Verified dataset versions

Interface improvements are recorded separately from factual dataset revisions, so a UI release cannot masquerade as fresher evidence.

  1. current

    Version 1.0

    Initial five-journal source-fragmentation study.

    Evidence reviewed
    2026-08-26
    Study date
    2026-08-18
    Supersedes
    Initial release

    Material contents

    • Mapped 15 official publisher, society, journal, and author-center surfaces.
    • Separated six author decision areas and 16 journal-by-decision evidence cells.
    • Published the typed dataset, CSV, methodology, and canonical guide owners together.
    Open v1.0 JSONDownload v1.0 CSVOpen history JSON

The evidence boundary

A detected difference is not yet a changed rule.

Publisher pages can redirect, block automation, rearrange markup, or inject dynamic content without changing an author requirement. The daily monitor therefore opens a review task; it never updates the public dataset.

  • Signal: a conditional request, final URL, or normalized content fingerprint differs.
  • Verification: a human reopens the official source and identifies the exact decision affected.
  • Revision: the new claim, prior observation, reason, date, and immutable files publish together.
Read the complete review policy