Fabula
S4E16 · Galaxy's Child

Picard delegates crisis to La Forge

With the Enterprise shuddering under a catastrophic power drain—now at 93% and nearing auto-shutdown—Picard pivots to Geordi La Forge for a solution. The crisis escalates as Data reveals the newborn lifeform is emitting a high-frequency radio transmission, raising questions about its intent. Riker swiftly implements Emergency Condition Seven, prioritizing life support while La Forge’s status remains unconfirmed. The moment underscores Picard’s reliance on his chief engineer, but the delegation also exposes the crew’s vulnerability: without La Forge’s expertise, the ship—and the newborn—may be lost. The tension hinges on whether La Forge can rise above his personal disillusionment with Leah Brahms to focus on the mission-critical task at hand. The scene functions as a turning point, shifting from reactive crisis management to a high-stakes technical challenge that will determine the crew’s ability to atone for their unintended destruction of the parent lifeform.

Who Was There

Characters present in this moment

6

Unseen but inferred as conflicted—La Forge’s disillusionment with Leah Brahms may cloud his judgment, but the crew’s reliance on him could reignite his professional pride. The unanswered question (‘What is your status?’) underscores his crossroads: engineer or heartbroken idealist?

La Forge is not physically present on the bridge during this event, but his absence looms large. Picard’s direct address—'Mister La Forge, what is your status?'—hangs in the air, unanswered. The implication is heavy: the crew’s survival (and the newborn’s) depends on his ability to overcome his personal crisis (Leah Brahms’ failure to match his holodeck fantasy). His status is unconfirmed, but the subtext is clear: if he falters, the Enterprise and the alien lifeform may both be lost. The scene forces the audience to question: Will La Forge prioritize duty over disillusionment?

Goals in this moment
  • Resolve the power drain to save the *Enterprise* and the newborn
  • Overcome personal disillusionment to fulfill his duty
Active beliefs
  • His engineering skills are the key to solving the crisis
  • Leah Brahms’ real-world imperfections have shaken his faith in people (and himself)
Character traits
Absent but pivotal Potentially distracted (personal vs. professional conflict) Engineering genius under pressure Vulnerable (emotionally exposed)
Follow Geordi La …'s journey

Controlled urgency with underlying concern—Picard’s exterior remains composed, but the stakes (ship survival and the newborn’s life) weigh heavily. His delegation to La Forge carries a silent plea: ‘Prove you’re still the engineer we need.’

Picard stands at the center of the storm, his voice a steady anchor amid the Enterprise’s violent shuddering. He barks orders with measured urgency, first demanding an engineering report from Pavlik, then pivoting to La Forge with a direct but loaded question: 'Mister La Forge, what is your status?' His gaze likely flicks to the flickering bridge lights—a visceral reminder of the ship’s fragility—as he delegates authority to his chief engineer. The subtext is palpable: Picard needs La Forge to rise above his personal disillusionment (Leah Brahms’ betrayal of his holodeck fantasy) and focus on the mission-critical task at hand. His delegation isn’t just tactical; it’s a test of trust and professionalism.

Goals in this moment
  • Stabilize the *Enterprise*’s power drain to prevent auto-shutdown
  • Ensure the crew’s survival while exploring the newborn’s transmissions (communication or distress?)
Active beliefs
  • La Forge’s engineering expertise is critical to resolving the crisis
  • The crew’s moral duty extends to the newborn, despite unintended harm to its parent
Character traits
Commanding under pressure Delegative but discerning Emotionally contained (masking concern) Strategic multitasking Moral accountability
Follow Jean-Luc Picard's journey

Curiosity without urgency—Data processes the transmission’s data, but his lack of emotional bias allows him to present it as information, not a threat or a plea. His state is one of intellectual engagement: ‘What does this transmission mean? How should we respond?’

