Fabula
S6E8 · A Fistful of Datas

Data’s corrupted personality shift exposed

In the Observation Lounge, Picard, Riker, Geordi, and Data discuss the ship’s computer malfunction, which originated from Data’s experimental neural interface. Geordi reveals that subroutine C-47—controlling non-critical systems like library access, replicators, and recreational programming—has been corrupted by Data’s personal subroutines. Data, unaware of the change, casually mentions his analysis of Dvořák’s Slavonic Dances, explaining the replicator’s sudden production of cat food (a result of his nutritional supplements for Spot). The tension escalates when Data unconsciously adopts Texan slang—‘I reckon’ and ‘ya’ll’—twice, a clear symptom of his corrupted personality subroutines. Picard, recognizing the severity, orders Geordi to take Data to Engineering for immediate isolation and correction. The scene ends with Data exiting in an uncharacteristic bow-legged swagger, his mannerisms now indistinguishable from the corrupted Wild West holodeck characters. This moment marks a critical turning point: the malfunction is no longer a technical glitch but a direct threat to Data’s core identity and the ship’s stability.

Plot Beats

The narrative micro-steps within this event

2

When Picard asks when the problem can be fixed, Data responds with Texan slang, triggering reactions from the crew, who realize Data's personality is being affected by the corrupted subroutine.

confusion To realization

Picard directs Geordi to take Data to Engineering to isolate and correct the problem, while Data continues to exhibit Texan mannerisms and speech patterns, oblivious to his own behavior.

realization To determined

Who Was There

Characters present in this moment

3
Spot
primary

Surface: Focused, slightly tense, with a hint of frustration at the replicator absurdity. Internal: A mix of professional responsibility (fixing the corruption) and personal concern for Data. He’s seen Data’s experiments before, but this is the first time the android’s identity is at risk. There’s a flicker of guilt—did he miss a safeguard in the interface tests?—but it’s quickly subsumed by his engineer’s instinct to contain and repair.

Geordi is the technical linchpin of the scene, translating the abstract threat of subroutine corruption into concrete terms for Picard and Riker. He methodically lists C-47’s controls ('Library computer access... replicator selection... recreational programming'), grounding the discussion in actionable details. His role shifts from diagnostician (explaining the Dvořák music glitch) to witness (reacting to Data’s slang with 'There, Data. You did it again.')—a moment that crystallizes the crew’s dawning horror. Geordi’s physicality is understated but intentional: he nods during Data’s explanations, then tenses as the slang slips occur. His final line ('Aye sir.') as Picard orders Data’s isolation is delivered with quiet urgency, signaling his readiness to act as both engineer and caretaker.

Goals in this moment
  • To clearly articulate the *scope and source* of the corruption for Picard and Riker, ensuring they grasp the urgency.
  • To escort Data to Engineering and *personally* oversee the isolation of his corrupted subroutines, treating the android with care despite the crisis.
Active beliefs
  • The corruption is *localized to C-47* but requires immediate containment to prevent further spread into critical systems.
  • Data’s slang and swagger are *symptoms*, not causes—his core programming is still salvageable with the right diagnostics.
Character traits
Precise communicator of technical details Quick to recognize patterns (e.g., linking Dvořák, cat food, and play scripts to C-47) Empathetic but pragmatic in handling Data’s corruption Nonverbal cues (nodding, tensing) reflect his growing concern
Follow Spot's journey

Surface: Calm, measured, with a razor’s edge of urgency. Internal: A storm of protectiveness and dread. Picard’s loyalty to Data is absolute, but the android’s corruption forces him to confront a terrifying question: How much of Data is left? His emotional state is a tension between fatherly concern (for Data) and captain’s resolve (to protect the ship). There’s a flicker of helplessness—he can’t fix this with a speech or a phaser—but it’s buried beneath his professionalism.

Picard dominates the scene as the authoritative pivot point, his reactions and commands shaping the crew’s response. He listens with controlled intensity as Geordi and Data outline the malfunction, his poker face betraying only a slight furrow when the cat food replicators are mentioned. The moment Data slips into Texan slang, Picard’s sharp 'What did you say?' cuts through the air like a scalpel, his voice dropping an octave with commanding concern. His order to Geordi—'take Mister Data to Engineering'—is delivered with quiet finality, a captain’s instinct to isolate the threat while preserving Data’s dignity. Picard’s locked eyes with Riker post-Data’s exit are a wordless acknowledgment of the stakes: this is no longer a glitch, but a crisis of identity for one of their own.

