Make the receipt easy to cite.

How to cite a Redacted Forge page

Use the page or asset's displayed title, Redacted Forge as publisher when no named author is shown, the displayed version or last-material-update date when available, and the canonical URL.

Recommended pattern:
[Title]. Redacted Forge. Version [version or update date]. [canonical URL]

When a page provides its own suggested citation, use that version because it is tied to the asset's version history.

Original maps, timelines, datasets, indexes, and graphics

Qualified original Redacted assets should publish a citation manifest containing methodology, source bibliography, publisher/authorship, publication/update dates, version, canonical URL, correction state, and asset-specific reuse status.

Citation and linking are encouraged for public, current assets. That does not automatically grant permission to reproduce, redistribute, sell, modify, or commercially license the full asset. Follow the reuse state displayed with that specific asset.

Third-party records stay third-party

Historical photographs, archival scans, government records, newspaper images, museum objects, licensed media, quotations, and other source materials can carry rights separate from Redacted Forge. Redacted Forge cannot grant rights it does not control.

If a Redacted asset contains third-party material, the asset should identify that fact and preserve the source institution's or rights holder's terms. A Redacted citation manifest never relicenses underlying third-party material by implication.

Corrections and superseded assets

Citations should point to the current canonical version when possible. If an original map, timeline, dataset, or Evidence Page is materially corrected or superseded, its citation record should preserve the old version state and point to the replacement or correction rather than silently changing history.

Reuse beyond ordinary citation/linking

Some original assets may later be available for explicit reuse, embedding, classroom distribution, institutional licensing, data/API access, book/audio adaptation, or compilation/OTT use. Those permissions exist only when the asset displays explicit terms or a real agreement covers the use.

Until specific terms are shown, do not infer a blanket open-content license from the fact that an asset is publicly viewable.