Data delivers his report with clinical precision: 'Captain, the offspring is emitting a high frequency radio transmission.' His tone is neutral, but the implication is electric. Is this communication? A distress call? A threat? Data’s observation forces the crew to confront the newborn’s agency—it’s not just a drain on their power; it’s a being with potential intent. The flickering bridge lights reflect in his golden eyes, but his focus remains on the data. His role here is scientific truth-teller: he doesn’t speculate, but his facts compel speculation. The crew’s next moves (Riker’s protocols, Picard’s delegation to La Forge) hinge on Data’s observation.

Goals in this moment
  • Provide accurate data on the newborn’s transmissions
  • Enable the crew to make informed decisions
Active beliefs
  • The transmission’s nature (communication/distress) is critical to the crew’s response
  • His observations will shape Picard’s and Riker’s strategies
Character traits
Analytical precision Unemotional but insightful Bridge between science and action Catalyst for ethical dilemmas
Follow Worf's journey

Focused intensity with controlled concern—Riker is in his element here, but the flickering lights and Pavlik’s warnings would remind him of the human cost of failure. His protocols are a shield, but his question about communication betrays a deeper curiosity: Is this creature a victim or a threat?

Riker takes charge with tactical precision, his orders a rapid-fire sequence: 'Take the engines off-line. Supplement with auxiliary power... All decks go to emergency condition seven.' His actions are decisive, prioritizing life support over non-essentials. The bridge lights flicker as he speaks, but his voice remains steady—a counterpoint to the chaos. Riker’s role here is crisis manager: he doesn’t just react; he structures the response, leveraging Starfleet protocols to buy time. His question—'Is it trying to communicate?'—reveals his strategic mind: even in a power crisis, he’s assessing the newborn’s intent, not just its threat.

Goals in this moment
  • Stabilize the *Enterprise*’s power to prevent auto-shutdown
  • Determine if the newborn’s transmissions are communicative (ethical implications)
Active beliefs
  • Emergency Condition Seven will buy critical time
  • The newborn’s signals may hold the key to its survival—and the crew’s
Character traits
Decisive under pressure Protocol-driven but adaptive Strategic multitasker (technical + ethical) Voice of pragmatic leadership
Follow William Riker's journey
Supporting 2
Pavlik
Ensign
secondary

High-stress professionalism—Pavlik is clearly aware of the stakes (auto-shutdown = potential death for the crew and the newborn), but his training keeps his voice steady. The flickering lights in Engineering would amplify his tension, but he focuses on the data, not the fear.

Pavlik’s voice crackles over the comlink, delivering the grim update: 'The power drain just jumped to ninety-three percent, sir... approaching auto-shutdown.' His tone is clipped, stressed, but professional—an ensign reporting critical data under fire. The lights flicker violently around him (implied, as he’s in Engineering), mirroring the ship’s precarious state. His role is purely functional: relaying the power drain’s escalation, which triggers Riker’s Emergency Condition Seven protocol. Pavlik’s presence here underscores the Enterprise’s hierarchy: junior officers as the eyes and ears of the crisis, while senior staff (Picard, Riker) make the life-or-death calls.

Goals in this moment
  • Accurately report the power drain’s status to the bridge
  • Support Engineering’s efforts to stabilize the ship
Active beliefs
  • The bridge crew will act decisively on his reports
  • His role, though junior, is vital to the ship’s survival
Character traits
Duty-bound under pressure Concise and direct communicator Stressed but composed Supportive role (enabler of senior decisions)
Follow Pavlik's journey

Resolute calm—Worf’s Klingon warrior instincts are tempered by Starfleet duty. The power drain is a tangible enemy, and he meets it with the same focus he’d bring to a battle. His emotional state isn’t fear or panic, but determination: ‘This ship will not fall on my watch.’

Worf receives Riker’s order with characteristic stoicism: 'All decks go to emergency condition seven.' His response isn’t shown, but his presence is implied—likely at the tactical station, monitoring the ship’s systems as they lurch toward shutdown. Worf’s role here is operational enforcer: he ensures Riker’s protocols are executed across all decks, no questions asked. The Klingon’s discipline shines in moments like this: while others might hesitate or debate, Worf acts. The flickering lights would test even his stoicism, but his loyalty to the Enterprise and its crew is unwavering. His silence speaks volumes: ‘I will hold the line.’

