What counts as a “correction” here?
The archive contains both hard observations and human interpretation. We correct factual and provenance errors quickly. Interpretations aren’t “corrected” — they’re debated, labeled, and updated as evidence improves.
Correction
A factual or provenance error: wrong attribution, incorrect location precision, mislabeled source type, misquoted citation, or a mistake that could change how readers interpret a site/claim.
Update
New evidence or additional context that changes the “state of play” but doesn’t invalidate the prior text. Example: adding a new measurement photo, expanding context, or a curator note.
Clarification / Safety Change
A wording improvement, scope clarification, or a safety/heritage protection adjustment (like reducing coordinate precision). These are logged, but may omit sensitive details by design.
How we decide
- We separate observation from interpretation. If the issue is interpretive, we steer it into a Claim Thread with labels.
- We require sources. A correction request needs a link/ID and supporting evidence or reasoning.
- We prefer minimal edits. Fix the error, preserve what still holds, and document the delta.
- We protect sites and people. Privacy and heritage safety can override “full transparency” on exact details.
Where notices appear
- Major corrections get an advisory line near the top of the affected page(s).
- All logged changes appear in the Corrections Log below with a stable ID.
- Thread-level corrections may be added as a moderator note inside the claim discussion.
- Policy changes are logged, with an effective date.
Request a correction
Found an error? Amazing. That’s the archive doing its job. Paste the link (or object ID), tell us what’s wrong, and include any supporting sources. We’ll log the outcome either way.
Corrections Log
A living record of changes. Major corrections include what changed and why. Updates capture new context and improved provenance. Safety changes are logged without revealing sensitive details.
-
Jan 8, 2026Correction
EA-2026-001 — Baalbek dossier: corrected provenance labeling on hero gallery item
One image previously labeled as Primary (Original) has been relabeled to Secondary (Repost) with attribution, after a contributor flagged the original publication source. The image remains visible, but provenance now matches the evidence rules.
-
Jan 8, 2026Update
EA-2026-002 — Added “coordinate precision” note to multiple site templates
Updated site templates to display a clear indicator when a location is shown approximately (heritage protection). This improves transparency without exposing sensitive coordinates.
-
Jan 7, 2026Clarification
EA-2026-003 — Evidence Standards: clarified “observation vs interpretation” wording
Clarified language to distinguish what is directly observed in an image/measurement versus what is inferred. No policy change—just a sharper line between the two categories.
-
Jan 6, 2026Update
EA-2026-004 — Claims UI: added “Change my mind” prompt helper
Added a short prompt under the “Change my mind” field to reduce performative certainty and encourage testable claims. This aligns the UI with structured debate mechanics.
-
Jan 4, 2026Correction
EA-2026-005 — Map preview card: corrected evidence-count display rounding
Fixed a rounding bug in the “Evidence Density” indicator that could overstate counts on low-evidence sites. Visual indicator now matches the underlying count.
-
Dec 30, 2025Retraction
EA-2026-006 — Removed a duplicated media item presented as original field evidence
An upload was presented as a first-hand capture but matched an existing published image. The duplicate was removed, and the contributor was asked to resubmit with proper attribution if appropriate.
Become a Founding Contributor
Get first access to the live archive, change alerts, and early invites to “Pattern Hunts.” Your email is the key that unlocks the full map interactions and submission tools.
Related trust pages
Corrections are downstream of standards. These are the “rules of the game” that make the log meaningful.
Evidence Standards
Provenance fields, labeling, citation rules, and how we separate observation from interpretation.
Privacy & Safety
How we protect people and sites, handle sensitive locations, and respond to safety issues fast.
Credibility Policy
How we avoid hype, keep the archive honest, and “bridge back to process” when controversy spikes.