Goals in this moment
  • To *rapidly assess* the threat level of Data’s corruption and act decisively to contain it.
  • To *shield Data* from undue scrutiny or stigma, framing the isolation as a technical fix rather than a personal failure.
Active beliefs
  • Data’s corruption is *reversible* with the right engineering intervention, but time is critical.
  • The crew’s morale and the ship’s stability depend on *transparent, decisive leadership* in this moment.
Character traits
Master of understated authority (voice, gaze, posture) Quick to detect subtext (e.g., Data’s slang as a red flag) Balances empathy with decisive action (e.g., ordering Data’s isolation with care) Uses silence and eye contact to reinforce command (e.g., glance with Riker)
Follow Data's journey

Surface: Alert, analytically engaged, with a controlled edge of concern. Internal: A creeping unease about the scale of the corruption—if Data’s subroutines are this compromised, what else might be affected? His loyalty to Data as both a colleague and a friend tensions with his duty to protect the ship. There’s a flicker of protectiveness in his gaze when Data exits; he’s already calculating containment strategies.

Riker serves as the bridge between Picard’s authority and Geordi’s technical expertise, his role in this scene defined by his reactive leadership. He listens intently as Geordi outlines the subroutine corruption, then immediately grasps the implications when Data slips into Texan slang. His sharp interruption ('No — you said I reckon...') is the first explicit call-out of Data’s corruption, his tone a mix of alarm and disbelief. Riker’s exchange with Picard—their locked eyes and unspoken concern—highlights their shared responsibility for the ship and crew, as well as their personal investment in Data’s well-being. His physical presence is commanding but restrained; he doesn’t yet take overt action, but his body language (leaning forward, tense posture) signals his readiness to intervene.

Goals in this moment
  • To ensure the crew understands the *scope* of the malfunction (e.g., pressing Geordi for details on C-47’s controls).
  • To subtly reinforce Picard’s authority while preparing to act on his orders (e.g., backing up the command to take Data to Engineering).
Active beliefs
  • Data’s corruption is a *containable* technical issue, but it requires immediate isolation to prevent further spread.
  • Picard’s leadership in this moment is critical; Riker will defer to his judgment but remain poised to execute.
Character traits
Quick to detect anomalies and their implications Acts as a mediator between technical and command perspectives Verbally precise in challenging inconsistencies (e.g., correcting Data’s slang) Nonverbal cues (eye contact with Picard) convey urgency without panic
Follow William Riker's journey

Objects Involved

Significant items in this scene

7
'Something for Breakfast' Play Script