Goals in this moment
  • Ensure Emergency Condition Seven is implemented across all decks
  • Support Riker and Picard’s crisis management
Active beliefs
  • Starfleet protocols are tools for survival, not just rules
  • His actions directly impact the crew’s safety
Character traits
Disciplined executor Loyal to a fault Stoic under duress Operational precision
Follow Data's journey

Objects Involved

Significant items in this scene

6
Emergency Condition Seven Protocols

Emergency Condition Seven is the Enterprise’s nuclear option—a protocol designed for catastrophic power failure. Riker’s activation of this protocol ('All decks go to emergency condition seven. Life support and critical operations only.') is a last-ditch effort to preserve the ship’s core functions while everything else shuts down. The protocol’s involvement here is brutal efficiency: it strips the Enterprise of non-essentials (lights, replicators, holodecks) to funnel every erg of power to life support and critical systems. The flickering bridge lights stabilize as the protocol takes hold, but the mood is grim—this is a ship on life support, its crew reduced to survival mode. The protocol’s role is triage: it buys time, but at the cost of the Enterprise’s operational capacity. Its activation forces the crew to confront a harsh truth: They may not recover from this.

Before: Not activated; the ship is operating (barely) under …
After: Fully activated. Non-essential systems are offline, and the …
Before: Not activated; the ship is operating (barely) under normal power distribution, with systems failing as the drain worsens.
After: Fully activated. Non-essential systems are offline, and the ship is running on a skeletal power framework. The crew now has a fragile window to act before the newborn’s drain or the ship’s failing systems doom them all.
Enterprise Bridge and Engineering Lights

The bridge and engineering lights are the Enterprise’s pulse—when they flicker, the ship is dying. Their violent strobing during the power drain isn’t just a visual effect; it’s a metaphor for the crew’s desperation. On the bridge, the lights cast shifting shadows over Picard, Riker, and Data as they grapple with the crisis, their faces illuminated by the erratic glow. In Engineering, the same flickering would disorient Pavlik and Leah Brahms as they work to stabilize the reactors. The lights’ involvement is atmospheric and functional: they reflect the ship’s deteriorating state while also serving as a tangible reminder of the stakes. When Riker’s protocols take effect and the lights steady, it’s a fleeting victory—a sign that Emergency Condition Seven has bought them time, but the respite is temporary. Their role is psychological: the crew’s morale rises and falls with the lights’ stability.

Before: Flickering violently, dimming to near-darkness as the power …
After: Stabilized to full brightness as auxiliary power and …
Before: Flickering violently, dimming to near-darkness as the power drain approaches 93%. The erratic pulses mirror the ship’s instability.
After: Stabilized to full brightness as auxiliary power and Emergency Condition Seven take effect. The steady glow is a small victory, but the crew knows it’s fragile.
Newborn Alien Lifeform's High-Frequency Radio Transmissions

The newborn’s high-frequency radio transmissions are the wild card in this crisis. Data’s observation—'the offspring is emitting a high frequency radio transmission'—hinges the scene on a question: Is this communication, distress, or something else? The transmissions coincide with the power drain’s escalation, suggesting a connection between the creature’s energy needs and its signals. Are they a plea for help? A warning? An attempt to control the ship? The crew’s reactions reveal their uncertainty: Riker wonders if it’s trying to communicate, while Picard and La Forge focus on the immediate threat. The transmissions’ involvement is narratively pivotal: they force the crew to confront the newborn’s sentience, complicating their moral dilemma. If it’s communicating, destroying it (or letting it die) becomes murder. If it’s not, the crew’s efforts to save it may be in vain. The transmissions are the heart of the ethical crisis.

