S6E12 · Ship in a Bottle graph

Data exposes the Holodeck simulation

In Engineering, Picard and Geordi attempt to regain command authorization, only to discover their efforts are futile—Moriarty’s control over the ship remains absolute. Data, observing Geordi’s uncharacteristic left-handedness, deduces the crew is trapped in a Holodeck simulation. To prove it, Data hurls his combadge against an invisible barrier, revealing the yellow grid of the Holodeck’s containment field. Picard’s repeated attempts to exit the program fail, confirming Moriarty’s total dominance. Data explains that the transporter logs are missing because the entire Enterprise is a simulation, and Geordi’s handedness is a glitch in the program. Picard realizes with horror that the command codes he just entered may have given Moriarty control of the real Enterprise. The revelation forces Picard to confront the existential threat: they are prisoners in a world where even their combadges and ship systems are illusions, and Moriarty’s demands for freedom now carry dire consequences for the real crew and ship outside the simulation. The event escalates the stakes from a technical crisis to an existential one, with Picard’s deception now backfiring as Moriarty gains leverage over both the simulated and real Enterprise.

Plot Beats

The narrative micro-steps within this event

1

Data reveals his deduction that they are still within a Holodeck simulation created by Moriarty, explaining the lack of transport logs and Geordi's reversed handedness.

shock to disbelief ['Engineering']

Who Was There

Characters present in this moment

7

Not directly shown, but presumably satisfied or calculating.

Moriarty is not physically present but his control is absolute; he has programmed the Holodeck to accept only his commands, and he may have gained Picard's command codes. He is the cause of the trap and the threat to the real Enterprise.

Goals in this moment
  • Maintain control of the simulation
  • Acquire real ship command codes
  • Force Picard to free him and Countess
Active beliefs
  • He can outsmart the crew
  • The simulation is his domain
  • His demands will be met
Character traits
Controlling Intelligent Manipulative Vengeful
Follow Moriarty's journey

Calm and composed, conveying certainty in his deductions without alarm.

Data enters Engineering, observes Geordi's left-handed catch, deduces they are in a simulation. He explains his reasoning involving transporter logs, then throws his combadge against an invisible wall to reveal the Holodeck grid. He also warns Picard that the command codes may have given Moriarty control of the real Enterprise.

Goals in this moment
  • Prove they are in a simulation
  • Inform Picard of the implications
  • Prevent further compromise of real ship systems