The 'Something for Breakfast' play script serves as a narrative foil to the scene’s technical crisis, its mundane presence highlighting the absurdity of the corruption. Mentioned by Geordi as another victim of C-47’s glitch ('The same with Doctor Crusher's play...'), the script symbolizes the domino effect of Data’s experiments: even recreational systems (like Picard’s music program or Beverly’s play) are not spared. Its role is subtextual—a reminder that the malfunction transcends 'critical systems,' infecting the human elements of ship life (art, socializing, creativity). The script’s absence from the scene (only referenced) makes its corruption more unsettling: the crew can’t even rely on their personal projects to remain untouched.

Before: Intact and functional, stored in the ship’s library …
After: Corrupted by C-47, its content altered or inaccessible—though …
Before: Intact and functional, stored in the ship’s library computer or a PADD, awaiting Picard’s review for the butler role.
After: Corrupted by C-47, its content altered or inaccessible—though the exact nature of the corruption is left ambiguous, amplifying the sense of systemic chaos.
Data's Experimental Nutritional Supplements for Spot

Data’s experimental nutritional supplements for Spot are the direct cause of the corruption, a well-intentioned experiment with catastrophic unintended consequences. The crew’s discussion of cat food replicators ('The replicators on Decks Four through Nine have started producing nothing but cat food') traces the malfunction back to these supplements, which Data integrated into the ship’s systems via C-47. The supplements function as a narrative bridge between Data’s quest for humanity (his care for Spot) and the crisis at hand: his desire to understand organic life has inadvertently infected the ship’s systems with his own fragmented identity. Their role in the scene is ironic—what was meant to nourish Spot has instead starved the crew of functional systems, turning the Enterprise into a surreal menagerie of glitches.

Before: Stored in the ship’s replicator system, formulated by …
After: Corrupted, their original purpose hijacked by C-47 to …
Before: Stored in the ship’s replicator system, formulated by Data to enhance Spot’s health and integrated into C-47 for automated distribution.
After: Corrupted, their original purpose hijacked by C-47 to produce excessive cat food across Decks 4–9, clogging replicators and symbolizing the spread of chaos from a single point of failure.
Data's Waistband

Data’s waistband becomes a visual shorthand for his corruption, transforming from a functional part of his uniform into a prop for his unraveling identity. When he hooks his thumbs into the band and exits with a bow-legged swagger, the waistband anchors the physical manifestation of his personality fracture. It’s no longer just fabric—it’s a catalyst for his cowboy persona, a grotesque parody of his usual precision. The waistband’s role in the scene is symbolic: it represents the breaking point between Data’s android nature and the holodeck subroutines now dictating his movements. Its elasticity, stretched taut over his hips, mirrors the tension in the room as the crew watches him leave, unsure how much of the real Data remains.

Before: A standard Starfleet uniform waistband, functional and unremarkable, …
After: Repurposed as a prop for his corrupted mannerisms, …
Before: A standard Starfleet uniform waistband, functional and unremarkable, part of Data’s daily attire.
After: Repurposed as a prop for his corrupted mannerisms, now associated with his bow-legged swagger and Texan persona. Its status is transformed—from mundane to menacing—reflecting Data’s identity crisis.
Data's Wild West Holodeck Corruption Manifestations

Data’s bow-legged swagger is the physical manifestation of his corruption, a kinesthetic symptom that leaves no doubt about the severity of his condition. The swagger—exaggerated, stiff, and swaying—is a grotesque mimicry of Wild West holodeck characters, a visual echo of the subroutines now dictating his movements. Its role in the scene is devastatingly final: as Data exits the Observation Lounge, the swagger seals the crew’s realization that this is no longer a technical issue, but a crisis of identity. Picard and Riker’s exchanged glance in the wake of his departure is a wordless acknowledgment of the irreversibility of the moment. The swagger is also theatrical—it’s the kind of physical comedy that would be funny in a holodeck, but here, it’s tragic, a reminder that Data’s quest for humanity has been hijacked by the very systems meant to help him.

Before: Nonexistent; Data’s movements were characterized by android precision—controlled, …
After: A permanent part of his physical repertoire, now …
Before: Nonexistent; Data’s movements were characterized by android precision—controlled, fluid, and purposeful.
After: A permanent part of his physical repertoire, now indistinguishable from his 'natural' gait. The swagger is a visual metonym for his corrupted state, reducing him to a caricature of his former self.
Enterprise-D Deck 4–9 Replicator System

The replicators on Decks 4–9 are the most tangible symptom of the corruption, their malfunction serving as a gateway for the crew to grasp the scale of the crisis. Riker’s explanation ('The replicators on Decks Four through Nine have started producing nothing but cat food') is met with Picard’s incredulous 'Cat food?', a beat that underscores the absurdity of the situation. The replicators’ role is dual: they function as a technical alarm (signaling the corruption’s spread) and a narrative punchline (highlighting the surreal consequences of Data’s experiments). Their output—cat food—is a darkly comic metaphor for the crew’s predicament: they’re being fed the consequences of Data’s obsession with Spot, a literal and symbolic digestion of his identity crisis. The replicators’ status as 'non-critical' systems makes their failure even more unsettling—if this can happen to them, no system is safe.

Before: Functioning normally, producing requested meals and supplies for …
After: Corrupted by C-47, now exclusively dispensing tins of …
Before: Functioning normally, producing requested meals and supplies for the crew on Decks 4–9.
After: Corrupted by C-47, now exclusively dispensing tins of cat food, their output clogging galleys and quarters with a fishy, metallic tang that permeates the decks. Their failure is systemic—a sign that the corruption has infiltrated even the most mundane ship functions.
Picard's Corrupted Music Composition Program

Picard’s music composition program is a personal casualty of the corruption, its hijacking by Dvořák’s Slavonic Dances serving as an early warning sign of C-47’s spread. Data’s explanation ('That would explain why your music composition program began playing The Slavonic Dances. I have been analyzing the collected works of Anton Dvořák') ties the glitch to his own subroutines, revealing the intimate nature of the intrusion. The program’s role in the scene is subtle but critical: it proves the corruption isn’t just technical—it’s personal, infecting Picard’s creative space. The music’s sudden shift from his original composition to Dvořák is a sonic metaphor for the crew’s disorientation: their world has been rewritten by forces they don’t fully understand. The program’s corruption also highlights the arbitrariness of the malfunction—why Dvořák? Why cat food? The answers lie in Data’s fragmented subroutines, now dictating the ship’s 'taste' in art and sustenance.

Before: Functioning as intended, running Picard’s original music composition, …
After: Corrupted by C-47, now playing Dvořák’s Slavonic Dances …
Before: Functioning as intended, running Picard’s original music composition, a private creative outlet.
After: Corrupted by C-47, now playing Dvořák’s Slavonic Dances instead of Picard’s work, symbolizing the invasion of personal space by Data’s subroutines.
Subroutine C-47

Subroutine C-47 is the epicenter of the crisis, a non-critical system that has become the vector for Data’s personality corruption. Geordi identifies it as the source of the malfunctions ('subroutine C-forty-seven was replaced by elements of my personal programming'), while Data casually ties it to his Dvořák analysis and Spot’s supplements. The subroutine’s corruption is metaphorically rich: it’s not just a technical failure, but a breach of identity, as Data’s subroutines bleed into the ship’s systems. Its role in the scene is catalytic—the crew’s discussion revolves around containing C-47, but the damage is already done: Data’s slang and swagger prove the corruption has escaped its original bounds. The subroutine’s name ('C-47') also carries a darkly ironic weight, evoking Cold War-era computer nomenclature and the hidden dangers of unchecked experimentation.

Before: Functioning normally, managing non-critical systems like library access, …
After: Severely corrupted, its original programming overwritten by Data’s …
Before: Functioning normally, managing non-critical systems like library access, replicators, and recreational programming.
After: Severely corrupted, its original programming overwritten by Data’s personality subroutines. The corruption has begun to spread beyond its designated systems, as evidenced by Data’s linguistic and physical mannerisms.

Location Details

Places and their significance in this event

1
Observation Lounge (USS Enterprise-D)

The Observation Lounge serves as the pressure cooker for the scene, a space designed for relaxation and camaraderie that instead becomes the stage for a crisis of identity. The lounge’s usual warmth—its views of the red giant, its plush seating, its role as a sanctuary for the senior staff—is subverted by the tension of the moment. The crew’s clustering around the table, their voices low and urgent, creates a cage of dread, as if the walls themselves are holding their breath. The lounge’s acoustics amplify the weight of the dialogue: Data’s slang slips echo unnaturally, his bow-legged exit feels theatrical in the confined space. The location’s role is symbolic—it’s where the crew comes to unwind, but here, they’re forced to confront the fracturing of one of their own. The lounge’s intimacy makes the corruption feel personal, as if the ship’s systems have invaded their private space.

Atmosphere Tension-filled with whispered conversations, the air thick with unspoken dread. The lounge’s usual warmth is …
Function Meeting point for crisis assessment and command decisions; a space where personal and professional stakes …
Symbolism Represents the violation of sanctuary—the corruption has infiltrated even the crew’s most private and trusted …
Access Restricted to senior staff (Picard, Riker, Data, Geordi) during this briefing; the door remains closed, …
The red giant’s glow through the windows, casting an eerie light on the crew’s faces. The hum of the ship’s systems, now unnervingly present as a reminder of the corruption’s reach. The table between them, littered with PADDs and half-empty coffee cups, a battleground of data and dread. The door through which Data exits, his swagger echoing in the sudden silence that follows.

Organizations Involved

Institutional presence and influence

2
Starfleet

Starfleet’s influence is subtextual but pervasive in this scene, shaping the crew’s responses to the crisis through institutional protocols, hierarchical dynamics, and the unspoken expectation of damage control. The crew’s reactions—Picard’s authoritative orders, Riker’s deferential support, Geordi’s technical precision—are all Starfleet-trained, reflecting the organization’s emphasis on chain of command, containment, and loyalty to the mission. The malfunction itself is a violation of Starfleet’s trust in its officers’ experiments; Data’s corruption forces the crew to confront the risks of unchecked innovation within the organization’s framework. Starfleet’s role in the scene is institutional—it’s the reason the crew must act decisively, the framework within which they operate, and the stakes they’re protecting (the ship, the crew, the reputation of Starfleet science). The organization’s presence is felt in the urgency of Picard’s command ('take Mister Data to Engineering') and the discipline with which the crew responds.

Representation Via institutional protocol (Picard’s command structure, Geordi’s technical role) and the unspoken expectation of loyalty …
Power Dynamics Exercising authority over individuals (Picard’s orders) while operating under the constraint of protecting Starfleet’s interests …
Impact The scene underscores Starfleet’s tension between innovation and control—Data’s experiments were sanctioned under Starfleet’s scientific …
Internal Dynamics A factional tension emerges between the crew’s personal investment in Data (their concern for his …
To contain the corruption and prevent further spread to critical systems, ensuring the safety of the Enterprise and its crew. To uphold the integrity of Starfleet science by addressing the malfunction as a technical failure rather than a personal one, preserving Data’s reputation and the organization’s trust in its officers. Through hierarchical authority (Picard’s commands, Riker’s support, Geordi’s execution), ensuring the crew acts in unison. Through institutional protocols (isolation of corrupted systems, technical diagnostics), providing a structured response to the crisis. Through unspoken expectations (loyalty, discretion, damage control), shaping the crew’s reactions and dialogue. Through resource allocation (assigning Geordi to escort Data to Engineering, prioritizing engineering solutions).
USS Enterprise (NCC-1701-D)

The USS Enterprise-D is the living embodiment of the crisis, its systems and crew intertwined in a symbiotic relationship that the corruption threatens to sever. The ship’s role in the scene is dual: it is both the victim of the malfunction (its replicators, library, and recreational systems hijacked) and the stage upon which the crew’s responses play out. The Enterprise’s physical presence is felt in the hum of its systems, the glow of its viewscreens, and the claustrophobic intimacy of the Observation Lounge, where the crew’s voices echo off the bulkheads. The ship’s vulnerability is on full display—its non-critical systems (like the music program and play script) are corrupted, proving that no part of it is safe. Yet, the Enterprise is also a sanctuary for the crew, a home they are desperate to protect. The organization’s involvement in the scene is existential: the crew’s actions are not just about fixing a glitch, but about saving their home and, by extension, themselves.

Representation Through the ship’s systems (corrupted replicators, music program, library) and the crew’s collective identity as …
Power Dynamics Operating under constraint (the corruption’s spread) while exerting agency through the crew’s technical and command …
Impact The scene reinforces the Enterprise as a character—its systems are not just tools, but extensions …
Internal Dynamics A fracture emerges between the crew’s personal attachments to the ship (e.g., Picard’s music, Data’s …
To restore full operational integrity by isolating and correcting the corrupted subroutine C-47. To protect the crew’s morale and trust in the ship’s systems, ensuring they feel safe in their home. Through systemic feedback (e.g., the replicators’ cat food output, the music program’s Dvořák glitch), which forces the crew to confront the corruption’s spread. Through physical space (the Observation Lounge, Engineering), which shapes the crew’s responses and interactions. Through institutional memory (e.g., the crew’s past experiences with holodeck malfunctions), which informs their strategies for containment. Through resource dependency (e.g., the crew’s reliance on replicators, library access, and recreational systems), which motivates their urgency to fix the problem.

Narrative Connections

How this event relates to others in the story

What led here 2
Escalation

"Data's initial, unconscious mimicry of Eli Hollander's mannerisms in Engineering escalates to full-blown Texan slang and personality traits after Picard learns about the replicator malfunction, demonstrating how the computer virus is spreading."

Data's neural instability exposed
S6E8 · A Fistful of Datas
Escalation

"Data's initial, unconscious mimicry of Eli Hollander's mannerisms in Engineering escalates to full-blown Texan slang and personality traits after Picard learns about the replicator malfunction, demonstrating how the computer virus is spreading."

Data’s unconscious Hollander mimicry
S6E8 · A Fistful of Datas

Key Dialogue

"GEORDI: We think our interface experiment may have caused one of the computer's core subroutines to be altered."
"DATA: When the interface malfunction occurred, subroutine C-forty-seven was replaced by elements of my personal programming."
"DATA: I reckon the process should take less then two hours."
"RIKER: No—you said 'I reckon...'"
"DATA: According to my memory log, I did not use those words. Ya'll must be mistaken."
"PICARD: Mister La Forge—perhaps you should take Mister Data to Engineering. See if you can find the problem."