Request Log — Are We LCARS Yet?

2151 — ENT NX‑01

2256 — DISCO (S1–2) USS Discovery, Crossfield Class

2259 — SNW USS Enterprise (Pike refit)

2265 — TOS Constitution Class

2364 — TNG Galaxy Class

2369 — DS9 Terok Nor / Ops Station

2371 — VOY Intrepid Class

2399 — PIC La Sirena / Starfleet HQ

3189 — DISCO (S3+) USS Discovery, Zora Class

2026 — REAL WORLD (CLOSED) Apple + Frontier LLM Subscriptions

2026 — REAL WORLD (OPEN) Framework + Fairphone + Open‑Weight LLMs

Order a specific dish or drink by voice

Mess-hall dispenser takes a spoken order ("Milk, cold.") — no food replicator exists yet, so it's Chef's cabinet system, not synthesis on demand

No on-screen voice drink-order instance sourced yet for this tier — flagged for a follow-up research pass

Food service here runs on "matter synthesizers," not replicators, per this tier's own research — no specific voice-order instance sourced yet

No specific voice drink-order instance sourced yet for this tier — flagged for a follow-up research pass

"Computer, a glass of water, five degrees." — Riker replicates a cold drink for a visiting dignitary, a textbook mundane order

"Computer, orange juice." — Jake orders breakfast in Sisko's quarters, an ordinary replicator request

Coffee replicates fine, but under explicit power rationing this far from a starbase — a recurring constraint, not a one-off

A replicator tea order and a separate replicator wine request, both routine personal orders

Replicator technology is franchise-standard well before this era, but no specific voice-order instance was sourced this pass — flagged for follow-up

A frontier voice assistant can place a smart-kitchen or delivery order on request — nothing in this stack synthesizes food from raw energy, though

Home Assistant can trigger a wired smart-appliance or ordering integration, but only if the household already built that integration — no vendor default

Replicate a non-food item on request

No replicator exists this era at all — confirmed absent, not just unused

No on-screen instance sourced yet for this tier — flagged for a follow-up research pass

Industrial replicators are franchise-standard by this era, but no specific non-food replication instance was sourced this pass — flagged for follow-up

An antique subspace-transceiver part, replicated from a design pulled out of an old data file in the station library — a routine hobby-project request

Replication of spare parts is explicitly constrained by hardware scarcity out here — the crew has to ration what gets replicated, not just what gets eaten

No on-screen instance sourced yet for this tier — flagged for a follow-up research pass

On-demand 3D printing and delivery exist, but nothing in this stack turns a spoken request directly into a physical object the way a replicator does

Same gap as the closed stack — open hardware doesn't change what's physically possible here

Synthesize a meal reflecting a species' cuisine or dietary need

No replicator exists this era — dietary needs are handled by Chef's actual cooking and a hydroponic greenhouse, not synthesis on demand

No on-screen instance sourced yet for this tier — flagged for a follow-up research pass

No specific dietary/species-restriction instance sourced yet for this tier — flagged for a follow-up research pass

A Cardassian recipe turns up pre-loaded in the station's own food replicator memory bank — leftover data from the station's original operators, years into Starfleet use

No specific dietary/species-restriction instance sourced yet for this tier — flagged for a follow-up research pass

An assistant can generate a recipe or plan a dietary-appropriate meal; nothing in this stack physically synthesizes the food itself

Same caveat as the closed stack, local-model-generated

Run a holodeck/holosuite recreational program

No holodeck exists anywhere on this ship — confirmed absent

Holo-communicators exist briefly this era, but a malfunction gets them stripped out fleet-wide — the direct, on-screen reason the next era has none

This tier's own writers frame its debut tech as a "holodeck-precursor," not a full holodeck — no specific recreational-program instance sourced yet

No holodeck exists this era

Ordinary personal holodeck use — Data practicing ballroom dancing with a computer-generated partner and music ahead of a wedding, no malfunction involved

The station's holosuites are franchise-famous, but no specific recreational-program instance was sourced this pass — flagged for follow-up

Both a pulp holo-adventure program and a small-town holo-village get run for ordinary recreation across multiple episodes, no crisis attached

Holographic crew are well-established this era, but no specific recreational-program instance was sourced this pass — flagged for follow-up

No specific recreational-program instance sourced yet for this tier — flagged for a follow-up research pass

This stack's own review calls a mixed-reality headset "the closest 2026 gets to... a holodeck ticket" — immersive VR, not physical holography

Same caveat as the closed stack — open VR/game-engine tooling exists, but it's DIY integration, not a turnkey holodeck

Reserve/schedule holodeck time for personal recreation

Not applicable — no holodeck exists this era

Not applicable — no holodeck-grade recreation confirmed this era

Not applicable — only a holodeck-precursor concept exists this era

Not applicable — no holodeck exists this era

Holodeck use is heavily documented this era, but no specific booking/scheduling instance was sourced this pass — flagged for follow-up

No specific booking/scheduling instance sourced yet for this tier — flagged for a follow-up research pass

