Picard Frames a Shipwide Contagion
Plot Beats
The narrative micro-steps within this event
THE ENTERPRISE positions itself en route to Iconia, placing the ship and crew on a collision course with whatever threat lies there.
PICARD delivers a supplemental log entry: the Enterprise endures random system failures that mirror the Yamato's catastrophe, framing the ship's malfunctions as part of a larger, possibly contagious problem.
Who Was There
Characters present in this moment
Measured but clearly concerned; a commander projecting control while compressing urgency into the chain of command.
Delivering a supplemental captain's log via ship comm that reframes random system failures as possibly related to the Yamato's destruction; pressing engineering for answers and compressing strategic urgency into direct questions.
- • Establish whether the Enterprise's failures are the same threat that destroyed the Yamato.
- • Force engineering to prioritize investigation and immediate mitigation.
- • Conserve time and resources; compel faster decision-making under uncertainty.
- • The Yamato's fate is a relevant precedent and may be causally linked to current failures.
- • Time is a critical, limited resource and warrants decisive action even without full information.
Frantic momentum tempered by technical sobriety — urgently worried but concentrating on testable leads.
Rushing among consoles in Main Engineering holding and annotating a PADD; verbally reports that the Yamato's logs implicate an alien probe but concedes that without physical access to the device he cannot explain or fully diagnose the Enterprise's failures.
- • Determine whether the alien probe caused the Yamato's destruction.
- • Acquire the probe (or access to it) so forensic diagnostics can explain the Enterprise anomalies.
- • Buy enough time to run analyses and propose containment measures.
- • The Enterprise's issues are not due to a design flaw.
- • The Yamato's diagnostic logs contain critical evidence implicating an outside technological agent.
- • Physical access to the probe is necessary to provide a complete explanation or fix.
Objects Involved
Significant items in this scene
Geordi uses the Engineering PADD to display and annotate the Yamato's diagnostic log entries, turning scattered error reports into a focused line of evidence. The PADD functions as the immediate conduit for linking past catastrophe to present anomalies and as Geordi's working tool for rapid hypothesis formation.
Geordi uses the Engineering PADD to display and annotate the Yamato's diagnostic log entries, turning scattered error reports into a focused line of evidence. The PADD functions as the immediate conduit for linking past catastrophe to present anomalies and as Geordi's working tool for rapid hypothesis formation.
Location Details
Places and their significance in this event
Iconian Homeworld is referenced as the Enterprise's destination and the geopolitical locus that raises the stakes for the diagnostic work: the presence of Iconia ties scientific findings to strategic consequence.
Main Engineering serves as the operational crucible where diagnosis and immediate action converge: consoles, stations, and technicians form the physical locus for Geordi's analysis and the relay of critical information to command.
Narrative Connections
How this event relates to others in the story
Across episodes
"Geordi's experience with overdue deuterium conduit maintenance ( Epis 10) establishes his technical vigilance under operational constraints, echoing his rapid analysis of the Yamato's system failures (Epis 11) caused by an alien program."
Overdue Deuterium Maintenance Forces Standard Orbit"The operational constraint of lost warp capability in 'The Dauphin' due to overdue deuterium conduit maintenance teaches Geordi patience and prioritization. This experience informs his rapid, focused triage of cascading system failures in 'Contagion,' where he must stabilize urgent crises without the luxury of extended analysis."
Engineering Grounds the Ship — Wesley Sent to Stores"Geordi's experience in diagnosing an alien program's infiltration in Episode 11 (Contagion) directly enables his rapid technical assessment of an unknown interference source in Episode 12 (The Royale). In both episodes, he identifies systemic corruption/malfunction using sensor data and diagnostic tools."
Phantom Interference — Beam-Out Denied"Geordi's role as the 'Engineering hands' persists across episodes - in Episode 11 he is 'frantic and pragmatic' in diagnosing the alien program's spread, and in Episode 12 he immediately assumes a similar 'clinical' role, reading out sensor data on Theta Eight."
Orbit Over Theta Eight — The Hard DataKey Dialogue
"PICARD (V.O.): Captain's log, supplemental. As happened with her sister, the Enterprise is being plagued by a series of system failures. So far they are random, but perhaps early symptoms of what happened to the Yamato."
"GEORDI: A solution, no sir, but I can eliminate one worry. It is not a design flaw. I've been reviewing the Yamato's log, and I think maybe that alien probe had something to do with her problems."
"PICARD'S COM VOICE: Lieutenant, time is the one thing which we do not have in abundance."