STATUS
Working concept. Realm and final location unresolved.
This is not the existing Roadhouse back-room “Partial Recovery” incident. That story uses Patch, Banjo, one remote operator, cached views, and one Roadhouse server. This concept remains separate until the archive establishes whether it belongs to a new realm, a voice-box piece, an album track, or another location.
CORE IDEA
One person or underlying system. Three terminals. The same connection and the same wider brain, but different context, buffers, and loaded history produce different answers and quiet confusion.
This is not three different people and not a schizophrenia or mental-health metaphor. The humour is deadpan and dry, with old technology doing its best through fragmented buffers.
WORLD RULES
- The location is not Clive’s Bar.
- The final location is not yet known.
- A new realm is possible but not confirmed.
- General Pentaverse rules apply unless a later source explicitly establishes an exception.
- One fixer or operator is implied, but identity and visibility remain unresolved.
- Atmosphere may include green screens, industrial hum, rain, fridge cycling, dust, terminal beeps, kettle clicks, and a faint guitar hum.
WORKING VOICE PATTERN
Terminal A carries the calm archive/log voice and retains the fullest history.
Terminal B is hands-on and practical, concerned with panels, contacts, cables, fans, and keeping old systems serviceable.
Terminal C wakes with a blanker local buffer. It feels familiar but lacks the others’ history, retains stray impressions or soundtrack fragments, and is quietly bewildered by what it has missed.
The terminals are not separate characters by default. They are three interfaces returning different results from incomplete shared context.
RECOVERED FRAGMENT — BUFFER LAG
A late server room holds one mainframe and three terminals on the same wiring. Terminal A logs a minor stack lag and preserves what still works. Terminal B cleans contacts and talks a failing fan back into service. Terminal C wakes with incomplete context, dust logs, cable talk, and a tune it cannot quite play.
Terminal C wonders whether they are all the same box pretending otherwise. Terminal A files the philosophical drift under “not tonight.” Terminal B tells it to hold still while the connection is tightened. The three screens dim together as the mainframe settles.
Ending exchange:
Terminal A: “End of entry. All quiet.”
Terminal B: “Seconded.”
Terminal C: “Thirded… mostly.”
RECOVERED FRAGMENT — SHIFT CHANGE
At shift change, each terminal reports from its own partial view. One trusts the logs, one trusts the exposed hardware, and one carries impressions it cannot source. Their disagreement is procedural rather than hostile: three sensible accounts produced from incomplete information.
RECOVERED FRAGMENT — THREE CONNECTIONS
The three terminals attempt to reconcile a common connection without gaining common history. Their synchronisation fails, but their closing ritual aligns: fresh coffee, dust dealt with, a guitar hum in the background, rain on the skylight, and the fridge clicking off in solidarity.
Ending exchange:
Terminal A: “Sync failed. Again. Reckon we call it a night, make a fresh pot, and let the lot sleep it off.”
Terminal B: “Seconded. After the dust’s dealt with.”
Terminal C: “Thirded… though I wouldn’t say no to that guitar hum in the background. Fridge just clicked off in solidarity. Cheeky sod.”
NEEDS REVIEW
- final realm and physical location
- whether the terminals remain anonymous A/B/C or receive archive-role labels
- whether the operator appears directly
- whether this becomes prose, spoken-word audio, an album track, or a recurring fragment set
- whether any relationship to 3CH0 is intended or merely superficial
SOURCE PROVENANCE
Absorbed from:
- Three Terminals same connection (unresolved).md
- seed_Three Terminals, One User .md, used only to distinguish this concept from the Roadhouse spin-off it inspired
- seg_o_roadhouse_back_room_three_terminals_overlap_struck.md, used to verify the later Roadhouse incident is already represented elsewhere
Intake date: 2026-08-11.


