Fabula
Object
Object

USS Enterprise Main Computer

A distributed, ship‑spanning authoritative computing presence that manifests as a clipped, disembodied voice and through local consoles (status bands, terse diagnostic text, responsive touch panels). It provides centralized control and diagnostics for sensors, propulsion, turbolifts, and localized modules; logs experiment telemetry, issues countdowns from bridge stations, answers Sickbay queries with clinical diagnostics, and records operational evidence. During the crisis its cadence can fracture into terse, interrupted prompts and system indicators flicker, requiring crew overrides.
6 appearances

Purpose

To monitor, coordinate, and control core starship functions—sensors, navigation and propulsion state, environmental and elevator systems—and provide voice and console feedback to bridge officers.

Significance

Acts as the narrative fulcrum that converts an apparent external threat into an internal mystery: its aberrant speech (chess moves) and cascading failures force command to divide priorities between damage control and investigation, eroding certainty and escalating psychological tension aboard the Enterprise.

Appearances in the Narrative

When this object appears and how it's used

6 moments
S3E1 · Evolution
Override: Beverly Shuts Rogue Refreshment Slot

The Enterprise ship computer manifests as the neutral, disembodied voice that replies to Beverly's commands; it insists diagnostics are normal even while hardware behaves otherwise, demonstrating an epistemic gap between sensor/logic reports and observed reality.

Before: Responsive and authoritative—reporting the food slot 'functioning properly' despite ongoing malfunction.
After: Remains the authoritative interface answering Beverly, but its diagnostic assertion is visibly contradicted when the slot halts after her override; it is effectively overridden in practice though still active.
View full event
S3E1 · Evolution
Quiet Panic: Beverly Presses Picard About Wesley

The ship's computer is the subject of the opening directive (diagnostics, food slots) and the underlying procedural worry. It is invoked to justify immediate action and to root the scene's personal conversation in a practical operational problem that threatens Doctor Stubbs' experiment.

Before: Partially compromised or unreliable but appearing to function ('seems to be working again, for the moment').
After: Designated for a level one diagnostic series; condition unresolved but slated for verification and repair.
View full event
S3E1 · Evolution
Duty vs. Discovery: Framing the Core Crisis

The main computer is the ostensible source of the crisis discussed: Picard alerts the council to a potential breakdown, Data offers probabilities about its self-correction, and the system's integrity frames the debate over mission continuation versus crew safety.

Before: Operational but exhibiting unexplained anomalies leading command to suspect a partial compromise; engineering is alerted.
After: Uncertain and actively under repair by engineering (Commander La Forge referenced as attempting repairs); remains the central technical unknown driving decisions.
View full event
S3E1 · Evolution
Stubbs' Ultimatum — Picard Holds the Line

The USS Enterprise main computer is the subject of the briefing: its potential breakdown initiates the debate. Officers argue over risk decisions with the computer malfunction as the technical fulcrum that determines whether the experiment proceeds or the ship withdraws.

Before: Suspected instability or fault flagged; under diagnosis with Commander La Forge attempting repairs.
After: Unresolved — still under repair and central to command's decision; technical uncertainty persists as ethical debate is interrupted by an operational comm.
View full event
S3E1 · Evolution
The Blast and the Obsessed

The Enterprise Ship Computer acts as the repository and conduit for streaming telemetry: consoles ingest the neutron star's output, displaying facts, figures, and overlays that guide the crew and become the medium through which Stubbs loses himself in raw numbers.

Before: Operating normally, ready to record and present incoming experiment telemetry to bridge and science consoles.
After: Flooded with a high‑volume telemetry stream; actively logging and displaying torrented data, perhaps strained but functioning as the archive of the event.
View full event
S3E1 · Evolution
Obsession at the Eye of the Blast

The ship's computer is the repository for the torrent of telemetry Stubbs is harvesting; it records and displays the incoming numbers and figures while serving as the documentary witness to the experiment's result and as the medium through which data is secured.

Before: Operational and receiving telemetry, routing data to consoles and archives.
After: Continuing to log data from the event but potentially receiving high‑volume inputs; acts as the persistent record although some inputs may be compromised by the blast's intensity.
View full event