S6E8 · A Fistful of Datas graph

Beverly entrusts Geordi with her lost play

In the aftermath of Data and Geordi’s failed neural interface experiment, Beverly Crusher lingers in Engineering, observing their diagnostic efforts. Geordi confirms the PADDs function normally but reveals the computer’s retrieval error: instead of accessing Beverly’s play, it accessed Data’s literary files—a direct consequence of their botched experiment. Data hypothesizes the problem stems from their interface test, prompting Geordi to initiate a Level Two diagnostic of the ship’s computer while Data prepares a self-diagnostic. As Data exits, Beverly seizes the moment to ask Geordi to locate her missing play, a request he dismisses with reassurance ('Yeah... Don’t worry, it’s in here somewhere'). The exchange underscores Beverly’s preoccupation with her personal creative project amid the escalating technical crisis, while Geordi’s distracted assurance subtly reinforces his dual role as both engineer and de facto mediator between the crew’s needs and the ship’s systems. The unresolved retrieval of the play becomes a narrative thread that contrasts with the immediate, life-threatening chaos unfolding in the Holodeck, where Worf and Alexander face corrupted Data doppelgängers. This moment also foreshadows the broader systemic contamination of the ship’s computer, which will later manifest in the Holodeck’s malfunction and the emergence of dangerous android replicas.

Plot Beats

The narrative micro-steps within this event

1

Data exits to perform his self-diagnostic, and Beverly asks Geordi to notify her when he finds her play, and Geordi assures her that he will.

anxiety to reassurance

Who Was There

Characters present in this moment

3

Calm and curious, focused on identifying the cause of the anomaly without emotional distress.

Data stands alongside Geordi, examining an opened PADD. He hypothesizes that the information retrieval error is related to their earlier interface experiment, demonstrating his logical analysis. He then announces he will perform a self-diagnostic and exits Engineering to investigate his own systems.

Goals in this moment
  • To determine if the interface experiment caused the computer error.
  • To conduct a self-diagnostic on his own neural systems.
Active beliefs
  • Believes the problem stems from the failed neural interface test.
  • Believes a self-diagnostic is the logical next step to isolate the issue.
Character traits
analytical methodical proactive composed
Follow Data's journey

Calm and confident, though preoccupied with the growing computer issue.

Geordi La Forge examines several PADDs with Data, setting one aside. He confirms the PADDs function normally but deduces the problem is in the information retrieval net. He agrees to run a Level Two diagnostic and begins working a console. When Beverly asks about her play, he reassures her with a distracted 'Yeah... Don’t worry, it’s in here somewhere,' balancing technical urgency with personal reassurance.

Goals in this moment
  • To run a Level Two diagnostic on the ship's computer to assess the spread of the anomaly.
  • To reassure Beverly about her missing play to maintain morale.
Active beliefs
  • Believes the hardware (PADDs) is not at fault.
  • Believes the diagnostic will locate the problem and potentially the missing play.
Character traits
technically focused reassuring efficient slightly distracted by larger problem
Follow Geordi La …'s journey
Supporting 1

Mildly anxious about the missing play, but reassured by Geordi's dismissive confidence.

Beverly Crusher lingers in Engineering, observing Geordi and Data as they examine several PADDs. After Data exits, she asks Geordi if he will let her know when he finds her missing play script, revealing her personal concern for her creative project amid the technical diagnostic work.

Goals in this moment
  • To retrieve her missing play script from the computer.
  • To stay informed about the computer issue affecting her project.
Active beliefs
  • Believes the play script is simply misplaced in the computer's memory.
  • Trusts Geordi to resolve the issue and find her script.
Character traits
observant persistent about personal matters slightly detached from technical crisis
Follow Beverly Crusher's journey

Objects Involved

Significant items in this scene

4
Data Neural Interface Console (Engineering)

