Following a record through time
What this chapter does
A page can change, and the evidence it discusses can change too. This tutorial helps you compare a recorded earlier version with a later one, inspect the reason, and cite the version you actually read. It does not assume that every Counterpedia object has a revision history.
Reader outcome
Identify two versions of one record, read their differences and associated source context, and distinguish document, event, and revision dates.
Our example: the Titan investigation
OceanGate’s Titan was lost in June 2023. The NTSB public docket holds multiple investigative materials, while the Coast Guard Marine Board report is a later institutional report. A contemporaneous warning, a subsequently recovered record, and the later investigation’s interpretation are distinct dated sources. We use them to understand why evidence dates and publication dates cannot be collapsed, not to pretend they are versions of one document.
Before you begin
Choose a Counterpedia record with at least two visible revisions. If the Titan subject has no recorded revision pair, use another real history-bearing record. Note its exact identity and both version labels; dates on external reports are not automatically Counterpedia revision numbers.
1. Open a real record history
Open the subject or record, locate any History or Versions view, and identify the current version and its predecessor. Note the version identifier or timestamp as displayed. If the only available material is a set of separate reports, do not call that a version history of the same object; instead compare them as documentary chronology.
2. Separate three clocks
Read each version’s recorded time and any source timestamps. The event, the document’s publication, and the record’s revision each have a different meaning.
| Clock | Titan illustration | What it tells you |
|---|---|---|
| Event time | Loss of the submersible in June 2023 | When the event occurred |
| Documentary time | Dated investigation materials and later reports | What a specific issuer recorded or concluded, at its date |
| Record history time | The actual revision shown in Counterpedia | When this Counterpedia object changed |
Expected result: you know whether a date belongs to the subject’s history, the source, or the page itself.
3. Compare one changed statement
Place the earlier and later record versions side by side, or read them in sequence. Select a changed statement, citation, status, or qualification. Record the earlier wording and the later wording without losing which edition contains which. If only formatting changed, say so instead of inventing a substantive correction.
4. Look for the reason and evidence
Inspect the revision note, decision or source reference when the record provides one. Then open the identified evidence, if authorized. In the Titan example, a 2025 official report can interpret data gathered in 2023, and a 2018 industry warning can describe earlier concerns. Neither document alone establishes what each 2023 decision-maker subjectively knew. Preserve the different questions and authors.
5. Read a refusal or reconsideration in its own terms
If the selected record includes a refused proposition, supersession, or reopened issue, inspect the exact statement, reason, and any stated reopening condition. If it does not, leave that feature out of the worked example and use a separately identified record only when available. A refusal isn’t a technical error; an unresolved question isn’t a negative finding.
6. Follow a successor without rewriting the past
If a successor record or revision exists, open it and note the link back to the earlier version. Compare what it adds, retracts, or reframes. A later revision is not automatically stronger merely because it is newer; it may have more evidence, different scope, or a changed editorial judgment.
7. Cite the exact version
Write down the record title, producer, exact record and version identity, date or revision context, and the statement or source you used. Where a cited source has its own edition, include that too. Do not treat a persistent route to the current version as proof you can retrieve an older one indefinitely.
Expected result: you can tell another reader which version informed your account, how it differed, and what record supports the reason for the change. Continue with Evidence and uncertainty or Saving and citing.
Corresponding overview
Understand how knowledge changes