Holodeck program scheduling functions as a personal-recreation booking system — the crew reserves time same as any shared shipboard resource

No specific booking/scheduling instance sourced yet for this tier — flagged for a follow-up research pass

No equivalent concept — nothing in this stack maps onto reserving shared "holodeck time"

Adjust ambient temperature/lighting/environment by voice

No on-screen instance sourced yet for this tier — flagged for a follow-up research pass

This era's interface already includes ambient voice pickup shipwide (see the comparison page), but no environment-adjustment-specific instance was sourced this pass — flagged for follow-up

No on-screen instance sourced yet for this tier — flagged for a follow-up research pass

Mainstream smart-home voice control of lighting and thermostats is a well-documented, everyday consumer capability

"Computer, lights" — this stack's own Home Assistant + local Whisper voice pipeline runs entirely on-LAN, no cloud wake word required

Run a bridge/ship status check or diagnostic report

No on-screen instance sourced yet for this tier — flagged for a follow-up research pass

This tier's own research pass explicitly found no clean routine bridge-diagnostic moment to cite — a documented gap in available material, not an oversight

A pre-launch bridge status check — "lights are green across the board," course confirmed laid in — a standard verbal status report

No on-screen instance sourced yet for this tier — flagged for a follow-up research pass

A fluidic sensor diagnostic run solo, and a subsystem diagnostic handled in the background while coffee replicates — both ordinary, no malfunction

No on-screen instance sourced yet for this tier — flagged for a follow-up research pass

A bio-neural gel-pack infection gets diagnosed via computer, and an engineering diagnostic terminal sees routine, non-crisis research use elsewhere

A navigation sensor status check, plus a diagnostic/reactivation pass on a dormant positronic matrix

No on-screen instance sourced yet for this tier — flagged for a follow-up research pass

Device and system health checks are a standard, mainstream feature on modern phones and computers

Mature, self-hostable open-source system-monitoring tooling covers this well

Perform a calculation or data-modeling query

No on-screen instance sourced yet for this tier — flagged for a follow-up research pass

"Based on computer analysis, of course..." — computer-modeled logistics for tribble disposal, treated as an unremarkable background function

No on-screen instance sourced yet for this tier — flagged for a follow-up research pass

Provides the spacetime math needed to break a recursive time loop — a defining, high-stakes version of the same basic function

Frontier assistants handle arbitrary calculation and data modeling trivially

Local open-weight models handle most calculation fine, but this stack's own review notes they trail the frontier on the hardest reasoning

Look up a fact or run a background check

No on-screen instance sourced yet for this tier — flagged for a follow-up research pass

"Run a full computer check on Mister Flint and on this planet... stand by with your results" — an ordinary investigative order, successfully returned

A clan-affiliation database check comes back with a clean negative result — the lookup function works; the record just isn't there

A review of all off-station information requests made about a specific officer, cross-checked against a medical-history query — a records search that becomes key evidence

No on-screen instance sourced yet for this tier — flagged for a follow-up research pass

Security footage and database records get pulled on a specific incident as a routine investigative step

Identifies a specific ship-propulsion detail by cross-referencing Federation records

Trivial for a frontier assistant, with the usual accuracy caveat on obscure or contested facts

Same capability, more caveated on obscure or niche facts for smaller open-weight models

Access ship schematics or a technical manual on demand

No on-screen instance sourced yet for this tier — flagged for a follow-up research pass

This stack's own review states it plainly: what it can't buy at any price includes root access and schematics

Every board, port, and panel in this stack's hardware is a published, orderable part — schematics-level openness by design

Feed the computer an instruction it takes too literally, or a logical paradox

No on-screen instance sourced yet for this tier — flagged for a follow-up research pass

An android short-circuits on a liar's paradox ("Illogical! Illogical! Please explain."), and a hostile probe gets caught in a fatal logic loop ("Error. Error. Error. Examine.") — the same vulnerability twice over

This era's two biggest computer-driven plots both start with a hologram taking an instruction too literally — the same failure mode as the previous era, softened but not eliminated

No on-screen instance sourced yet for this tier — flagged for a follow-up research pass

Not applicable in the same way — full sentience by design doesn't map onto a logic-paradox exploit the way a literal-minded computer does

Adversarial prompts can confuse a large language model, but it's a different failure mode entirely — no short-circuiting

Same caveat as the closed stack

Translate an unknown spoken language in real time

This era's defining flaw: a universal translator that repeatedly fails on first contact, across four separate documented incidents, sometimes fixed only by switching to a human doing it manually

No on-screen instance sourced yet for this tier — flagged for a follow-up research pass

Successfully adapted to compare brainwave patterns and translate an entirely non-verbal form of communication — a genuine edge case handled well

No on-screen instance sourced yet for this tier — flagged for a follow-up research pass

Real-time translation is a documented, marketed feature of this stack's frontier assistants; quality varies by language pair

Open-weight models can do this too, generally a step behind frontier quality per this stack's own review

Dictate or record a personal/captain's log