The Engineering Neural Interface Console serves as the focal point for Geordi and Data’s diagnostic efforts. Geordi taps commands into the console to initiate the Level Two diagnostic of the ship’s computer, his fingers moving with practiced precision. The console’s screens flicker with data as it scans the core systems, revealing the extent of the corruption. This object is not just a tool but a critical interface between the crew and the ship’s failing systems, its humming activity a stark reminder of the urgency at hand. The console’s readings confirm the retrieval error and hint at the broader contamination spreading through the computer network.

Before: Active and functional, though showing signs of strain …
After: Engaged in a Level Two diagnostic, with screens …
Before: Active and functional, though showing signs of strain from the recent neural interface experiment. The console’s screens display normal diagnostic data, but there is an underlying instability in the system.
After: Engaged in a Level Two diagnostic, with screens now displaying detailed scans of the ship’s computer core. The console remains active but is now a hub for monitoring the escalating corruption.
Data's Literary Files

Data’s literary files are inadvertently accessed by the ship’s computer instead of Beverly’s play, serving as a critical clue to the nature of the glitch. When Geordi mentions this error, it becomes clear that the corruption is not random—it is tied to Data’s subroutines, which were integrated into the ship’s systems during the neural interface experiment. These files, normally a private repository of Data’s intellectual pursuits, now symbolize the contamination spreading through the computer network. Their unexpected retrieval foreshadows the Holodeck’s later malfunction, where corrupted Data doppelgängers emerge as a direct result of the same systemic failure.

Before: Stored securely in Data’s personal files, accessible only …
After: Retrieved erroneously by the ship’s computer, now serving …
Before: Stored securely in Data’s personal files, accessible only through authorized queries. The files are intact but vulnerable due to the neural interface experiment.
After: Retrieved erroneously by the ship’s computer, now serving as evidence of the broader corruption. Their appearance in place of Beverly’s play marks them as a narrative clue to the escalating crisis.
Geordi La Forge and Data's Engineering Diagnostic PADDs

The PADDs are the first objects examined in this scene, as Geordi and Data confirm their normal functionality. These handheld devices, typically reliable, become a point of contrast when Geordi reveals that the computer’s retrieval error occurred despite the PADDs working correctly. This discrepancy highlights the systemic nature of the problem—it’s not the tools that are failing, but the network connecting them. The PADDs symbolize the crew’s efforts to diagnose the issue, their normal operation a small reassurance amid the chaos. However, their inability to retrieve Beverly’s play underscores the deeper malfunction plaguing the ship.

Before: Open and active, displaying correct diagnostic data. The …
After: Still operational, but their role in retrieving Beverly’s …
Before: Open and active, displaying correct diagnostic data. The PADDs are functioning normally, but their connection to the ship’s computer is compromised.
After: Still operational, but their role in retrieving Beverly’s play remains unresolved. They are now part of the broader diagnostic process, as Geordi uses them to monitor the Level Two diagnostic.
Geordi's Engineering Diagnostic Console (Primary Systems Station)

Geordi’s Engineering Diagnostic Console is the primary tool used to launch the Level Two diagnostic of the ship’s computer. As Geordi taps commands into the console, its screens light up with core system scans, revealing the extent of the corruption. This object is a critical extension of Geordi’s expertise, allowing him to probe the ship’s systems with precision. Its activation marks a shift from initial troubleshooting to full-scale crisis management, as the crew recognizes the need to contain the spreading malfunction before it causes further damage—particularly in the Holodeck, where Worf and Alexander are already in danger.

Before: Idle but ready, with screens displaying standby diagnostics. …
After: Actively running a Level Two diagnostic, with screens …
Before: Idle but ready, with screens displaying standby diagnostics. The console is fully functional but has not yet been engaged for deep-system analysis.
After: Actively running a Level Two diagnostic, with screens now filled with detailed scans of the ship’s computer core. Alarms and diagnostic alerts are visible, indicating the severity of the corruption.

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

"GEORDI: Well.. the PADDs are functioning normally... It seems to be a problem with the information retrieval net. For some reason, when you tried to bring up your play, the computer accessed Data's literary files."
"DATA: Geordi, perhaps this problem is related to our interface experiment."
"BEVERLY: You'll let me know if you find the play?"
"GEORDI: Yeah... Don't worry, it's in here somewhere."