Suite 666 and the world¶
Three character layers¶
The living office is organized around three kinds of character:
- Suite 666 is the protagonist named by the title. Its layout, light, sound, clutter, room purposes, supplies, work evidence, and accumulated artifacts make the team's condition physically legible.
- The outside world is an environmental character. The campaign clock, solar cycle, traffic, weather, delivery windows, building events, and views through the glass create pressure without waiting for conversation.
- The people interpret and change those environments. They have authored identities, bounded schedules, tasks, relationships, commitments, memories, knowledge audiences, needs, and interruptibility, but they do not bypass browser authority.
The hierarchy is about authority, not emotional importance. A model can propose language and bounded social/work records; only browser events can change the world projection.
Fictional people and activity
Jesse Rourke, Toby Hale, Jonah Cade, Avery Crowe, Jamie Wilder, Bennett Pryor, Donna Jackson, their relationships, their studio work, and The Glass Meridian campaign are fictional. Historical evidence documents the physical office and 1993 context, not these characters or events.
Suite 666 as protagonist¶
Suite 666 is not a sentient narrator and cannot speak as a person. Its character is observable through state and physical evidence:
| Dimension | Browser-owned expression |
|---|---|
| Atmosphere | solar light, weather tint, fog, precipitation, room tone, and daily music genome |
| Order | moving boxes, supplies, furniture, delivery status, room purposes, and placards |
| Rhythm | arrivals, departures, focused work, breaks, meetings, delivery windows, and Day 7 campaign time |
| Social load | proximity conversations, commitments, relationship shifts, interruptions, and shared memories |
| Work pressure | task prerequisites, owners, progress, blockers, artifacts, risk, milestone, and build deadline |
| Memory | append-only events, replayable state, conversation records, artifact provenance, and physical traces |
The initial suite is visibly sparse: six workstations and folding chairs occupy mostly bare rooms, boxes wait near an almost-empty supply shelf, and the first playable is due by Day 7 at 6:00 PM. Browser rules can update concrete domains such as tasks, inventory, room purposes, artifacts, and delivery state. Provider prose cannot overwrite the suite with a replacement description.
The fictional room-purpose placards are especially important. They let the same structural space express changing operational use without claiming that those names or placements are historical labels from id Software's office.
The outside world¶
The simulation's absoluteMinute is the only campaign clock.
minuteOfDay === absoluteMinute % 1440 is projected into the tour world, so the
sky, traffic, and HUD share one clock authority. At the normal rate one simulated
minute passes per real second; focused work and sleep still advance that same
event-authoritative clock.
The astronomical presentation uses the June 25, 1993 Town East Tower reference path for each campaign day's time of day. Authoritative weather fields map to sky color and brightness, cloud coverage and speed, celestial visibility, direct and ambient light, fog distance, and bounded precipitation. Traffic density follows that same time projection.
Exterior events have scheduled, active, resolved, and missed states plus an explicit list of rooms from which they are observable. The initial starter-supply delivery runs from 2:00 PM to 3:00 PM on Day 1. Its state drives the delivery cart and player notification; it is not a provider-invented scene.
The outside world is not an omniscient feed. A character learns an event through an allowed observation or memory path. Looking through a window, being in an observable room, hearing another participant, receiving a visitor, and reading an artifact remain distinct browser-owned knowledge routes.
The founders¶
| Character | Control | Authored role | Initial home |
|---|---|---|---|
| Jesse Rourke | Player | Technical lead | West workroom |
| Toby Hale | Autonomous founder | Systems designer | Game room |
| Jonah Cade | Autonomous founder | Programmer | Code workroom |
| Avery Crowe | Autonomous founder | Artist | Art workroom |
| Jamie Wilder | Autonomous founder | Producer | Project room |
| Bennett Pryor | Autonomous founder | Sound designer | East studio |
Jesse is embodied by the first-person #player; the living stage intentionally
does not render a second Jesse character. The other five founders are visible
procedural characters when present. Each has an authored daily schedule with a
deterministic run/day stagger, energy, focus, stress, expression,
interruptibility, current task, and semantic location.
At minute boundaries, the runtime selects bounded actions such as working, collaborating, taking a coffee/rest/window break, meeting, or remaining idle. It chooses only known task and activity anchors, reserves their capacity, plans over known portals, requests structural door actions, and persists enough route and scheduler state to reproduce the same future after reload. Autonomous actors cannot invent geometry or walk through an unaccepted door transition.
The player can interrupt an available founder for a proximity conversation. The browser may turn validated proposals into conversation, task, commitment, relationship, memory, and artifact events. Proposed actor intents stay advisory and do not replace the scheduler.
Donna as the office's reflection¶
Donna Jackson is a fictional optional office-manager candidate whose care is practical, not mystical. She notices the operational signals that make Suite 666 legible: an unattended delivery, an empty shelf, a visitor nobody greeted, an exhausted team, or an obligation without an owner.
Her path remains a player decision:
absent: no Donna visual or schedule is active;candidate: she waits visibly at the threshold but cannot be talked to;hired: she follows the authored entrance route to reception, becomes interactable, and joins her regular office schedule;declined: the optional path is closed for that run.
Every transition requires the same dedicated browser action twice. DeepSeek,
the Curator, typed staffing language, and ordinary conversation cannot select
one. Donna may participate in ordinary office work and conversation only after
hiring. She cannot join D&D activity, receive campaign context, or appear in a
campaign audience; campaignParticipant is invariantly false.
Donna reflects the office without replacing it: the suite accumulates needs, she may coordinate a response, the response changes visible office state, and a run without her must carry those needs differently.
Curator, music, and ritual¶
The Curator is an invisible, non-speaking browser service. Each day has a run-local seed and at most one bounded pressure plan. Optional DeepSeek planning receives a public-only projection and may target only the five autonomous founders. A 35-second authority window, stale-revision checks, strict proposal validation, and deterministic local fallback prevent a remote request from owning campaign progress. The Curator has no memory across runs.
Each campaign day also has a browser-authored music genome: seed, tempo, mode, pulse, density, tension, and timbre labels. The audio layer projects that genome onto the existing score's timing, tonal palette, texture, articulation, and brightness. The model does not supply executable audio or arbitrary samples.
The Glass Meridian D&D session is scheduled for Day 7 from 7:00 PM to 11:00 PM for all six founders. Runtime events move it through scheduled, active, and completed states and can create a recap artifact. Donna's exclusion is both a character boundary and a reducer invariant.
The weekly playable is due one hour before that session. When every required feature and referenced artifact passes browser validation, the build terminal changes from a progress display to the fixed 4 by 3 Relay Run. This makes the week's work observable as authored interaction rather than generated code.
Authority hierarchy¶
authoritative browser event stream
├── campaign clock and living-runtime checkpoint
├── Suite 666: tasks, inventory, room purposes, artifacts, and build
├── outside world: weather, exterior events, traffic/sky projection
├── rituals: D&D and daily music genomes
└── people
├── authored identity, schedule, needs, activity, and location
├── relationships, commitments, and knowledge-scoped memories
├── validated conversation records
└── provider proposals awaiting browser projection
This hierarchy keeps language expressive without allowing fluent output to silently rewrite time, employment, knowledge, persistence, or physical space.