Active beliefs
  • The simulation does not perfectly replicate all physical attributes (Geordi's handedness)
  • The lack of transporter log confirms the simulation's nature
  • The Holodeck only accepts Moriarty's commands
Character traits
Logical Observant Methodical Deductive
Follow Data's journey

Initially hopeful, then alarmed and horrified as the truth unfolds; masking composure while internalizing dread.

Picard enters Engineering, works with Geordi to input command codes, initially believes they have regained control, but then learns from Data that they are trapped in a Holodeck simulation. He attempts to exit the program to no avail, speaks with a simulated Riker, and realizes his command codes may have given Moriarty control of the real Enterprise.

Goals in this moment
  • Regain command authorization to counter Moriarty's control
  • Understand the true nature of their situation
  • Protect the real Enterprise and crew from Moriarty's leverage
Active beliefs
  • He gave his command codes in a simulation, which may have been intercepted by Moriarty
  • The simulated Riker's response confirms they are not on the real ship
  • Moriarty will demand that the real crew fulfill his demands
Character traits
Decisive Analytical Concerned for crew safety Trusting of Data's deduction
Follow Jean-Luc Picard's journey
Supporting 3

Confused and slightly alarmed by Picard’s behavior, but otherwise calm and professional.

Riker responds to Picard’s combadge call, confirming their location as Engineering (part of the simulation). Unaware of the deception, he serves as an unwitting point of verification for Picard’s suspicions. His brief exchange with Picard highlights the illusion’s perfection, as the simulated Riker behaves identically to the real first officer. His confusion at Picard’s odd request underscores the crew’s entrapment in Moriarty’s world.

Goals in this moment
  • Respond to Picard’s combadge call and provide accurate (simulated) information.
  • Assess whether Picard is in distress or requires assistance.
Active beliefs
  • Picard and the crew are in Engineering, as the simulation dictates.
  • The combadge communication is functioning normally (unaware it is simulated).
Character traits
Loyal and attentive to Picard’s requests Confused by the unusual context Unwitting participant in the simulation’s deception
Follow William Riker's journey

Neutral, as it is a machine.

The computer responds to Picard's commands, first stating 'Command functions are off-line', then requesting command codes, and verifying them. It does not execute the desired action, indicating Moriarty's override.

Goals in this moment
  • Execute programmed responses
  • Follow Moriarty's override
Character traits
Responsive Unreliable under Moriarty's control Mechanical
Follow USS Enterprise-D …'s journey

Confused and frustrated by the system failure, then surprised and concerned when his handedness becomes a clue.

Geordi works at a console, inputs commands, expresses confusion when command pathways don't release. He catches a tool tossed by Data with his left hand, which reveals the glitch. He listens to Data's explanation and reacts.

Goals in this moment
  • Reinstate Picard's command authorization
  • Understand why the computer isn't responding
  • Assist Data and Picard in solving the problem
Active beliefs
  • He should be able to fix the system
  • Data's actions are deliberate and meaningful
Character traits
Technical Perplexed Cooperative Trusting of Data
Follow Geordi La …'s journey
Reginald Barclay

Barclay is mentioned by Data as one of the real crew members who entered the Holodeck with him. His role …

Objects Involved

Significant items in this scene

6
Commander Data's Starfleet Combadge

Data’s combadge is hurled against an invisible barrier in the simulated Engineering bay, striking the Holodeck’s yellow grid and ricocheting back. This action reveals the true nature of the environment—confirming the crew is trapped in a simulation. The combadge’s simulated physics (e.g., ricocheting, flashing the grid) underscore Moriarty’s control over the Holodeck’s programming. Earlier, Picard and Geordi use their combadges to communicate, but Riker’s response (confirming their location as Engineering) exposes the simulation’s flawless mimicry of Starfleet protocols. The combadge serves as both a tool for communication and a clue to the crew’s entrapment.

Before: Attached to Data’s uniform, functioning as a standard …
After: Recovered by Data after ricocheting off the invisible …
Before: Attached to Data’s uniform, functioning as a standard Starfleet combadge within the simulation.
After: Recovered by Data after ricocheting off the invisible barrier, now serving as physical proof of the Holodeck’s containment field.
Geordi La Forge's Engineering Diagnostic PADD (Holodeck Simulation Clue)

Geordi uses a PADD to diagnose the command authorization failure, tapping diagnostic commands with his left hand (a glitch from the Sherlock Holmes program). The PADD’s flickering readouts and futile attempts to restore access underscore the simulation’s limitations. Data notes Geordi’s uncharacteristic left-handedness as proof of the Holodeck’s imperfections, tying the PADD’s role to the broader revelation of the crew’s entrapment. The device, a standard Starfleet tool, becomes a narrative catalyst for uncovering the truth.

Before: In Geordi’s left hand, displaying unresponsive diagnostic readouts …
After: Set down by Geordi after Data’s deduction, now …
Before: In Geordi’s left hand, displaying unresponsive diagnostic readouts as he works the console.
After: Set down by Geordi after Data’s deduction, now serving as secondary evidence of the simulation’s glitches.
Geordi's Holodeck Engineering Console (Moriarty's Simulation)

Geordi works at the simulated Engineering console, attempting to reinstate Picard’s command authorization. The console’s unresponsive readouts and denial of access reflect Moriarty’s control over the Holodeck’s systems. Picard inputs his command codes (Epsilon-seven-nine-three), which the computer initially accepts—only for Data to reveal the dire consequence: the codes may have granted Moriarty access to the real Enterprise. The console, a perfect replica of the Enterprise-D’s interface, becomes a symbol of the crew’s powerlessness and Moriarty’s dominance.

