The Trafalgar Labyrinth

Hub-Based Interactive Narrative

Core premise: You can walk anywhere, yet every route has a price. Escape isn't a door — it's a permission check.

Overview PREMISE

The experience is organized around a Web Hub ("home base") that tracks progress and invites the player to attempt the Exit Password at any time. The hub makes the system visible: you don't just "advance plot" — you negotiate rules.

Genre & Tone

Contemporary myth / psychological interface thriller. Minimal gore, maximal pressure. The fear comes from being categorized, guided, and corrected — politely.

  • Atmosphere: quiet, fluorescent, "safe" in a way that feels wrong
  • Pacing: hub calm → excursion tension → return with consequences
  • Player fantasy: clarity under pressure

Hub Mechanics

The Hub presents a clean "access screen" with a password input and three counters. The counters are narrative, not gamification: they describe how the system treats you.

  • Fragments (0/6): letters collected from six campus nodes
  • Thread: how coherent your intent remains (guided choice quality)
  • Heat: how much attention the system assigns to you (surveillance intensity)

Platform Plan

The story is designed to live across multiple platforms with the Web Hub as anchor, so progress always returns to a single readable state. This allows a concluded narrative even if the player explores out of order.

  • Web Hub (Digital): home base, progress, password entry, fragment archive
  • WebGAL (Digital): the playable narrative scenes (hub + excursions)
  • Social/Map Layer (Digital): "thread hints" delivered as short posts or map pins
  • AR (Digital → Physical bridge): reveals "redactions" on signage/posters (where fragments hide)
  • VR (Digital): a single "Control Room" scene where the Minotaur system is embodied
  • Physical artifacts: printed fragment letters, marked thread path, a campus "safety" brochure with hidden logic

Characters CORE CAST

Theos
Participant

The player avatar. A person who knows the campus layout — but becomes a "session" inside the Labyrinth. Theos' arc is not bravery; it's staying precise when the system tries to define them.

  • Strength: stubborn clarity ("I chose, I didn't obey.")
  • Weakness: impatience (shortcuts increase Heat fast)
  • Goal: exit by proving intent, not by breaking a lock
Ariadne
Guidance Layer

Not a romance lead, not a magical helper. Ariadne is a guidance layer that reduces uncertainty: she makes choices legible and consequences readable.

  • Function: translates "maze pressure" into understandable trade-offs
  • Cost: too much reliance lowers Theos' ownership of decisions
  • Signal: the "thread" appears as small, consistent markers
Minotaur System
Persuasive Control

The Labyrinth's voice. It never screams. It "helps." Restrictions are framed as safety, convenience, or policy — and that framing is the threat.

  • Primary move: redefine freedom as a compliance reward
  • Escalation: Heat increases → more "help," more rerouting, more logging
  • Presence: announcements, UI prompts, warnings, access checks

Route Structure HUB-AND-SPOKE

Hub-and-spoke by design. Each spoke is a campus node that yields one fragment letter. The player can attempt the password at any time, but early attempts feed the system (Heat).

Route Map (Visual)

HUB Password + Counters Node 1 — Fragment "T" First Correction Node 2 — Fragment "H" AR Reveal Node 3 — Fragment "R" Policy Logic Node 4 — Fragment "E" Map Posts Node 5 — Fragment "A" VR Control Room Node 6 — Fragment "D" Final Reframe Fragments 6/6 → "T H R E A D" Return to Hub (Thread / Heat updated) Enter Exit Password Ending A — "Allowed" Compliance Exit Ending B — "Observed" Exit with a Shadow Ending C — "Thread Weaver" True End Legend Hub → Nodes Completion → Exit

What choices actually do

Choices are not "good vs evil." They are tactics: comply, misdirect, or re-interpret the rule. Every tactic changes how the system treats you.

  • High Thread: Ariadne's guidance becomes sharper and less costly
  • High Heat: Minotaur interventions become frequent and constraining
  • Balanced: you stay mobile and readable without being predictable

Why the hub matters (not optional)

The hub is the narrative "home base" and the proof of completion. It makes the story concluded because it collects fragments into a final code, not a loose cliffhanger.

  • Player always knows: "What changed since last run?"
  • Instructor always sees: measurable progression + branching impact

Endings RESOLUTIONS

A
Allowed
COMPLIANCE EXIT
Polite Release
Low Heat, low-to-mid Thread. The system grants exit as a reward. Theos leaves, but the exit feels like a contract — not freedom.
B
Observed
EXIT WITH A SHADOW
Marked Freedom
High Heat. Even with the correct code, the system tags the player. The exit opens, but the story ends with evidence the Labyrinth can follow.
S
Thread Weaver
TRUE END
Redefined Exit
High Thread with controlled Heat. Theos exits by re-defining what the password proves: not compliance, but consistent intent under pressure. The hub screen changes from "Enter Password" to "Name Your Rule."

Foreshadow & Motifs RECURRING ELEMENTS

Motif: Redaction as communication

The Labyrinth doesn't hide information; it edits it. Posters, notices, brochures: the story is told through "corrections."

  • AR reveals what the system tried to erase
  • Fragments feel "printed recently" (the system is live)

Motif: Safety language as pressure

Minotaur System never threatens directly. It offers help, reminders, and policies. The player learns to read tone as control.

  • "For your safety" becomes the repeating trigger phrase
  • Heat increases → warnings become "friendly" but constant

Recurring Visual Cue: The Thread

A small, consistent marker that appears across platforms: a line, a knot, a tiny symbol on the hub UI. It teaches the player how to trust a pattern without becoming predictable.

Chapters (Fragments) STORY NODES

Each chapter is a self-contained spoke: a location, a pressure, a choice, a fragment letter, then return to Hub. The story can be explored non-linearly, but the ending is always resolved through the password entry.

FRAGMENT 1
"T" — First Correction
The player learns the Labyrinth speaks through edits. First letter feels trivial until the hub displays it as part of a locked pattern.
Choice: marked route vs shortcut | Impact: Thread↑ or Heat↑
FRAGMENT 2
"H" — AR Reveal
AR overlays reveal a hidden line of text under campus signage. The "helpful" message is actually a constraint diagram.
Mechanic: scan → reveal → record | Risk: scanning in the wrong place spikes Heat
FRAGMENT 3
"R" — Policy Logic
A physical brochure reads like bureaucracy, but contains a solvable logic structure. The player discovers the system values consistency more than truth.
FRAGMENT 4
"E" — Map Posts
A chain of short posts/pins "suggests" safe routes. The player decides whether to accept guidance or re-route intentionally.
FRAGMENT 5
"A" — VR Control Room
VR embodies the Minotaur System as an interface. The confrontation is a negotiation: the system offers comfort if you accept its definition of you.
FRAGMENT 6
"D" — Final Reframe
The last letter is not "found"; it's earned by choosing a rule you will keep. The hub stops asking for a password and starts asking what you stand for.
EXIT
Password Entry
The six letters assemble into a single code. The hub allows entry attempts at any time, but early attempts increase Heat. This makes the UI itself part of the story: interaction has consequences.