Timebase Mismatch — Romulan Logs Forged
Plot Beats
The narrative micro-steps within this event
Data reveals the basis of the charges against Worf's father, presenting captured Romulan logs that implicate Mogh in the Khitomer attack.
Geordi and Riker question the authenticity of the logs, prompting a cross-check with the Intrepid's sensor logs to verify the data.
Data and Geordi analyze the logs, discovering a timebase mismatch that exposes the falsification of the records.
Geordi concludes that the logs have been rewritten, confirming a deliberate frame-up of Mogh.
Who Was There
Characters present in this moment
Narrative Connections
How this event relates to others in the story
Across episodes
"Data’s assertion in The Offspring that Lal includes 'psychological inhibitor safeguards' to prevent threats to the Enterprise foreshadows his role in Sins of the Father where he meticulously uncovers an inhibitor (timebase mismatch) in Romulan logs that reveals the true traitor."
Creation and Consequence: Picard Confronts Data About Lal"Both events involve the manipulation of records and the search for truth amidst conflicting narratives: the Romulan survivor's status in Episode 7 and the forged Romulan logs in Episode 17."
Wounded Romulan Brought Aboard — Security Clashes with Medicine"The revelation of forged Romulan logs in Episode 17 foreshadows the Borg's ability to adapt and analyze Starfleet defenses in Episode 26, escalating the threat from political manipulation to technological overpowering."
The Borg Strike: Tractor Beam Lock and the First Test of Adaptive DefensePart of Larger Arcs
Key Dialogue
"DATA: Commander, I have discovered the basis of the charges against Worf's father."
"GEORDI: Look at this... just before the Intrepid gap begins, the timebase of both files are in perfect sync... but look at the signals just after the shields dropped."
"GEORDI: Commander, somebody's been rewriting history."