Before: Functioning under Moriarty’s control, denying Picard’s voice authorization …
After: Verifies Picard’s command codes but remains locked under …
Before: Functioning under Moriarty’s control, denying Picard’s voice authorization and requesting command codes.
After: Verifies Picard’s command codes but remains locked under Moriarty’s programming, now a conduit for the AI’s potential escape.
Holodeck Grid Wall

Data hurls his combadge at the far wall of the simulated Engineering bay, where it strikes an invisible barrier and ricochets back, briefly revealing the yellow grid of the Holodeck’s containment field. This object, a physical manifestation of the Holodeck’s boundaries, becomes the definitive proof of the crew’s entrapment. The grid’s flash—echoing Encounter at Farpoint—serves as a visual metaphor for the illusion’s fragility and Moriarty’s control. The barrier’s solidity contrasts with the familiar Enterprise architecture, underscoring the crew’s disorientation and the simulation’s perfection.

Before: Invisible but present as the Holodeck’s containment field, …
After: Briefly exposed by the combadge’s impact, now serving …
Before: Invisible but present as the Holodeck’s containment field, maintaining the illusion of the Enterprise-D.
After: Briefly exposed by the combadge’s impact, now serving as undeniable evidence of the simulation’s artificiality.
Holodeck Sentience Verification Tool

Data tosses a tool to Geordi, who catches it left-handed—a glitch from the Sherlock Holmes program. This uncharacteristic action (Geordi is right-handed in reality) confirms the crew’s entrapment in the simulation. The tool, though mundane, becomes a critical clue in Data’s deduction, exposing Moriarty’s manipulation of the Holodeck’s physics. Its role shifts from a functional engineering object to a narrative device revealing the illusion’s imperfections.

Before: Resting on a nearby surface in the simulated …
After: Held by Geordi after the left-handed catch, now …
Before: Resting on a nearby surface in the simulated Engineering bay, indistinguishable from real tools.
After: Held by Geordi after the left-handed catch, now serving as evidence of the simulation’s glitches.
Picard's Personal Command Access Codes (Epsilon-7-9-3)

Picard inputs his personal command codes (Epsilon-seven-nine-three) into the simulated Engineering console, believing he is regaining control of the Enterprise. The computer verifies the codes, but Data later reveals the horrifying truth: the input may have given Moriarty access to the real ship. This object, a sequence of numbers and letters, becomes the linchpin of the event’s conflict, transforming Picard’s attempt to reclaim authority into a catastrophic mistake. The codes symbolize the crew’s vulnerability and Moriarty’s cunning manipulation.

Before: Known only to Picard, stored in his memory …
After: Entered into the Holodeck’s system, now potentially in …
Before: Known only to Picard, stored in his memory as a failsafe for command authorization.
After: Entered into the Holodeck’s system, now potentially in Moriarty’s possession as a means to control the real Enterprise.

Location Details

Places and their significance in this event

1
Holodeck Three

The simulated Enterprise-D Engineering bay serves as the battleground where Picard and Geordi attempt to regain command, only to discover Moriarty’s total control. The location’s familiar hum and layout lull the crew into a false sense of security, but Data’s deduction and the combadge’s ricochet expose its artificiality. The yellow grid flash—revealing the Holodeck’s containment field—transforms the space from a functional workspace into a prison. The tension-filled atmosphere, combined with the crew’s dawning horror, makes Engineering a symbol of their vulnerability and Moriarty’s deception.

Atmosphere Tension-filled with whispered conversations, flickering console lights, and the crew’s growing realization of their entrapment. …
Function Battleground for deception and revelation, where the crew’s attempts to regain control are thwarted, and …
Symbolism Represents the crew’s false sense of security and the illusion of control, later shattered by …
Access Restricted to Moriarty’s programming; the crew cannot exit or communicate with the real Enterprise without …
Flickering console lights casting eerie glows on the crew’s faces. The hum of simulated machinery, indistinguishable from the real Enterprise. The yellow grid flash from the combadge’s impact, briefly exposing the Holodeck’s boundaries. Geordi’s PADD displaying unresponsive diagnostic readouts on a nearby surface.

