A chronology is not yet a version history.
Putting these documents in order helps explain what could have been known at each stage. You finish with the accounts and documents in sequence, and a clearer sense of what each could establish at the time.
Comparing actual versions of the same Counterpedia record is a further step when a suitable edition pair is available. Publication dates of separate documents do not, by themselves, constitute a Counterpedia revision history.
When does a sequence of documents become a version history?
Dates in a row look like history. They are not the same as versions of one record. This journey builds a chronology and then tests whether it is a revision history — and here it is not.
See the subject in Counterpedia Titan · research Entry · Research · not admittedOr begin with step 1 ↓A reading exercise
A timeline is not a version history
Compare a dated Titan document with the question of whether one Counterpedia record has two editions.
Titan document chronology
These Titan materials give each document its own date, but they do not sort the documents for you, and the dates are of different kinds: when something happened, when a document was issued, and when it was published or released. You build the timeline yourself.
Titan · research dossier and document leads Research · not admittedCoast Guard report
This Coast Guard report is one document in that timeline. A later publication date does not make it a newer edition of a Counterpedia record.
U.S. Coast Guard Marine Board · Titan investigation, redacted report (4 Aug 2025) Original publisher materialSee the distinction
To compare versions, you need the same record identified twice and each version named. This example shows what to say when that pair is not available.
Carry this forwardWhen the pair is missing, report the timeline honestly; do not invent a before-and-after comparison.
Follow the trail
- 01
Read the Titan dossier
The loss of the Titan submersible in June 2023 was followed by public statements and later investigative material. The dossier points to dated document leads and the source inventory for them. Treat each lead as a separate publisher document, not as an edition of one Counterpedia record. Record the issuer and date of each lead before you use it; together they document a developing account, which is not yet a version history.
Open Titan · research dossier and document leads Research · not admitted
Keep: A dated list of Titan document leads, none described as a record revision.
- 02
Add the later investigative material
Later investigative material about the loss is one more set of dated publisher documents in that developing account, not a revision of anything that came before. Use the source inventory to keep each document's issuer and date attached, and place it in the sequence by both. Treat it as further material from a named body, never as a later state of an earlier statement or of any other item already in the dossier.
Open U.S. Coast Guard Marine Board · Titan investigation, redacted report (4 Aug 2025) Original publisher material
Keep: Each later document's issuer and publication date, not an invented edition.
- 03
Order the documents
Arrange the document leads into a dated sequence, keeping each date’s kind visible: event or underlying, issue, publication or release. Identify what each document could establish, and record when it became public only where that date is given. Keep internal record revisions and the history of your own session separate from the documents’ dates. Where a publication or release date is not given, mark it unknown rather than substituting another kind of date.
Open Titan · research dossier and document leads Research · not admitted
Keep: A dated document sequence with date kinds labelled and unknown publication or release dates marked, kept separate from Counterpedia record revisions.
- 04
Test for a same-record pair
Ask the only question that governs version history: can any two of these be identified as the same object at two recorded revisions? A valid comparison needs two recorded states, verified version identifiers, and dated changes between them. Publication dates alone do not make an edition pair, and the current Titan leads do not establish a same-record revision pair. A later report or a saved conversation is not a revision of a public object.
Keep: A yes-or-no finding on whether two revisions of the same record exist here.
- 05
State the honest result
Finish with the dated document sequence you constructed from the leads, each date keeping its kind, and an explicit finding that no same-record revision pair was established for Titan in this release. When two real recorded states of one record exist, the result is a version-specific comparison of what changed and when. Where they do not, the correct result is that the required version pair is unavailable, and no comparison is manufactured to fill the gap.
Keep: A dated document sequence preserving each date’s kind, with unknown publication or release dates marked, and an explicit “no version pair established” conclusion.
Open the material
- Titan · research EntryResearch · not admitted
- Titan · research dossier and document leadsResearch · not admitted
- U.S. Coast Guard Marine Board · Titan investigation, redacted report (4 Aug 2025)Original publisher material
Research material is not admitted evidence; publisher links identify someone else’s document.
What to notice
- A chronology of separate documents is not a revision history.
- A later report is not a new version of an earlier one, and a later publication or a saved conversation is not a revision of a public object.
- What was knowable at the time is not the same as what is known now.
- Internal record revisions, external publication dates and session history answer different questions and must stay distinct.
A useful finish
A dated sequence of the document leads in which each date keeps its kind (event or underlying, issue, publication or release) and publication dates that are not given stay marked unknown, with an explicit statement that no Counterpedia edition pair was established and that the required version pair is unavailable here.
Worked example
Observed on 4 November 2026 on the public site, signed out. This is what one actual run of these steps produced.
Document leads: the Titan entry lists 14 publisher documents, each with a labelled date or period and 9 with a recorded issuer. None is described as a revision of a Counterpedia record.
Same-record pair: none. Titan shows one record state, and its history, versions, compare and revisions pages return “This page could not be found.”
Ordering: this run put the dates in order but treated every date as a publication date, although some were underlying or issue dates. Steps 3 and 5 were therefore done again on 5 November; see the later checks.
Finish: the limitation finish. No version comparison was made, because no version pair exists here.
What it rests on
- Counterpedia's Titan research entry, marked “Research entry · Not admitted”, and its research dossier.
- The dates as the product records them on the 14 document cards.
What it did not establish
- Both 2025 Coast Guard report links, the one on this page and the different address the dossier records, returned 403 to this run. The report's dates were not checked against a document, and whether the two addresses serve the same file is not established.
- No two recorded states of one record exist here, so no version comparison was possible.
Later check, 5 November 2026: Steps 3 and 5 were run again on the public site, signed out, against the corrected instructions. The result is a dated sequence of the 14 leads plus the loss itself (18 June 2023), each date keeping its kind: for example, the Spencer Composites report's issue date (25 June 2015), the Dive 80 monitoring data's underlying date (15 July 2022), and the Coast Guard report's document date (4 August 2025) and public release date (5 August 2025). Two cards give a bare “Date” whose kind the product does not state, and those stay unlabelled.
Later check, 5 November 2026: A publication or release date is given for 5 of the 14 documents and marked unknown for the other 9. The NTSB report, opened directly, is dated 2 October 2025 on its cover but gives no release date, so its release date stays unknown. Date-like parts of web addresses were not treated as publication dates.
Later check, 5 November 2026: Conclusion: no same-record revision pair was established for Titan; the required version pair is unavailable here, and no comparison was manufactured. The history and version pages were checked again and still return HTTP 404 (not found). Apart from the NTSB report, the dates rest on the product's records; the Coast Guard originals were not retried.
If it stops
- This journey does not invent a version comparison to satisfy the experience.
- Version-aware comparison requires two actual revisions of one record.
- Titan is an illustrative subject, not an established two-version specimen; nothing here implies that a version pair exists.
- The method applies to any record with two real recorded states; the named subject neither defines it nor limits where it can be used.
Go deeper
Before you go deeper: The first chapter, Following a record through time, describes the full version workflow and needs a record with at least two recorded revisions. Titan has none in this release, so follow the chapter's own instruction: use another real record that has a history, or keep Titan as a dated document sequence. Its comparison steps are not something this page completed.