Source date — nullvuild

A source date is the date that tells a reader which version of a source was used, checked, or updated.

It is not always the same as the publication date. A policy page may be published once and updated many times. A software document may show a version number but not a visible publish date. A news article may be corrected after release. A dataset may have a collection date, a release date, and a download date. A useful source trail makes those dates explicit so later readers can judge whether the note is stale, current, or tied to a specific historical version.

A source date note usually includes three fields: source published date, last checked date, and relevant version or effective date. If only one date is available, the note should say which one it is. Writing “2026 source” is weaker than writing “checked on 2026-06-23; page did not show an effective date.” The second form admits what is known and what is not known.

The boundary is that a source date is not a guarantee of truth. It is a traceability marker. A recent source can still be wrong, biased, incomplete, or poorly interpreted. The date only helps the reader understand the time context of the claim.

Source dates matter most when a page explains prices, legal rules, API behavior, product limits, public health guidance, travel requirements, or fast-moving technical features. In those cases, a clear date can prevent someone from reusing a note after the underlying source changed.

A practical interpretation: every durable summary should show when the source was checked and which part of the source the note relies on. That small habit makes later correction and comparison much easier.

Source date citation trail 2026

// COMMENTS

ON THIS PAGE

Source date citation trail 2026

// COMMENTS ↓ Newest First

ON THIS PAGE

// COMMENTS