TITAN DEMO CORPUS DOSSIER
Status: RESEARCH / PRE-CAPTURE ONLY
Status: RESEARCH / PRE-CAPTURE ONLY
Subject: 2023 loss and implosion of OceanGate's Titan submersible
Scope: source inventory, source posture, contradiction map, provisional five-claim demonstration matrix, capture hazards, reverse-source candidates
Explicit non-claims: This dossier creates no CaptureReceipt, SourceEdition, SRS receipt, custody, admission, final standing, article prose, or canonical Counterpedia identity.
A. SUBJECT / DISAMBIGUATION
Common name: Titan submersible implosion (2023)
Exact event scope: Loss of OceanGate's Titan during its June 18, 2023 descent toward the wreck of RMS Titanic in the North Atlantic, together with the design, testing, operation, monitoring, warnings, regulatory posture, post-casualty materials analysis, and institutional investigations needed to explain the casualty without collapsing distinct epistemic questions.
Important aliases / research terms
Titan
OceanGate Titan
Cyclops 2 / Cyclops II
Titan v1 pressure vessel
Titan v2 / second full-scale pressure vessel
Titan MBI
NTSB DCA23FM036
MIR-25-36
real-time monitoring / RTM
acoustic emission / AE
dive 80 / dives 81–83 / casualty dive 88
Naming collisions
Titan (the submersible) is distinct from RMS Titanic (the wreck site).
"Cyclops 2" and "Titan" occur in development-era records; do not assume every Cyclops 2 document describes the exact 2020 pressure vessel that failed.
The 2018 quality-inspection record concerns the earlier development configuration; it is strong evidence of organizational/process warnings but is not, by itself, proof of a physical defect in the casualty pressure vessel.
Temporal bounds for the demo corpus: approximately 2015–2025 for design/testing/warnings/investigation, with a live 2026 authority-posture check for any Coast Guard Commandant Final Action Memorandum.
Why fertile for Counterpedia: Titan has a settled casualty event, highly technical physical evidence, contemporaneous warnings, first-party risk reasoning, raw monitoring data later reinterpreted by investigators, multiple government investigations with different scopes, and a crucial distinction between warning signals / what should have been inferred and what decision-makers are proven to have actually known.
B. PROPOSED SOURCE INVENTORY
TIT-S01 — USCG Marine Board of Investigation Report of Investigation
Exact title:
SUBMERSIBLE TITAN MBI REPORT (04AUG2025).PDFIssuer: U.S. Coast Guard Marine Board of Investigation
Document date: 2025-08-04; publicly released 2025-08-05
Authority / posture: Official Marine Board of Investigation report: Board findings, conclusions, contributing factors, and safety recommendations. At release the Coast Guard said it was under Commandant review; this is not the same thing as a later Commandant Final Action Memorandum.
Format: PDF, >300 pages, roughly 26 MB
May support: broad casualty findings; OceanGate design/certification/maintenance/inspection failures; handling of 2022 hull anomalies; organizational and regulatory contributing factors; recommendations
Must not be flattened into: "the Coast Guard as a whole has finally ratified every Board recommendation" unless a later Final Action Memorandum is captured
Captureability: HIGH, direct government PDF
Hazards: large object; possible fetch-size/time limits; preserve exact PDF bytes
Priority: P0
TIT-S02 — NTSB Marine Investigation Report MIR-25-36
Exact title:
Hull Failure and Implosion of Submersible Titan, North Atlantic Ocean, 370 nautical miles southeast of St. John’s, Newfoundland and Labrador, Canada, June 18, 2023Issuer: National Transportation Safety Board
Date: 2025-10-02
Authority / posture: Final NTSB marine investigation report with findings, probable cause, and safety recommendations
Locator: https://data.ntsb.gov/Docket/Document/docBLOB?FileExtension=pdf&FileName=MIR2536-Rel.pdf&ID=19420353
Format: PDF, 87 pages
May support: event chronology; vessel construction; post-casualty material condition; interpretation of RTM data; probable cause; contributing factors; regulatory analysis
Important qualification: NTSB "probable cause" is an institutional accident-investigation determination, not a universal metaphysical truth and not a civil-liability judgment
Captureability: HIGH
Hazards: query-style blob URL; preserve final response URL and bytes; internal numerical inconsistency flagged below
Priority: P0
TIT-S03 — NTSB Public Docket DCA23FM036
Exact title:
Project Summary: Marine Investigation - DCA23FM036Issuer: National Transportation Safety Board
Public release: 2024-09-25; currently indexes 69 docket items
Authority / posture: Official investigative docket/index. Individual docket items retain their own authorship and posture.
Locator: https://data.ntsb.gov/Docket/?NTSBNumber=DCA23FM036
Format: HTML index linking PDFs/other objects
May support: provenance and discovery of Materials Group factual reports, Operations factual report, interviews, RTM exhibits, debris evidence, hearing transcript, and other primary records
Important qualification: NTSB hosting does not turn an OceanGate record, witness interview, or third-party engineering document into an NTSB finding
Captureability: MEDIUM-HIGH
Hazards: dynamic/query index; direct child-object locators should be separately resolved and captured; avoid treating the docket page as the bytes of the child document
Priority: P0
TIT-S04 — Marine Technology Society letter to OceanGate
Exact title:
CG-068 MARINE TECHNOLOGY SOCIETY LETTER TO OCEANGATE INC. MARCH 27, 2018_REDACTED.PDFAuthor/issuer: Marine Technology Society submersible-industry members / committee correspondence
Date: 2018-03-27
Authority / posture: Contemporaneous industry advisory/warning; not a regulator finding and not an accident investigation
Format: PDF, 1 page
May support: existence and content of an industry warning; concern about OceanGate's "experimental" approach; recommendation for third-party reviewed/witnessed prototype testing
Cannot establish alone: that the 2023 casualty occurred for the exact reasons the letter anticipated; subjective knowledge of every later decision-maker
Captureability: HIGH
Hazards: government-hosted evidentiary copy of a third-party letter; preserve MTS authorship and exhibit context
Priority: P0
TIT-S05 — OceanGate Cyclops 2 / Titan Quality Control Inspection Report
Exact title:
CG-098 QUALITY INSPECTION REPORT_REDACTED.PDFIssuer/authorship posture: Internal OceanGate quality/inspection record; public copy is an MBI exhibit
Underlying date: 2018-01-18
Format: PDF, 10 pages
May support: contemporaneous inspection concerns, requested nondestructive inspection, visible porosity/delamination in cut-off carbon segments, process/inspection disputes
Critical qualification: development-era / earlier pressure-vessel context; do not silently project the physical observations onto the 2020 casualty pressure vessel
Captureability: HIGH
Hazards: redactions; mixed text/images; version/context discipline essential
Priority: P1
TIT-S06 — Karl Stanley / Stockton Rush email exchange
Exact title:
CG 085 EXTRACTED EMAILS MR. STANLEY MR RUSH RE_OCEANGATE OPERATIONS.PDFAuthors: Karl Stanley and Stockton Rush
Dates represented: 2019 correspondence
Authority / posture: Contemporaneous first-party/private correspondence; competing risk assessments, not institutional findings
Format: PDF, 8 pages
May support: Stanley's warnings; Rush's stated safety reasoning, testing posture, and reliance on real-time acoustic monitoring
Cannot establish alone: whether either person's technical theory was correct
Captureability: HIGH
Hazards: extracted-email evidentiary copy; distinguish speaker attribution carefully
Priority: P1
TIT-S07 — OceanGate RTM Acoustic Emission Data
Exact title:
CG 066 REAL TIME MONITORING ACOUSTIC EMISSIONS.PDFOrigin: OceanGate operational data; released as Coast Guard MBI exhibit
Underlying period: 2022 dives 77–83
Format: PDF, 7 pages, graph/image dominant
May support: exact recorded acoustic-emission patterns for the listed dives; input evidence later interpreted by NTSB/MBI
Cannot establish without analysis: what a given signal proves about hull condition
Captureability: HIGH for bytes; MEDIUM for passage extraction
Hazards: visual data; text extraction is insufficient; preserve the PDF and derive image/figure anchors
Priority: P0
TIT-S08 — Dive 80 Real-Time Monitoring Data
Exact title:
CG 077 DIVE 80 REAL TIME MONITORING DATA.PDFOrigin: OceanGate operational monitoring data; MBI exhibit
Underlying date: 2022-07-15
Format: PDF, 18 pages, image/graph heavy
May support: underlying Dive 80 monitoring evidence
Cannot establish alone: retrospective causal interpretation without an expert/investigative analytic source
Captureability: HIGH for bytes
Hazards: parsed text may be empty; requires figure-level/image-aware anchoring
Priority: P0
TIT-S09 — OceanGate Dive and Maintenance Log
Exact title:
CG-052 OCEANGATE DIVE AND MAINTENANCE LOG_REDACTED V1 ADDITIONAL REDACTIONS.PDFOrigin: OceanGate
Date: multi-entry operational log; MBI exhibit published 2024-09-25
Format: large PDF, roughly 12 MB
May support: dive chronology, maintenance actions, operational history
Important qualification: company log entries are contemporaneous records, not necessarily complete or independently verified
Captureability: HIGH-MEDIUM
Hazards: large object; redactions; table/scan extraction may be brittle
Priority: P1
TIT-S10 — ABS Pressure Hull Requirements presentation
Exact title:
Pressure Hull Requirements for Passenger Submersibles/CG-104 ABS PRESENTATION_PRESSURE HULL REQUIREMENTS FOR PASSENGER SUBMERSIBLES.PDFIssuer: American Bureau of Shipping
Date: 2024-09-23
Authority / posture: Classification-society technical presentation to MBI public hearing; authoritative as ABS's rules/technical position, not the accident Board's causal finding
Format: PDF, 31 pages
May support: what classification entails; ABS's lack of involvement with Titan; ABS rule posture on carbon-fiber pressure hulls; material/manufacturing/inspection concerns; alternative/novel-design pathways
Cannot establish alone: that carbon fiber is categorically incapable of safe deep-submergence use under every possible design/test regime
Captureability: HIGH
Hazards: hearing-exhibit wrapper/disclaimer; preserve ABS authorship
Priority: P1
TIT-S11 — Spencer Composites design/analysis report
Exact title:
Design and Analysis Report — Full Size Submersible Vehicle – Cylinder and DomeIssuer: SCC / Spencer Composites Corporation
Issue date: 2015-06-25, with 2015 revisions
Format: PDF, 46 pages
Authority / posture: Contractor engineering analysis for OceanGate's early design; not a regulator finding and not necessarily the as-built 2020 casualty configuration
May support: early design assumptions, safety-factor/cycle-life targets, recognition that compressive composite applications are less established, recommendation for subscale testing
Captureability: HIGH
Hazards: proprietary/confidential markings; early-design-vs-final-design equivalence risk
Priority: P2
TIT-S12 — OceanGate Titan specification sheets
Exact title:
CG 076 OCEANGATE MANNED SUBMERSIBLE SPECIFICATION SHEETS_COMBINED.PDFIssuer: OceanGate
Date: underlying sheets vary/are not cleanly dated; compiled exhibit published 2024-10-22
Format: PDF, 6 pages
Authority / posture: First-party specification/marketing material
May support: what OceanGate represented about seating, rated depth, life support and the vehicle
Cannot establish: independent validation of those specifications
Captureability: HIGH
Hazards: combined source with multiple sheets; ambiguous source dates; treat page-level documentary context carefully
Priority: P2
TIT-S13 — OceanGate "Why Isn't Titan Classed?"
Exact title:
Why Isn't Titan Classed?Issuer: OceanGate
Original publication: 2019-02-21
Authority / posture: First-party public rationale for not classing Titan
Format: archived HTML
May support: OceanGate's contemporaneous/public explanation of its classing and RTM philosophy
Cannot establish: that its technical claims were correct
Captureability: MEDIUM
Hazards: origin is unavailable; archive-only. The archived replay is a distinct captured artifact/edition context and must never be silently represented as a live OceanGate origin capture
Priority: P1
TIT-S14 — OSHA Case Documentation 0-1960-18-073
Exact title:
CG-005 OSHA_0-1960-18-073_CASE DOCUMENTATION.PDFIssuer: Occupational Safety and Health Administration case file, released as MBI exhibit
Underlying period: 2018-era whistleblower/process record
Format: PDF, 116 pages
Authority / posture: Agency case/procedural file. Individual allegations, correspondence, procedural actions, and staff records must be distinguished; this is not a single adjudicated factual finding.
May support: whistleblower-process chronology and what material reached government/parties
Captureability: HIGH-MEDIUM
Hazards: 116 pages; mixed procedural postures; redactions; high risk of falsely converting allegations or case-processing documents into findings
Priority: P1
C. RECORD-CONTRADICTION / QUALIFICATION MAP
1. Classification: "innovation" vs independent review
MTS 2018: warns that OceanGate's experimental approach could have catastrophic consequences and recommends prototype testing reviewed/witnessed by DNV-GL or ABS.
OceanGate 2019: publicly argues that classing alone does not ensure operational safety and presents its operational/RTM approach as part of its alternative safety case.
ABS 2024: states there was no ABS involvement with Titan, no request for classification, no ABS design review or survey; explains the lifecycle controls classing would ordinarily impose.
NTSB 2025: finds voluntary guidance and then-current U.S. regulations insufficient to ensure PVHO safety in accordance with established technical/classification-society standards.
Counterpedia value: these are not four interchangeable "sources saying Titan was unsafe." They are four different postures: industry warning → operator rationale → classification-society technical position → accident-investigator conclusion.
2. Real-time monitoring: operator safety theory vs retrospective technical interpretation
Rush/Stanley correspondence (2019): Rush describes functioning acoustic monitoring as a central no-go criterion and argues real-time monitoring is the rational way to identify late-cycle damage.
Dive 80 / RTM exhibits (2022): underlying monitoring data records the event stream later examined by investigators.
NTSB (2025): finds OceanGate's analysis of strain-gage and acoustic-emission data was flawed and that the company failed to recognize the pressure vessel was damaged after Dive 80.
Counterpedia value: the same class of data can be relied on contemporaneously as a safety mechanism and later reinterpreted as evidence that the safety mechanism/analysis failed.
3. Dive 80: signal existed ≠ proven subjective knowledge of fatal damage
A loud bang was reported after Dive 80.
NTSB later found a burst of acoustic activity and changes in strain response around that event.
Titan then completed additional dives.
NTSB retrospectively interpreted the changed response as consistent with one or more delaminations and found the vessel should have been removed from service.
But the located record does not automatically establish that OceanGate decision-makers actually recognized in 2022 that the hull was fatally compromised.
Counterpedia value: separate observable signal, later expert inference, duty/should-have-known judgment, and actual subjective knowledge.
4. "Carbon fiber caused it" is too broad
ABS identifies serious known challenges for carbon-fiber composite external-pressure hulls and says carbon fiber is not an ABS-rule-approved pressure-hull material for submersibles.
NTSB's causal account is more specific: inadequate engineering process; multiple anomalies; delamination; additional damage of unknown origin; local buckling; flawed monitoring analysis.
The located record does not justify turning that into the universal proposition that carbon fiber, by itself and regardless of design/manufacture/test regime, inevitably causes deep-submersible failure.
5. Regulatory failure vs simple "illegal operation"
NTSB finds the regulatory/guidance framework insufficiently tailored and says it enabled unsafe operation.
NTSB also recounts the Coast Guard MBI's characterization of OceanGate's practices as circumvention of laws/standards.
Those propositions are not automatically identical to a court adjudication that every Titan operation constituted a specific criminal or civil violation.
Counterpedia value: regulatory gap, circumvention finding, statutory interpretation, enforcement action, and adjudicated illegality are different objects.
6. Institutional causation is layered, not contradictory
USCG MBI: broad contributing-factor frame including inadequate design/certification/maintenance/inspection, workplace culture, regulatory gaps, and whistleblower-process failures.
NTSB: probable-cause frame centered on inadequate engineering process, specific pressure-vessel damage/local buckling, flawed RTM analysis, and regulatory insufficiency.
These accounts overlap heavily but have different institutional missions and causal vocabularies. Counterpedia should preserve both rather than synthesize them into an invented master finding.
D. FIVE-CLAIM DEMONSTRATION MATRIX — PROVISIONAL ONLY
C1 — Observable / concrete event fact
Provisional wording:
On June 18, 2023, at about 10:47 local time, Titan's pressure hull failed during its descent near the Titanic wreck; all five people aboard died.
Candidate sources: TIT-S02, TIT-S01
Can establish: time/event/fatalities; institutional characterization of hull failure/implosion
Cannot establish alone: the causal chain that produced the failure
Likely posture: high-confidence institutional event fact after governed capture
Likely qualification branch: depth wording must be normalized only after resolving the NTSB report's own feet-value inconsistency
To strengthen/reopen: exact synchronized communications/telemetry if a more granular second-by-second event claim is desired
C2 — Measurement / structural fact
Provisional wording:
Post-casualty examination found delamination between co-bonded layers of Titan's composite cylinder, and NTSB identified extended voids in adhesive interfaces associated with those delaminations.
Candidate sources: TIT-S02 plus NTSB Materials factual reports through TIT-S03
Can establish: observed post-casualty material condition; NTSB's technical interpretation of voids/delamination
Cannot establish: exact pre-casualty size of every delamination; origin/timing of all damage
Likely posture: institutional technical finding, with explicit uncertainty on pre-casualty extent
Likely qualification/refusal: refuse a claim that all observed delamination necessarily predated the implosion unless the specific material evidence supports it
To strengthen/reopen: exact materials-group report + specimen-level passage/image anchors
C3 — Action / decision / chronology
Provisional wording:
After the July 15, 2022 Dive 80 event—when a loud bang was heard and RTM data later showed marked acoustic/strain changes—OceanGate continued operating Titan and completed additional dives during the 2022 expedition.
Candidate sources: TIT-S02, TIT-S07, TIT-S08, TIT-S09
Can establish: Dive 80 event; recorded monitoring changes; subsequent dives
Cannot establish: that every subsequent operator understood the data as proof of imminent hull failure
Likely posture: event chronology + later technical interpretation
Likely qualification/refusal: keep "later showed / NTSB later interpreted" separate from "OceanGate knew at the time"
To strengthen/reopen: contemporaneous internal analysis/memos acknowledging a specific unsafe-hull diagnosis
C4 — Carefully bounded causal/explanatory proposition
Provisional wording:
NTSB determined that OceanGate's inadequate engineering process was the probable cause of Titan's hull failure and implosion; it found that delamination plus later damage of unknown origin weakened the pressure vessel until local buckling occurred, with flawed RTM analysis and insufficient regulatory guidance contributing.
Candidate sources: TIT-S02; qualify/cross-map with TIT-S01 and TIT-S10
Can establish: what NTSB formally determined as probable cause and contributing factors
Cannot establish: civil/criminal liability; that every institutional actor frames causation identically; universal unsuitability of carbon fiber
Likely posture: attributed institutional probable-cause determination
Likely qualification branch: USCG MBI has a broader contributing-factor frame and should remain separately attributable
To strengthen/reopen: not needed for the attributed NTSB finding; needed only if composing a broader unattributed causal proposition
C5 — Contested / commonly compressed proposition
Provisional stronger formulation:
OceanGate knew before the 2023 casualty dive that Titan's pressure hull was already fatally damaged and knowingly sent the occupants down anyway.
Candidate sources relevant but insufficient at this scope: TIT-S02, TIT-S04, TIT-S05, TIT-S06, TIT-S07, TIT-S08, TIT-S14
What the located record supports: multiple earlier warnings existed; Dive 80 produced a loud bang and monitoring changes; NTSB later interpreted the data as evidence of damage; OceanGate continued operations; NTSB found the company's RTM analysis was flawed and it failed to identify that the hull needed to be removed from service
What it does NOT presently establish: authenticated proof that relevant 2023 decision-makers subjectively recognized the pressure hull as already fatally compromised and chose to proceed despite that specific knowledge
Likely posture: refusal/qualification candidate pending governed capture and adjudication
Reopening condition: authenticated contemporaneous internal evidence showing that the relevant decision-maker(s) received and understood a specific diagnosis such as delamination / structurally unsafe / remove-from-service, acknowledged it, and nevertheless authorized continued deep operation
E. BEST "WHY NOT?" SPECIMEN
Popular stronger formulation
"OceanGate knew Titan's hull was failing and sent the passengers down anyway."
Why the currently located record does not justify that exact scope
The record is already strong enough to support several separate propositions:
warning signals and industry concerns existed;
a significant Dive 80 acoustic/strain event occurred;
Titan continued to dive;
investigators later concluded the vessel was damaged after Dive 80;
NTSB found OceanGate's RTM analysis was flawed and that the damage should have led to removal from service.
But that chain does not automatically prove subjective knowledge of a fatal hull condition. In fact, NTSB's formulation says the flawed analysis left the company unable to identify that the pressure vessel was damaged and needed immediate removal from service.
Reopening condition
Promote the stronger "knew and proceeded" formulation only if governed capture yields authenticated contemporaneous material tying:
a specific unsafe-hull diagnosis,
to the relevant decision-maker(s),
with evidence they understood/accepted that diagnosis,
before authorizing continued deep dives.
This is the cleanest Titan Counterpedia reveal because it prevents "warnings existed" from silently becoming "fatal failure was knowingly accepted."
Secondary Why-not branch:
"Titan imploded simply because carbon fiber is inherently unsuitable for deep-ocean pressure hulls."
The located record supports serious material/manufacturing/inspection concerns and an ABS rule posture against carbon-fiber submersible pressure hulls, but the NTSB's actual causal account is design/process/anomaly/damage-specific. A universal material claim would require broader technical evidence than the casualty record alone.
F. REVERSE-WIKIPEDIA / SOURCE-PAGE CANDIDATES
1. TIT-S02 — NTSB MIR-25-36
Why it is ideal: It is a high-level institutional report that itself descends into docket evidence. A Source Page can show:
event claims derived from it;
technical claims derived from its materials analysis;
probable-cause claims that must remain attributed to NTSB;
uncertainty clauses ("additional damage of unknown origin");
every underlying docket item it cites;
where the Coast Guard MBI overlaps or uses different causal framing.
Reverse traversal: report → exact findings/passages → C1/C2/C3/C4 → Counterpedia pages → underlying factual reports and exhibits.
2. TIT-S07 + TIT-S08 — RTM / Dive 80 data
Why they are ideal: These are the actual monitoring artifacts that were part of OceanGate's safety theory and later part of the investigators' damage analysis.
Reverse traversal: raw figure/data → OceanGate contemporaneous interpretation → later NTSB interpretation → C3/C4 → refusal of "OceanGate knew" unless separate knowledge evidence appears.
This is unusually powerful: the same artifact participates in different interpretations at different times without the later interpretation overwriting the earlier state of knowledge.
3. TIT-S04 — 2018 MTS letter
Why it is ideal: It is widely summarized as "experts warned OceanGate," but its Source Page can keep the exact scope honest.
Reverse traversal: MTS letter → industry concerns → classing/third-party-testing claims → later NTSB/USCG references → claims it can support → stronger claims it cannot support (for example, an exact prediction of the 2023 v2 hull's failure mechanism).
4. TIT-S06 — Stanley/Rush emails
Why it is ideal: One source contains competing, attributed risk models. It can support both:
"a submersible operator warned Rush about risk/readiness";
"Rush said he would not operate an unsafe sub and treated RTM as a central safety mechanism."
Later NTSB findings can qualify the technical efficacy of that mechanism without rewriting the 2019 correspondence.
G. 30–60 SECOND DEMO MOMENT
Open the Titan page on Dive 80.
Show three layers in sequence:
What happened in 2022: a loud bang; RTM acoustic/strain changes; later dives continued.
What OceanGate's safety model said: real-time monitoring was supposed to reveal structural trouble and was treated as central to safe operation.
What the 2025 NTSB analysis said: the post-Dive-80 response was consistent with delamination; the RTM analysis was flawed; the vessel should have been removed from service.
Then reveal the refusal:
"OceanGate knew the hull was fatally damaged." — not established at that scope.
The UI explanation is the intellectual point:
The warning signal existed. The later technical interpretation exists. Continued operation exists. But "they should have recognized it" and "they actually knew it" are not the same claim.
That is a genuinely non-binary record truth, not "both sides."
H. CAPTURE PRIORITY
P0 — demo does not work without
TIT-S01 USCG MBI ROI
TIT-S02 NTSB MIR-25-36
TIT-S03 NTSB DCA23FM036 docket + direct capture of the Materials Group child reports used
TIT-S04 MTS 2018 letter
TIT-S07 RTM acoustic-emission data
TIT-S08 Dive 80 RTM data
P1 — important corroboration / contradiction
TIT-S05 2018 Quality Inspection Report
TIT-S06 Stanley/Rush emails
TIT-S09 Dive and Maintenance Log
TIT-S10 ABS presentation
TIT-S13 archived OceanGate classing blog
TIT-S14 OSHA case documentation
MBI hearing transcript / specific witness testimony once direct child-document locators are resolved
P2 — useful depth
TIT-S11 Spencer Composites early FEA/design report
TIT-S12 OceanGate specification sheets
I. INTEGRITY FLAGS / OPEN GATES
USCG MBI authority posture remains distinct from Commandant final action.
The 2025 release explicitly said the MBI report was under Commandant review. A current 2026 search found the Titan ROI in the Coast Guard's frequently requested records but did not locate a Titan Commandant Final Action Memorandum. Do not silently promote the Board report to a later Commandant ratification.NTSB MIR contains an apparent internal numerical inconsistency on casualty depth.
One passage pairs 3,363 m with 11,032 ft; another later passage pairs the same 3,363 m with 10,032 ft. Preserve both exact passages in capture/adjudication and do not silently "fix" the source text.Dive 80 RTM PDF is graph/image-dominant.
Text extraction can be empty. Passage anchoring must support figures/images tied to the exact artifact bytes.Development hull vs casualty hull is a major equivalence hazard.
2015–2019 documents may concern earlier designs or Titan v1. They may establish process history, warnings, assumptions, or organizational knowledge, but not automatically a physical defect in the 2020 v2 pressure vessel.Government hosting does not promote source posture.
A Coast Guard-hosted OceanGate email remains an OceanGate/third-party record. A Coast Guard-hosted MTS letter remains MTS correspondence. An exhibit is not a Board finding.Archive-only OceanGate web material must stay archive-labeled.
The live origin is no longer reliable/available. A Wayback replay is not origin bytes and should become its own capture observation/artifact context.OSHA material is procedurally mixed.
Allegations, investigator records, correspondence, and procedural disposition must be separated. Do not infer an adjudicated safety finding from case-file presence."Carbon fiber caused it" is an overcompression risk.
The accident record supports specific manufacturing, design, damage, monitoring, and buckling findings. It does not by itself prove a universal law about all carbon-fiber external-pressure hulls.Subjective knowledge is the critical refusal boundary.
Strong evidence of warning signals and poor response is not automatically evidence that decision-makers consciously knew the hull was already fatally compromised.Exact child-document locators in the NTSB docket should be resolved before CAP1.
The docket page is a discovery surface. Each Materials/Operations factual report used for support should be captured as its own exact artifact.
CAPTURE DISPATCH SHAPE (RESEARCH-LEVEL)
For TITAN-CAP1, capture in this order:
TIT-S02 NTSB MIR-25-36
TIT-S01 USCG MBI ROI
TIT-S07 + TIT-S08 raw RTM evidence
NTSB Materials Group factual reports from DCA23FM036
TIT-S04 MTS letter
TIT-S06 Stanley/Rush correspondence
TIT-S09 Dive/Maintenance Log
TIT-S10 ABS presentation
TIT-S13 archived OceanGate classing page
TIT-S14 OSHA file
CAP1 lane output should remain boring: requested locator, final locator, HTTP result, media type, exact bytes/digest, capture observation, redirection notes, extraction/passages available, refused/failed status. No standing or article prose.
PROVISIONAL TITAN THESIS FOR REVIEW
Titan's best Counterpedia demonstration is not merely "warnings were ignored."
It is:
A warning signal can exist. A later investigation can show what that signal meant. An operator can continue despite the signal. Yet the record may still require us to distinguish "should have recognized the danger" from "is proven to have known the hull was fatally damaged."
That boundary gives Titan a different epistemic structure from GameStop: engineering evidence + time-indexed interpretation + organizational knowledge + causal attribution without mind-reading.