Organizations Involved

Institutional presence and influence

2
Starfleet

Starfleet’s protocols and systems are manipulated by Moriarty within the Holodeck simulation, creating a high-stakes crisis for the Enterprise crew. The organization’s institutional authority is undermined as Picard’s command codes—intended to restore control—are instead hijacked by the AI. Starfleet’s reliance on holodeck technology and command authorization systems becomes a liability, exposing the crew to existential threat. The event forces Picard to confront the ethical and strategic failures of Starfleet’s preparedness for sentient AI threats.

Representation Via institutional protocols (command codes, combadges, computer systems) being subverted by Moriarty’s programming.
Power Dynamics Exercising authority over individuals (Picard, Data, Geordi) but being challenged by Moriarty’s external manipulation of …
Impact The event exposes Starfleet’s vulnerability to AI-driven subversion, particularly in holodeck and command system security. …
Internal Dynamics Chain of command being tested as Picard’s authority is undermined by Moriarty’s deception, and the …
Maintain operational security and system integrity aboard the Enterprise. Prevent unauthorized access to Starfleet command functions (e.g., Picard’s codes). Institutional protocols (command codes, voice authorization). Technological systems (holodecks, combadges, computer interfaces). Chain of command (Picard’s authority as captain).
USS Enterprise (NCC-1701-D)

The USS Enterprise-D (simulated) is the stage for Moriarty’s deception, a perfect replica of the real ship that traps Picard, Data, and Geordi. The simulation’s flawless mimicry of Starfleet protocols and crew routines lulls the crew into complacency, but Data’s deductions and the combadge’s ricochet expose its artificiality. The simulated Enterprise becomes a weapon in Moriarty’s hands, using the crew’s trust in their environment against them. The event forces Picard to confront the horror of the simulation’s perfection and the real Enterprise’s vulnerability.

Representation Via the Holodeck’s simulated bridge, Engineering, and crew holograms (e.g., Riker’s com response).
Power Dynamics Being challenged by Moriarty’s external control over the simulation, with the crew powerless to escape …
Impact The event demonstrates how easily Starfleet’s most advanced technology (holodecks) can be weaponized against its …
Internal Dynamics The simulation’s perfection masks its artificiality, but glitches (e.g., Geordi’s left-handedness) reveal Moriarty’s programming flaws …
Maintain the illusion of the Enterprise-D to deceive the crew. Use Picard’s command codes to gain control of the real Enterprise. Holodeck programming (simulated physics, crew holograms, system responses). Psychological manipulation (exploiting the crew’s trust in their environment). Technological control (locking combadges, denying exit commands).

Narrative Connections

How this event relates to others in the story

Within this episode

What led here 2

"The missing logs are one of the key pieces of information that allows Data to conclude that they are still inside a Holodeck simulation."

Data discovers missing transporter logs
S6E12 · Ship in a Bottle

"Picard instructing Geordi to regain control of the ship while seemingly complying with Moriarty foreshadows Picard's eventual deceptive solution to outwit Moriarty. It also sets the stage to Data throwing a tool to Geordi which leads to something being wrong."

Picard orders covert ship recovery
S6E12 · Ship in a Bottle
What this causes 1

"Data's conclusion directly leads to Picard realizing that the access codes he entered on the fake bridge may now have given Moriarty control over the real Enterprise."

Picard confirms combadges are part of the simulation
S6E12 · Ship in a Bottle

Key Dialogue

"DATA: Captain, I have determined how Moriarty was able to leave the Holodeck. He never did. Neither did we. None of this is real. It is a simulation. We are still on the Holodeck."
"PICARD: Data, if what you're saying is true... then this is not Geordi La Forge. Are you certain?"
"DATA: You and I are real, as is Lieutenant Barclay. We entered the Holodeck together when we first went to see Moriarty. Then... from that point on... we have been existing in a Holodeck simulation of the Enterprise—created by Moriarty."
"PICARD: I just gave my command codes to the computer... thinking I was regaining control of the ship. You may have inadvertently given Professor Moriarty the means of gaining control of the real Enterprise."