Engineering: Probe-Linked Contagion
Plot Beats
The narrative micro-steps within this event
Geordi hustles between stations, scribbling on a PADD as systems teeter; a com sounds and he lunges to answer, his movement compressing routine troubleshooting into urgent triage.
Geordi tells command he can rule out a design flaw and connects the Yamato's destruction to an alien probe, but demands to see the probe itself to prove the link.
Picard presses for an explanation of the Enterprise's failures; Geordi admits he cannot yet account for how the probe would affect their ship, leaving the threat ambiguous and unresolved.
Geordi warns the problems may escalate to Yamato-level severity and pleads for time to investigate; Picard snaps back that time is their scarcest resource, compressing the window for action and raising the stakes.
Who Was There
Characters present in this moment
Calmly authoritative but quietly anxious — professional composure that carries an undercurrent of mounting alarm.
Provides the scene's connective tissue through a captain's log voiceover and direct com queries; presses Geordi for progress and frames the engineering failures against the Yamato precedent, imposing urgency and command perspective.
- • Ascertain whether the Enterprise's failures match the Yamato's catastrophe.
- • Obtain actionable information quickly to guide containment and command decisions.
- • The Yamato's fate is the most relevant precedent and may inform their response.
- • Time is scarce; slow investigation risks repeating catastrophe.
Driven and anxious — confident in his analytical lead yet unsettled by the unknown mechanism and the potential speed of spread.
Frantic, focused: hurries between consoles with a PADD, annotating and cross‑checking the Yamato's log, deduces a probable link to an alien probe, admits he cannot yet explain the mechanism, and urgently requests physical access to the probe to prove the connection.
- • Validate the hypothesis by examining the physical probe to convert inference into proof.
- • Gain enough time and access to develop a defensive or corrective engineering response.
- • The Yamato's log contains the critical evidence linking the failures to a foreign device.
- • The system failures are not random design flaws but symptomatic of a contagion-like influence that could escalate rapidly.
Objects Involved
Significant items in this scene
Geordi holds and actively consults this PADD, which displays and annotates the Yamato's diagnostic logs; it functions as the tangible evidence that converts abstract system glitches into a traceable data trail implicating an alien probe.
Location Details
Places and their significance in this event
The Iconian Homeworld is referenced as the Enterprise's destination, providing geopolitical and narrative stakes; its mention frames the probe's possible origin and the larger risk if advanced Iconian tech is involved.
Main Engineering is the operational crucible for this discovery: technicians bustle, consoles are active, and Geordi moves between stations to synthesize ship data with the Yamato's logs, turning scattered failures into a single, actionable lead.
Narrative Connections
How this event relates to others in the story
No narrative connections mapped yet
This event is currently isolated in the narrative graph
Key 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."