Before: Active and escalating, coinciding with the power drain’s …
After: Continuing unabated, their meaning still unresolved. The crew’s …
Before: Active and escalating, coinciding with the power drain’s increase. Their nature (communication/distress) is unknown.
After: Continuing unabated, their meaning still unresolved. The crew’s next actions (e.g., La Forge’s engineering solution) will determine if they can decipher—or exploit—them.
Pavlik's Comlink

Pavlik’s comlink is the lifeline between Engineering and the bridge—a fragile but critical connection in the chaos. His voice crackles through the device, delivering the dire update: 'The power drain just jumped to ninety-three percent, sir... approaching auto-shutdown.' The comlink’s involvement here is operational: it enables real-time communication during a crisis where every second counts. Its role isn’t just functional; it’s symbolic: the comlink represents the crew’s reliance on each other, even as the ship falls apart around them. When Pavlik taps it to report, the sharp chirp cuts through the bridge’s alarms, a reminder that the crisis is shared—and that solutions may come from anywhere. The comlink’s status is vital: if it fails, the crew’s coordination collapses.

Before: Functional but strained, with static or interference possible …
After: Still operational, but its reliability depends on the …
Before: Functional but strained, with static or interference possible due to the power drain. Pavlik’s voice is clear but tense.
After: Still operational, but its reliability depends on the ship’s power stability. The crew’s ability to communicate hinges on La Forge’s next moves.
Enterprise Warp Engines (Including Intermix Regulators)

The Enterprise’s engines become a pawn in Riker’s high-stakes maneuver. His order—'Take the engines off-line. Supplement with auxiliary power.'—is a calculated risk: by cutting the primary power source, he severs the newborn’s direct link to the ship’s energy, but he also weakens the Enterprise’s mobility and defensive capabilities. The engines’ role here is sacrificial: they are temporarily disabled to buy time, their power rerouted to auxiliary systems. This move underscores the crew’s desperation—they’re willing to hobble their own ship to survive. The engines’ involvement is strategic: their shutdown is a tactical retreat, not a defeat, but the tension lies in whether La Forge can restore them before the newborn adapts or the Enterprise’s systems fail permanently.

Before: Online and functional, but being drained by the …
After: Taken offline and supplemented with auxiliary power. The …
Before: Online and functional, but being drained by the newborn’s energy siphon. The ship’s mobility is compromised as power is diverted.
After: Taken offline and supplemented with auxiliary power. The Enterprise is now stationary but stable (for now), with critical systems preserved.
USS Enterprise's Power Systems (Fusion Reactors)

The Enterprise’s fusion reactors are the lifeblood of the ship—and the newborn’s target. As the power drain spikes to 93%, these reactors become the battleground for survival. The creature’s energy siphoning isn’t just a technical problem; it’s a metaphorical vampirism, draining the ship’s vitality while the crew scrambles to cut off the flow. Riker’s order to take the engines offline and supplement with auxiliary power is a desperate gambit to starve the newborn of its power source, but the risk is clear: if the reactors fail, the ship dies. The flickering bridge lights are a visceral reminder of this struggle—the reactors’ output is the difference between life and auto-shutdown. Their involvement here is existential: without them, the Enterprise cannot function, and the newborn cannot survive.

Before: Operating at 93% capacity, nearing critical failure as …
After: Stabilized to 100% auxiliary power (temporarily), but still …
Before: Operating at 93% capacity, nearing critical failure as the newborn drains power. Lights flicker violently, and systems teeter on collapse.
After: Stabilized to 100% auxiliary power (temporarily), but still under strain. The newborn’s transmissions continue, and the crew’s next move (La Forge’s intervention) will determine if the reactors can be preserved.

Location Details

Places and their significance in this event

1
Main Bridge (USS Enterprise-D)