"Computer, pause" / "Resume log" — reliable voice-controlled log dictation, even while the translator is actively failing elsewhere

No on-screen instance sourced yet for this tier — flagged for a follow-up research pass

A standing order to log ongoing planetary survey data — ordinary, ongoing data-logging

No on-screen instance sourced yet for this tier — flagged for a follow-up research pass

Voice memo and dictation is a standard, mainstream feature

Local speech-to-text pipelines can do this; quality depends on what's actually been wired up

Decrypt or analyze an intercepted transmission

An intercepted message gets run through the translation matrix to decrypt and translate it — a routine intelligence task, no drama attached

No on-screen instance sourced yet for this tier — flagged for a follow-up research pass

A frontier assistant can analyze or decode text handed to it directly; real signal-intelligence decryption is a different, specialized capability entirely

Same caveat as the closed stack

Scan a person for a medical condition, parasite, or pathogen

No on-screen instance sourced yet for this tier — flagged for a follow-up research pass

A shipwide EM scan plus a medical biofilter diagnostic successfully detects an infection — but the same scan triggers a full station lockdown, so it's a success that escalates

No on-screen instance sourced yet for this tier — flagged for a follow-up research pass

A routine sickbay scan run on a crew member who turns out to be a chronic hypochondriac — an ordinary, low-stakes diagnostic visit

No on-screen instance sourced yet for this tier — flagged for a follow-up research pass

This stack's own review calls its wearables "the closest 2026 gets to... a tricorder" — real health sensors exist, but nothing at diagnostic-grade for pathogens or parasites

No equivalent open-hardware medical-scanning device exists in this loadout

Convert the holodeck/holosuite into medical overflow space

Not applicable — no holodeck exists this era

Not applicable — no holodeck-grade recreation confirmed this era

Not applicable — only a holodeck-precursor concept exists this era

Not applicable — no holodeck exists this era

No specific medical-overflow instance sourced yet for this tier — flagged for a follow-up research pass

The holodeck gets explicitly repurposed as overflow triage space during a medical crisis — a direct, on-screen instance of exactly this request type

No specific medical-overflow instance sourced yet for this tier — flagged for a follow-up research pass

No equivalent concept — nothing in this stack maps onto repurposing shared VR/AR space as clinical overflow

Locate a specific person or object shipwide via internal sensors

No on-screen instance sourced yet for this tier — flagged for a follow-up research pass

"Computer, locate Jake Sisko." / "Jake Sisko is in cargo bay fourteen." — an entirely ordinary station-wide locate query

No on-screen instance sourced yet for this tier — flagged for a follow-up research pass

Retrieves a specific set of coordinates from records on request — the same locate/navigation-query pattern, applied to a location rather than a person

Device-level location sharing ("Find My"-style) is a real but narrower analogy — it tracks devices people opt into, not people directly

Self-hosted presence/tracking setups exist, but require the household to build the integration themselves

Verify a voice/biometric authorization code before a sensitive action

A verbal authorization code is given and works — but it's spoken to a human receptionist over comms, not to the ship's own computer directly, so the "computer, authorization..." convention itself isn't confirmed yet

No on-screen instance sourced yet for this tier — flagged for a follow-up research pass

Access control exists and generally works, but in one documented case a planted security exploit lets it wrongly deny an officer's own valid clearance — a compromise, not a clean success

No on-screen instance sourced yet for this tier — flagged for a follow-up research pass

A security console accepts a forged identification outright — a documented authorization failure, not a partial one

No on-screen instance sourced yet for this tier — flagged for a follow-up research pass

Voice/biometric unlock exists for personal devices in this stack; nothing analogous exists for authorizing ship-scale actions

Hardware security keys provide strong device-level authentication here; same ship-scale gap as the closed stack

Ask the computer for guidance on an open-ended problem

No on-screen instance sourced yet for this tier — flagged for a follow-up research pass

Consulted directly for a solution — "did you find out anything from the computer?" / "Nothing useful." An honest non-answer, not a malfunction

No on-screen instance sourced yet for this tier — flagged for a follow-up research pass

Asked directly for personal guidance on a difficult crew decision — a genuine advisory exchange, not just a data lookup

Open-ended advice and recommendations are close to core functionality for a frontier conversational assistant

Open-weight models can do this; judgment quality is more variable than the frontier

Query or manage a personal schedule or duty roster

No on-screen instance sourced yet for this tier — flagged for a follow-up research pass

"Computer, display the Engineering duty roster for the next three days." — boilerplate shipboard admin, immediately followed by the plot turning dramatic; the request itself wasn't

No on-screen instance sourced yet for this tier — flagged for a follow-up research pass

Holodeck program scheduling doubles as personal-recreation booking — the closest on-screen analogue to managing a personal schedule via computer

No on-screen instance sourced yet for this tier — flagged for a follow-up research pass

Calendar and reminder management is a core, mainstream voice-assistant feature

Standard self-hosted calendar/reminder integrations are mature and widely used

What can you actually ask it to do?