Iconian Code Aboard: 'We're Sitting on a Bomb'
Plot Beats
The narrative micro-steps within this event
Geordi declares the spherical probe transmitted an alien computer program now present aboard the Enterprise and actively attempting to rewrite their software, framing the malfunction as an invasive, incompatible intelligence rather than a mechanical fault.
Data quantifies the threat—within hours the program learned and began reprogramming their database—and Picard and Geordi tie that capability to the Yamato probe, establishing causal link to the sister ship's destruction.
Riker connects the program to the ship's erratic instruments; Picard demands options and Geordi admits limited capability, converting technical explanation into a stark admission of vulnerability.
Riker questions how the program boarded despite no scan; Data reveals the Yamato log contained the program and the Enterprise's copy lodged in a specific mainframe section, and Geordi explains that localized deposition gives them limited breathing space.
Who Was There
Characters present in this moment
Cautious and resolute; medical teams are focused on patient triage and avoid risky automated systems.
Referenced by Data as the medical responders being dispatched via access tunnels under Pulaski's orders; they are portrayed as pivoting operations away from turbolifts toward safer, slower access routes.
- • Reach and treat injured crew without relying on compromised infrastructure.
- • Establish secure triage routes and stabilize casualties.
- • Turbolifts are unsafe given current system instability.
- • Patient outcomes depend on rapid, ground-level medical response even under constraints.
Concerned and urgent but outwardly controlled; his composure masks the recognition of strategic and moral consequences.
Picard leads the discussion, frames the forensic finding as a command problem, asks direct questions to clarify origin and scope, and converts technical detail into operational consequence.
- • Establish the origin and trajectory of the contagion.
- • Determine immediate options to protect crew and ship systems.
- • Information must be converted into orders swiftly to prevent further loss.
- • Technical problems translate into command-level moral responsibilities.
Clinical and methodical; his detachment frames the crisis as a problem to be solved rather than an emotional catastrophe.
Data provides clinical analysis: the program learned and began reprogramming the computer rapidly, identifies the Yamato log as the vector, and supplies the key technical fact that localization to one mainframe sector buys time.
- • Trace the program's source and current footprint within ship systems.
- • Communicate actionable technical facts that enable command decisions.
- • Objective, granular analysis yields usable tactical options.
- • Rapid learning algorithms can outpace human control if unchecked.
Tense and worried; his professionalism overlays a growing impatience to act and protect the crew.
Riker listens, links erratic instrument behavior and casualty reports to the revealed program, and voices the operational consequences as anxiety about mounting injuries and limited time.
- • Clarify how the program produced ship malfunctions and casualties.
- • Press for actionable steps to arrest the spread and protect personnel.
- • Failures in instrumentation are symptomatic of deeper systemic corruption.
- • Human lives and crew safety must constrain technical risk-taking.
Worried and resigned but committed; he accepts the chance of failure while promising to attempt containment and remediation.
Geordi explains the technical diagnosis: the probe transmitted an alien program, acknowledges the program's sophistication, concedes his limits in fully understanding or reversing it, and vows to try to stop it.
- • Identify how the program is interacting with Enterprise systems.
- • Contain and neutralize the Iconian program before it spreads.
- • The Iconian code is beyond current human analytical frameworks.
- • Even limited containment can create crucial breathing space for action.
Objects Involved
Significant items in this scene
Varley's Iconian Probe is invoked as the physical transmitter that sent the alien program. In this event it functions narratively as the provenance for the contagion: the crew trace the program's origin to the probe and use that linkage to explain the Yamato's fate and the nature of the threat aboard the Enterprise.
The USS Enterprise turbolifts are referenced as compromised infrastructure. Pulaski refuses to trust them for casualty transport; they symbolize the ship's automated systems now vulnerable to the alien code and therefore cannot be relied upon for safe movement.
Geordi's Engineering PADD (Yamato Log) is the concrete medium through which the Iconian program arrived: the Yamato log downloaded to the Enterprise contained the embedded program. The PADD/log is the forensic link connecting Yamato's destruction to the Enterprise's contamination.
Location Details
Places and their significance in this event
Enterprise Access Tunnels are identified as the alternate, practical artery for medical teams to reach casualties because automated transit is unreliable. They operate as a slower, risk-managed routing option during system instability.
The Observation Lounge serves as the crisis convening space where command, engineering, and operations converge to translate forensic data into policy and action. It functions as both analytic theater and moral forum—where technical facts become orders affecting human lives.
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
Themes This Exemplifies
Thematic resonance and meaning
Key Dialogue
"GEORDI: That probe was a transmitter sending an alien computer program. The same program that is currently aboard the Enterprise and trying to rewrite our software in its own image. We have two completely incompatible computer systems trying to interact."
"DATA: Consider, Captain, this program has entered an alien data base -- ours -- and in less than seven hours it has managed to not only learn our system, but has also begun to reprogram our computer."
"GEORDI: Sir, the Enterprise computer system is a lot like our bodies with a voluntary and involuntary system. Probably ninety percent of what happens on this ship is done automatically, completely beyond our control. We're sitting on a bomb that could go any second -- or never."