Worst Case Scenario — The Dead Author Still Writes

Voyager S3E25 — “Worst Case Scenario”

The holonovel that wrote itself — Seska’s ghost in the machine.

A meta-episode about authorship, authority, and the danger of unfinished stories. Tuvok’s tactical training program about a Maquis mutiny becomes a crew obsession, and when Seska’s pre-programmed subroutine (planted months before she left the ship) activates, the safety protocols come off and Tom and Tuvok are trapped inside a story that wants them dead.

The Dead Author Still Writes

Seska dies in S2, but her subroutine — planted in Tuvok’s program before her departure — activates like a time bomb. Her authorial voice, frozen at maximum resentment, seizes control of the narrative parameters. The episode literalizes something true: authors don’t die; their intentions live on in the structures they build. A training scenario becomes a weapon because its creator had unfinished business.

Dictates of Poetics vs. Making It Up

Tuvok invokes T’hain of Vulcan — a character’s actions must flow inexorably from established traits. Paris insists on unexpected plot twists. Torres wants heart, emotion, a love scene. Janeway rewrites from the outside. The episode argues that no single approach to storytelling is sufficient — it takes logic, intuition, emotion, and intervention to make a story work. And sometimes, the author needs to let go and let others finish it.

The Story That Escapes Its Author

Tuvok deleted the program. But B’Elanna recovered it. The crew wanted an ending. Seska’s subroutine wanted revenge. The program had a life of its own — not because it was alive, but because stories accrete meaning beyond what their creators intend. The episode itself is a story about a story that refuses to stay deleted.

Holodeck as Safe Space, Breached

The holodeck is supposed to be safe — safety protocols protect users from harm. When Seska strips them away, the breach is both literal (the characters can die) and metaphorical (the stories we tell ourselves can hurt us). The crew’s obsession with the mutiny scenario isn’t harmless fun — it’s processing real tensions between Maquis and Starfleet through fiction. The breach of safety protocols mirrors the breach of the fiction/reality boundary.

Cross-References

This episode pairs beautifully with the pentadirection architecture. The question of who writes the story — and what happens when multiple authors fight for control of the narrative — is the same question the Dissent Protocol wrestles with. Tuvok’s program was designed as a defense (training security officers against mutiny). It became a threat because it escaped its intended context. The same dynamic applies to any protocol: once published, it takes on a life beyond the author’s control.

Gate: 🐺🕊️ — The Dead Author framework connects to the Prior Claim Problem: Seska’s claim on the narrative outlasts her death. Authorship = prior claim, persisted through code.