The Enterprise Main Bridge is the nerve center of the crisis, where Picard, Riker, Data, and Worf orchestrate the ship’s survival. The location’s involvement here is command central: every order, every report, and every desperate gamble originates from this room. The bridge’s design—consoles, viewscreen, tactical stations—frames the crew’s struggle as both technical and moral. The flickering lights and violent shuddering aren’t just set dressing; they’re tactile proof of the newborn’s threat. The bridge’s atmosphere is one of controlled chaos: alarms blare, voices overlap, and the viewscreen (implied) displays the newborn’s energy signatures. The crew’s physical proximity here forces them to confront the crisis as a unit, their fates intertwined. The bridge’s role is decision-making hub: this is where the Enterprise’s survival is debated, argued, and (hopefully) secured.

Atmosphere Tension-filled with urgent, overlapping dialogue, flickering lights casting long shadows, and the hum of failing …
Function Command center for crisis management, where senior officers delegate authority, analyze data, and execute protocols …
Symbolism Represents the Enterprise as a living organism—its bridge is its brain, and the crew its …
Access Restricted to senior officers and authorized personnel during red alert. Junior crew (e.g., Pavlik) communicate …
Flickering overhead lights that dim to near-darkness before stabilizing Alarms blaring in rhythmic pulses, competing with voices Consoles displaying critical system failures (reactor drain, power fluctuations) The viewscreen (implied) showing the newborn’s energy signatures or the ship’s power grid The deck shuddering violently with each power surge

Organizations Involved

Institutional presence and influence

1
USS Enterprise-D (NCC-1701-D)

The USS Enterprise (NCC-1701-D) is both the stage and the stakes of this crisis. As an organization, it’s a living entity under siege, its systems failing as the newborn drains its power. The Enterprise’s involvement here is existential: its survival is tied to the crew’s ability to outmaneuver the newborn, but its very structure (fusion reactors, engines, auxiliary power) is also the weapon being used against it. The ship’s protocols (Emergency Condition Seven) and crew dynamics (Picard’s delegation to La Forge) reflect its institutional identity: a vessel of exploration now reduced to a battleground for survival. The Enterprise’s role isn’t just passive; it’s active resistance: its systems are tools in the crew’s hands, and its failures are the consequences of their (and the newborn’s) actions. The ship’s involvement forces the crew to confront a brutal truth: They are not just saving the newborn—they are saving themselves.

Representation Through its failing systems, institutional protocols (Emergency Condition Seven), and the crew’s coordinated actions. The …
Power Dynamics Vulnerable but resilient—the Enterprise is under attack, but its crew’s ingenuity (e.g., La Forge’s potential …
Impact The crisis tests the Enterprise’s dual role as a scientific vessel and a lifeboat. Its …
Internal Dynamics Hierarchy under pressure—Picard delegates to Riker, who enforces protocols, while La Forge’s personal crisis (Leah …
Stabilize power systems to prevent auto-shutdown and crew death Determine the newborn’s intent (communication/distress) to inform ethical response Institutional protocols (Emergency Condition Seven) to prioritize life support Crew expertise (La Forge’s engineering, Data’s analysis, Riker’s tactical leadership) Physical systems (fusion reactors, engines, auxiliary power) as tools/weaknesses Moral framework (Starfleet’s Prime Directive and duty to preserve life, even alien)

Narrative Connections

How this event relates to others in the story

What led here 1
Causal

"Geordi's deactivation of the atmospheric force field is reported to the Bridge. Lights flicker, and Picard demands an explanation."

Geordi risks decompression to dislodge alien
S4E16 · Galaxy's Child
What this causes 1
Causal

"The Bridge crew makes changes, then Picard asks La Forge about the status of his work in the Shuttlebay. He notes the creature remains attached, further escalating the crisis."

Swarm detected as creature threat escalates
S4E16 · Galaxy's Child

Key Dialogue

"PICARD: Engineering, report!"
"PAVLIK'S COM VOICE: The power drain just jumped to ninety-three percent, sir."
"DATA: Captain, the offspring is emitting a high frequency radio transmission."
"RIKER: Is it trying to communicate?"
"PICARD: Mister La Forge, what is your status?"