diff --git a/docs/workshops/gj-6711-furthest-system/mechanics-gestalt.md b/docs/workshops/gj-6711-furthest-system/mechanics-gestalt.md new file mode 100644 index 000000000..ee63741f9 --- /dev/null +++ b/docs/workshops/gj-6711-furthest-system/mechanics-gestalt.md @@ -0,0 +1,774 @@ +# Abzu — Mechanics Design +**Role:** Systems Designer (Gestalt) +**Date:** 2026-03-16 +**Workshop:** GJ 6711 — Furthest System + +--- + +## Prefatory Note + +The team built a hauntingly coherent world and then described how it feels. This document +translates that into what the player does. Everything here assumes the sealed envelope and +its internal canonical position: the thinness is a boundary condition between normal space +and the Interstitium that requires continuous observation from the human side to remain +stable. The community is the mechanism. The player can become part of it. + +The core design problem is this: the best ending is "you chose to stay or chose to leave +and neither choice is wrong." That ending only works if the player has invested something +real — real time, real decisions, real accumulated presence — in the vigil. Without +investment, stay/leave is a menu option. With investment, it's a genuine question. + +Everything below is designed to create that investment without forcing it. + +--- + +## 1. Player Verbs at Abzu + +Let me map the concrete actions available. The problem with "experience atmosphere" is that +it is not a verb. Here are the verbs. + +### Primary Verbs + +| Verb | What it looks like | Consequence | +|------|-------------------|-------------| +| **Watch** | Stand at a watch position during a community shift slot | Advances watch investment, triggers perception events, enables monologue unlocks | +| **Investigate** | Examine threshold markings, architectural anomalies, Mode 1 structures | Accumulates frame evidence; unlocks conversation topics | +| **Converse** | Talk to community members at appropriate trust tiers | Unlocks information tiers, surfaces rumors, reveals personal histories | +| **File** | Write the Adams & Ford entry | The one irreversible action at Abzu; propagates into the Reach | +| **Document** | Take field notes during watch (sub-action within Watch) | Produces the raw material for the entry; different note-taking produces different entries | +| **Depart** | Leave via gate | The binary choice; closes the Abzu chapter | + +### Secondary Verbs (Support the Primary Loop) + +| Verb | What it produces | +|------|-----------------| +| **Orient** | Navigate Stillpoint's deliberately disorienting layout — finding the watch location is itself a puzzle | +| **Sleep** | Advances time; triggers monologue drift events at different phases of stay | +| **Eavesdrop** | Overhear shift-change conversations; different information than direct conversation | +| **Examine doors** | The architectural evidence; triggers the monologue that fires at taller-than-standard geometry | +| **Access Meridian records** | The Institute's file is classified — but the Institute's interest is public record | +| **Read archive** | The community's oldest records; tier 4 knowledge, requires time investment to access | + +### What Is NOT a Verb at Abzu + +This matters. Abzu is designed to resist the normal game verbs: +- **Combat** — there is nothing to fight and no one to fight +- **Hack** — there is nothing to hack; the community has minimal Meridian presence +- **Steal** — there is nothing worth stealing; the community does not have extractable resources +- **Persuade** — you cannot talk your way to understanding; only time produces it + +A player who arrives with a toolkit built for other systems will find their tools don't +fit. This is designed. The monologue should register this: "There's nothing here to work +on. That's not a complaint. It's information." + +--- + +## 2. The Watch as Mechanic + +This is the load-bearing mechanic. Get this wrong and everything else collapses. + +### What "Keeping Watch" Is, Mechanically + +The watch is a **spatial+temporal commitment**. The player must be at a specific location +(the watch position, or within a defined proximity zone) for a specified duration. That is +all. No button to press. No puzzle to solve. No progress bar. + +The absence of a progress bar is intentional and important. The watch cannot be optimized. +You cannot "do watching efficiently." You are present, or you are not. + +**Why this is fun:** It inverts the normal game loop. The normal loop is: gather information, +form hypothesis, act, receive feedback, update. The watch loop is: be present, wait, notice, +be changed by noticing, wait more. Players who have only the first toolkit will find this +frustrating. Players who engage will find it revelatory. Both responses are valid and the +game should handle both (see Section 6). + +### The Watch Position + +There is one primary watch location: the thinness itself, which is not visible as a distinct +object. It is a zone. It is marked by the Mode 1 structures surrounding it — the founding +settlers built their watch structures around it, not to it. There is no wall around it. There +is no sign. There is a place where the community sits, in rotation, and looks at something the +player cannot quite identify as a specific thing to look at. + +Finding the watch location is itself the first challenge. The settlement's deliberately +disorienting layout (Araminta's design: no center of gravity, competing centers, paths that +aren't direct) means the player cannot navigate to it immediately. The watch location is +not labeled on any insert overlay — the community does not publish its location on the +Meridian. You find it by following community members during their shift changes. + +**The fog interaction:** When the player reaches the watch zone for the first time, the +fog-of-war behavior changes subtly. Not dramatically — the fog does not lift, the +shadowcasting does not expand. What changes is the quality of the fog at the boundary of +the watch zone. Instead of the normal fog gradient (seen / seeing / unseen), there is a +region at the boundary of the thinness where the fog behaves as if it cannot decide. Tiles +oscillate between seen and partial-seen states at a frequency the player's visual system +will register as movement. The monologue fires: "Something's wrong with my perception +here. Not wrong. Different. Like looking at something that isn't quite in the same light +as everything around it." + +### The Shift Schedule + +The community runs continuous shifts. These are mechanical facts: + +| Shift | Duration | Time of day | +|-------|----------|-------------| +| Dawn shift | 4 hours | First light to mid-morning | +| Day shift | 6 hours | Mid-morning to mid-afternoon | +| Dusk shift | 4 hours | Mid-afternoon to last light | +| Night shift | 6 hours | Dark hours | +| Deep night | 4 hours | Lowest point | + +Shifts overlap by 15 minutes. This overlap has never been shortened. + +The player can take a watch slot. The community will accept this. They will not explain +why. No NPC says "we need more watchers." They simply acknowledge the player's presence +at the watch position with the same matter-of-factness they apply to everything at Abzu. + +**Mechanical effect of taking a shift:** +- Advances the watch investment counter (see below) +- Triggers perception events appropriate to duration +- Opens certain community conversations that are only available to someone who has watched + +**Mechanical effect of missing a shift the player committed to:** +- The community notices — but does not comment. The NPC who would have relieved the + player watched alone. The monologue fires during the next encounter with that NPC: + "She knows I wasn't there." +- The watch investment counter does not advance +- Nothing catastrophic happens on a single miss. The vigil has 4,000 people and has + run for 300 years. One missed shift by a visitor is not a crisis. + +### Watch Investment Counter + +This is the hidden variable that drives the entire system. The player never sees it +directly. It drives what the game shows and tells them. + +``` +WATCH_INVESTMENT + Range: 0 to 100 + Display: never (internal only) + + Increments: + +10 per completed shift (diminishing returns above 50) + +3 per documented observation during a shift + +5 per conversation unlocked through watch presence + +15 for staying through a non-human shift change (see below) + + Decrements: + -5 per day without visiting the watch zone + -0 if the player is actively investigating, sleeping, or conversing + (absence is neutral, not punishing — only prolonged disengagement costs) + + Thresholds: + 20: Perception events begin (fog oscillation becomes more pronounced) + 40: Tier-2 community information unlocks; monologue register shifts + 60: Archive access unlocks; monologue describes "settling" + 80: Non-human shift change visible at Elevated tier; deepest conversation unlocks + 100: Full integration threshold — "you have stayed long enough to understand + that understanding is not what happens here" +``` + +**The player cannot grind this.** The shifts are 4-6 hours of game time. The player +cannot sleep-advance and count shifts. Being physically present at the watch zone for +non-shift hours contributes negligibly. The watch mechanic requires the player to engage +with the rhythm of community life at Abzu, not to optimize a number. + +### Doing It Well vs. Doing It Poorly + +| Quality | What it looks like | Feedback loop | +|---------|-------------------|---------------| +| **Well** | Taking shifts, arriving on time, staying for the overlap, documenting observations | Richer perception events, deeper community access, monologue coherence increases | +| **Adequately** | Taking shifts but leaving early, missing documentation | Mechanical progress, thinner experience | +| **Poorly** | Visiting the watch zone but not committing to shifts | Very slow investment gain, the community's matter-of-factness starts to feel pointed | +| **Not at all** | Skipping the watch entirely and focusing on investigation/filing | Possible — but the Adams & Ford entry reflects it. The community knows. The monologue knows. | + +The feedback is qualitative, not punitive. The game does not lock content from players +who don't watch. It gives them a different experience of the same content. + +--- + +## 3. Bleed on a Tile Map + +This is the visual/mechanical expression of vigil failure. It needs to be specific. + +### What Bleed Is, Mechanically + +Bleed is what happens when the thinness expands because observation lapses. At Abzu, the +vigil is stable — 300 years of unbroken continuity. The player will not trigger bleed +through a single missed shift. What the player experiences is the ambient presence of +the thing being managed — a constant low-level hum of the boundary condition — and +occasional events that suggest what bleed would look like at scale. + +These events are the game's way of giving the player experiential understanding of the +stakes without manufacturing a crisis. + +### The Bleed Tile States + +Standard fog-of-war has three states: seen, partial (remembered), unseen. At Abzu, in +the vicinity of the watch zone, a fourth state exists: + +**Threshold-adjacent tile state:** A tile at the boundary of the thinness is visible +by normal shadowcasting standards but is rendered differently. Characteristics: + +- The amber light quality is wrong. Not darker, not brighter. The color temperature + shifts toward the diffuse gas-giant reflection spectrum: slightly cooler, slightly + silver instead of amber. The effect is below conscious threshold on first encounter. + It accumulates. +- Entity color coding (D-033) behaves normally on threshold-adjacent tiles — but the + teal/green/amber of NPC relationship colors appears slightly desaturated. The D-033 + signal is reliable; the background it's read against is subtly different. +- No special visual effect, no shader, no post-processing. The difference is implemented + as a lighting zone with the reflected-light palette values from Araminta's spec + (`#c4a040` instead of `#d4920a`). Subtle. Intentional. Unannounced. + +### Bleed Events (Storyteller-Driven) + +The storyteller can trigger bleed events. These are rare — 2-4 per playthrough at Abzu, +depending on watch investment. They are the game's most honest expression of what is +at stake. + +**Event type: The Fog Expansion** + +Trigger: The player has been at Abzu for 3+ in-game days without taking a watch shift. + +Mechanical expression: +1. A specific cluster of tiles near the watch zone (not in the player's current LOS) + reverts to "unseen" state despite having been previously visited +2. The reversion is gradual — over 10-15 real seconds, the explored-and-remembered + tiles at the thinness boundary drain back to full fog +3. The monologue fires: "I've been here. I know this place. Why does this look like + I've never seen it?" +4. The effect reverses within the same scene if the player returns to the watch zone. + Normal fog exploration rules apply once they are physically present. + +This is not a jumpscare. It is not dramatic. It is a subtle wrongness that a player who +is paying attention will notice and a player who is not paying attention will walk past. +Both are valid responses. The player who noticed gets more. + +**Event type: The Overlap Failure** + +Trigger: The player has taken a watch shift and left before the overlap window (the +15-minute overlap before the next watcher arrives). + +Mechanical expression: +1. As the player leaves the watch zone before their relief arrives, the threshold-adjacent + tiles begin the fog oscillation behavior described earlier — the flickering between + seen and partial-seen +2. The oscillation increases in frequency for the 15-minute window when the thinness + is unattended +3. The community member who was supposed to relieve the player arrives and the oscillation + stops. The tiles stabilize. +4. The monologue fires, delayed: "I don't know what I thought I was doing. There's + a reason the overlap exists." + +**Event type: The Recognition** + +Trigger: Watch investment crosses 60 (the "settling" threshold) AND the player has +Augmented or Elevated tier. + +Mechanical expression: +1. During a watch shift, the fog at the thinness boundary does something it doesn't + do anywhere else in the game: it becomes directional. The normal fog gradient radiates + outward from the player. At the thinness, for a brief window (5-10 real seconds), + the fog gradient appears to radiate INWARD toward the watch zone — as if something + on the other side of the boundary is looking back. +2. Elevated tier only: the inward-gradient fog is accompanied by a thermal signature + in the watch zone that resolves to nothing when examined directly (Nigel and Araminta's + convergent design for the shift-takers). It is present, then it is not, without any + animation of disappearance. It was there. Now it isn't. +3. The monologue fires: "That was attention. Something paid attention to me." Full stop. + No elaboration. The player speculates. + +**What Bleed Would Look Like at Scale (Player Never Sees This)** + +For the design team: full bleed propagation would look like the fog-expansion event but +permanent, accelerating, and spreading through the gate network. High-bleed gates in other +systems are the distant echo of this. The player at Abzu can intuit this connection — the +monologue can gesture toward it at high watch investment — but the game never confirms +the mechanism. + +### Tile Map Expression: Summary Table + +| Bleed state | Tile appearance | Fog behavior | Sound | +|-------------|-----------------|--------------|-------| +| Normal (stable vigil) | Amber light (#d4920a) | Standard shadowcast | Ambient hum, low | +| Threshold-adjacent (always present) | Cool-silver light (#c4a040) | Slight oscillation at boundary | Hum frequency subtly shifted | +| Observation lapse (< 15 min) | Amber, slightly desaturated | Boundary tiles drain to fog | Hum gaps — brief silences | +| Fog expansion event | Normal, but wrong | Previously explored tiles revert | Silence, then ambient resumes | +| Recognition event (Augmented+) | Inward fog gradient, 5-10s | Direction reversal, then normal | Tone — not a sound effect, a frequency | + +--- + +## 4. The Adams & Ford Entry as Mechanic + +The commission is the player's external motivation and their decision surface. Let me +break down what this actually means mechanically. + +### The Entry as Accumulated Evidence + +The Adams & Ford entry is not written in a single interaction. It is assembled from the +player's entire time at Abzu. Every documented observation, every conversation, every +watch shift contributes to a pool of available material. When the player chooses to file, +they select from that pool — not from a list of abstract choices, but from the specific +things they recorded. + +**The documentation system:** + +During investigation and watch shifts, the player can document observations via a +field notes verb. This is a single button press — not a text input, not a journal +system. The player presses "document" and the system records: location, time, perception +tier active, watch investment level, and a system-generated summary of what the character +can currently perceive (derived from the monologue system's active state). + +| Note taken at | What it records | What entry it unlocks | +|---------------|-----------------|----------------------| +| Watch zone, investment < 20 | Baseline perceptual data: light quality, architectural description | "A quiet system at the end of the network" — the first correspondent's register | +| Watch zone, investment 20-40 | Anomalous perceptual data: fog quality, threshold-adjacent lighting | "Something about the light here" — the second correspondent's register | +| Watch zone, investment 40-60 | Relational data: the community's accommodation, the overlap ritual | "The community keeps a schedule that has no apparent purpose" | +| Watch zone, investment 60-80 | Understanding-approaching data: the watch as load-bearing, the overlap as necessity | "Three hundred years of something I cannot name" | +| Watch zone, investment 80+ | Integration-level data: the thinness as felt presence, the watching as acknowledgment | "The entry cannot be filed because I do not have the category for what I experienced" | + +This is the game's mechanical answer to why three correspondents failed. They were working +from lower watch investment. Not because they were less skilled — because they didn't stay +long enough. The first correspondent left during Phase 1 (days 1-14). The second left +during Phase 2. The third is in Phase 3, which is why they can't leave. + +### The Filing Decision + +When the player chooses to file, they face a single decision of substance: **what register +is the entry written in?** + +The game presents the player with their accumulated notes. Notes are grouped by register +(the five levels above). The player selects which notes form the basis of the entry. They +do not write text — the system generates the entry from the selected notes using the +monologue system's vocabulary. The player's choice is editorial: what did you decide to +include? + +**The consequence is permanent and propagates:** The filed entry goes into the game's +Meridian as the authoritative Adams & Ford record for GJ 6711. On subsequent playthroughs +(and in the shared setting's future), other characters can find this entry. The entry +describes what the player understood. If the player filed on day 3 with investment < 20, +the entry reads like the first correspondent's — professional, present, and slightly off. +If the player filed with investment 80+, the entry reads like someone who has been to a +place and cannot explain what the place did to them. Both are accurate. Neither is complete. + +### The Entry and the Watch Mechanic: Interaction + +Here is the emergent mechanic that makes this interesting. The Adams & Ford commission +creates tension with the watch: + +- Filing early (low investment) means writing an entry like the ones that came before — + technically complete, experientially insufficient. The commission is fulfilled. The + player can leave. But the entry will circulate through the Reach as the authoritative + description of Abzu, and it is wrong in ways the player may only understand on a + second playthrough. + +- Filing late (high investment) means the entry is richer and stranger and will do + something different to the Reach's understanding of this system. But staying long + enough to reach high investment means the player has engaged with the watch, and + engaging with the watch is how the stay/leave decision becomes real. + +The commission is a **deadline the player sets for themselves.** There is no in-game +pressure to file by a certain date. The player can stay indefinitely. The commission +is just permission — Adams & Ford contracted them to write an entry, not a +good one. The minimum is always available. The question is whether the player wants +to do more than the minimum. + +This is the same question the vigil asks. + +### What Happens If the Player Ignores the Watch and Just Files + +Let me be concrete about this path because it is valid and should be honored. + +A player who arrives, investigates efficiently, gathers tier-1 and tier-2 information, +takes notes during investigation (not during watch shifts), and files on day 5 will +produce an entry with investment ~ 10-15. The entry will read like the first +correspondent's. It will be technically accurate. It will describe a quiet frontier +system. The commission pays. + +The player can depart. The game does not punish this. + +But the monologue fires as they approach the gate: "I got what I came for. I should +feel satisfied." Pause. "I don't." This is not a guilt trip. This is character voice. +The character knows they left something unexamined. The player decides whether they +care. + +--- + +## 5. Tension and Stakes + +The project lead said: what can go wrong? Let me map the failure states. + +### Failure States at Abzu + +Abzu has no fail conditions in the conventional sense. You cannot die here (there is +nothing to fight). You cannot be arrested (the community has no enforcement structure). +You cannot miss a quest deadline (there are no quests). + +The failure states are informational, not mechanical. They are all states where the +player leaves with less understanding than they could have had. + +| Failure state | How it happens | What the player loses | +|---------------|----------------|----------------------| +| **Filing too early** | Impatience; efficient-optimization instinct | Entry quality; the community's tier-4 knowledge; the Recognition event | +| **Missing the recognition** | Not being at the watch zone at Elevated tier when the storyteller triggers it | One of the game's most significant perceptual events | +| **Not finding the watch zone** | The settlement's disorienting layout | Entire watch mechanic; entry is tier-1 data only | +| **Missing the non-human shift change** | Not being present at the right time OR having investment < 80 | The physical evidence that something non-human shares the vigil | +| **Leaving before the founding record unlocks** | Investment < 60 when the player departs | Cannot access the archive; the founding perceptual event is unknowable | +| **Overstaying past the leave window** | Staying too long... | Not a failure state. This is integration. This is the other ending. | + +### The Implicit Stakes: The Entry's Reach-Wide Consequences + +The entry propagates. This is the medium-term consequence structure. + +If the player files a tier-1 entry: +- The Reach's shared understanding of Abzu remains at tier-1 common knowledge +- The Veil Institute's file on Abzu does not gain external pressure +- The third correspondent continues to be listed as "active at GJ 6711" +- Other players (or the same player on a second playthrough) will find an entry that + reads like the first correspondent's, and will arrive at Abzu without useful preparation + +If the player files a tier-3 or tier-4 entry: +- The Reach's shared understanding shifts +- The Veil Institute's paralysis is stressed — the entry is now public record that + something anomalous exists at Abzu, which neither faction can ignore +- The Adams & Ford database has an entry that reads like someone who was changed by + what they experienced +- Subsequent visitors arrive primed differently + +These consequences are narrative/world-state, not gameplay-punishing. But they are +real. The entry the player files is permanent. It matters. + +### What Happens If the Player Ignores the Vigil Entirely and Tries to Force Answers + +A player who investigates aggressively — using all available perception modes, accessing +every Meridian record, pursuing every conversation to exhaustion — will find: + +- Every conversation eventually reaches a wall. Not a hostile wall. A wall made of + the limits of what can be explained to someone who hasn't stayed. The community isn't + hiding information. They are the answer, and the answer requires time. +- The four frames (astronomical, geological, perceptual, topological) can all be + partially confirmed through investigation alone. None of them resolve. Each one + produces more questions than it answers. +- Elevated tier investigation without watch investment produces the perception events + but without the monologue context that gives them meaning. The player sees the fog + inversion. The monologue says: "Something's wrong with my perception system." No + further interpretation. The Recognition Event is registered but not understood. + +This is the "interesting complex vs. annoying complex" question. Is it annoying that +investigation alone can't crack Abzu? My position: no, because the game has been +training the player to investigate for 23 hops. When investigation hits its limit at +Abzu, the player knows what they're experiencing. It's not a puzzle with a missing +piece. It's the correct experience of a place that resists the investigation framework. +The monologue names this directly at high investigation-without-watch states: "I've +looked at everything here. I still don't know what I'm looking at." + +--- + +## 6. The Decision to Stay or Leave + +This is the endgame mechanic. Everything else feeds into it. + +### The Decision Surface + +The decision to stay or leave is not presented as a choice. There is no dialogue option +"Do you want to stay?" There is no achievement. There is no conversation with an NPC +who says "you should stay." The decision is expressed entirely through player behavior: +do they walk to the gate? + +What the player has accumulated by the time they face this decision: + +**Investment in the watch:** +At high investment, the player has taken multiple shifts. They have a regular position +at the watch zone. Community members acknowledge their presence without comment. Their +monologue has shifted register — from visitor-observing to something more like +resident-understanding. The player has, functionally, been keeping watch. + +**The Adams & Ford entry:** +The entry is either filed (player has completed their commission) or unfiled (player +hasn't yet). If unfiled and investment is high, the monologue flags the tension: "I +could write the entry now. I could write it better. I don't know if I want to." + +**The personal investment (varies by playstyle hook):** +- Tycoon: they found the one thing money can't buy; do they try to replicate it elsewhere? +- Relational: they found the person they came for; but is the person they found someone + they want to leave with? +- Political: they have enough information to weaponize if they're willing to; are they? +- Investigation: they have the best possible entry; do they know what it means that + they can't fully explain what they experienced? + +### The Mechanical Expression of the Choice + +**The gate is always accessible.** The player can leave at any time. The game does not +lock them in. The community does not prevent them. No NPC stands in front of the gate. + +What changes based on watch investment is the monologue that fires when the player +approaches the gate to leave: + +| Investment | Monologue at gate | Subtext | +|------------|-------------------|---------| +| < 20 | "That was interesting. Unusual system. I have what I need." | Clean departure. No pull. | +| 20-40 | "I got what I came for. I should feel satisfied." Pause. "I don't." | First hook. Player must decide if they care. | +| 40-60 | "There's a shift tomorrow morning. I could take it. I don't have to." | The watch is named directly as the pull. | +| 60-80 | "Three hundred years. They built a community around this. I've been here [X] days and I think I'm starting to understand why." | Integration approaching. The game does not push. | +| 80+ | "I could file the entry and leave. The entry I'd file now isn't the same entry I would have filed when I arrived. I don't know what that means." Pause. "I think it means I have to decide." | The game is honest: this is a decision, not a drift. | +| 100 | "I'm not leaving. I don't think I was going to." | Integration complete. Player may still leave — but the character knows something has changed. | + +**If the player leaves at any investment level, that is a valid ending.** + +The game does not punish departure. The monologue accepts it. The entry the player files +(if they haven't already) reflects their investment level. They carry the experience +into the rest of the game — or the rest of the Reach, depending on where they go. + +**If the player stays:** + +Investment 80+ and choosing not to depart after the final monologue triggers a +mechanical state change: the player character is now part of the shift schedule as a +regular watcher. Not via a cutscene. Not via a dialogue confirmation. The shift +schedule NPC data updates. The player's watch position is assigned. The community +treats them as they treat any watcher: with matter-of-fact acknowledgment. + +The game continues. There is still content — conversations, archive access, further +perception events. But the character has made a choice that is functionally the same +as what the third correspondent made. The Adams & Ford entry goes unfiled unless the +player files it. + +The player can still leave. They can always leave. But leaving now fires a different +monologue: "I stayed. I watched. I know what I was watching for now. Not what it is. +What watching it requires." And then the gate. + +--- + +## 7. Integration with Existing Systems + +Let me map every Abzu mechanic to the systems that must support it. + +### Perception Tier System (D-017, D-019) + +**Baseline:** Sees the architectural evidence (taller doors), the Mode 1 construction, +the threshold markings. Gets full monologue commentary. Can access all watch shift +mechanics. Experiences fog-expansion events. Does NOT experience Recognition Event. +Does NOT see the thermal signature of the non-human shift-takers. + +**Augmented:** Above, plus — richer audio during shifts (the hum frequency shifts are +distinguishable as a pattern, not just a texture). During the Recognition Event: the +fog inversion is more pronounced and lasts longer. The monologue has more specific +vocabulary for what is perceived. + +**Elevated:** Above, plus — the Recognition Event includes the thermal signature at +the thinness boundary. The shift-taker thermal presence (present, then not, without +transition). The monologue fires with the highest-specificity interpretation: "That was +attention. Something paid attention to me." AND: at investment 80+, a secondary event +fires during a shift where the fog quality at the thinness becomes briefly coherent — +not a shape, not a face, but the quality of a direction. Something is oriented toward +the watch zone. The monologue: "I don't have a word for what I'm looking at. The watch +position is named that for a reason." + +**Tier-scaling design principle:** Every tier sees the same system. Higher tiers see +more of the same system. No tier unlocks a "truth" that lower tiers cannot access — +they just have sharper instruments for reading the same phenomenon. This preserves +the non-resolution principle while rewarding perception investment. + +### Fog-of-War System (D-011, D-035) + +Abzu requires two extensions to the standard fog system: + +1. **Threshold-adjacent tile classification:** A tile type that uses the reflected-light + palette rather than the primary-light palette. No new fog state — the tile is "seen" + normally. The difference is purely in lighting values. This is a zone property, not + a fog property. The fog shader reads it from the tile's zone tag. + +2. **Fog-inversion event:** A one-off trigger that can briefly reverse the direction of + the fog gradient near the thinness. Mechanically: for a specified window, the + thinness-boundary tiles are rendered with the fog shader in "inward" mode (the opacity + gradient is highest at the center of the thinness zone, fading toward the player's + position rather than the reverse). This is a client-side render effect triggered by + a server event. The event is storyteller-driven. It does not affect actual LOS + calculation — only the visual representation of the fog boundary. + + Concern: Does D-045 (environmental neutrality / strict zero shift) apply here? + Ruling: No. D-045 prohibits world-layer changes triggered by narrative state + (conspiracy activation, investigation progress). The fog-inversion is a diegetic + physical event — the thinness is actually doing something, and the fog system is + representing it accurately. It is more like weather (which D-045 explicitly permits) + than like the narrative-state visual shifts D-045 prohibits. + +### Internal Monologue (D-016) + +The monologue is the primary delivery system for all of Abzu's perceptual content. +Almost every mechanic described above triggers a monologue event. + +**Abzu-specific monologue registers:** + +| Register | Trigger condition | Tone | +|---------|-------------------|------| +| Visitor | Investment < 20 | Professional, observational, slightly flat | +| Noticing | Investment 20-40 | Quietly puzzled; the character knows something is different but doesn't have vocabulary | +| Settling | Investment 40-60 | Tentative; the character is building a framework that keeps not closing | +| Understanding-approaching | Investment 60-80 | The framework is abandoned; the character is reporting experience instead of building categories | +| Integration | Investment 80+ | Plain. No metaphor. The character describes what they see without interpretation because interpretation is no longer what the situation requires. | + +**The monologue register shift is the primary feedback loop.** The player knows their +investment is increasing not from a counter or a progress bar but from noticing that +the character's interior voice has changed. This is the correct feedback mechanism for +a location that resists gamification. + +**Key monologue events (non-negotiable, these must ship):** + +- First approach to watch zone (any investment): "These were built this size deliberately. + Someone decided this was the right size." (The taller doors. No elaboration.) +- First fog-expansion event: "I've been here. I know this place. Why does this look + like I've never seen it?" +- First non-human shift indicator (Augmented+): "I was wrong about something. I don't + know what yet." +- Recognition Event (Elevated): "That was attention. Something paid attention to me." +- Gate approach monologue: investment-scaled (see Section 6 table) +- Filing the entry: always fires at entry submission. Register matches investment level. + High investment: "I don't know if this helps anyone. I know it's accurate." + +**Monologue as unreliable narrator (D-016):** At low investment, the monologue can +be confidently wrong. "The shift schedule seems like a kind of communal ritual — +probably cultural significance from the founding era." The player learns this +interpretation is insufficient as investment increases. The monologue never announces +that it was wrong. The player compares early and late entries. + +### Storyteller / Rimworld-style Event System (D-005 referenced in Round 14) + +The storyteller's role at Abzu is to pace the bleed events and manage the recognition +event timing. Specific parameters: + +**Events per playthrough:** +- Fog expansion: 1-2 (triggered by watch abstention + minimum day threshold) +- Overlap failure: 0-1 (triggered by player leaving before overlap window; only once, + to avoid annoyance) +- Recognition: 0-1 (triggered by investment ≥ 60 AND Augmented+ AND being present + during a watch shift — the storyteller waits for the right moment) +- Non-human shift indicator: 0-1 (investment ≥ 80 AND present at shift change timing) + +**Storyteller escalation principle:** Unlike other systems in the game, the storyteller +at Abzu does NOT escalate tension over time. It de-escalates. The longer the player +stays, the quieter the events become. Early visits feel stranger. Long stays feel +settled. This inverts the normal storyteller pattern (build to crisis) and it is +intentional: Abzu's drama is internal, not external. + +**The storyteller knows the stay/leave state.** If the player has been at Abzu for +more than 20 game days without departing, the storyteller flags this as a potential +"staying" arc and ensures the non-human shift indicator event fires before the player +departs. Every player who stays long enough sees this. It is the payoff for staying. + +### Information Asymmetry — The Master Mechanic + +Let me break down what the player knows vs. doesn't know at each phase of Abzu. + +**What the player can know (knowable with effort):** +- The community keeps a continuous watch schedule (observable) +- The schedule has run for 300 years (tier-2 community knowledge) +- Three Adams & Ford correspondents preceded the player (tier-2 specialist knowledge) +- The founding structures are over-built for actual conditions (observable) +- The doors are taller than standard (observable; monologue flags) +- The Veil Institute has a classified file on this system (Meridian record, partial) +- Something about the light is different (observable once the player notices) + +**What the player can accumulate but not resolve:** +- What is being watched +- Whether the non-human shift-takers are Builders, Threshold entities, or something else +- Whether the founding settlers understood what they were starting +- What would happen if the vigil failed at scale +- Whether the high-bleed gates in the rest of the Reach are connected + +**What the player cannot access, ever:** +- The community's tier-4 knowledge (the full understanding) — this cannot be transmitted. + Not because it is withheld. Because it requires staying. The player who stays long + enough approaches it but cannot close on it. This is correct. Miri's phrase: "you + either understand or you don't. Understanding comes from staying." +- Direct evidence of what takes the other shifts. The doors are physical evidence. + The thermal signature (Elevated only) is perception-scaled ambiguity. The player + never sees the shift-takers. +- Confirmation of the high-bleed connection. The monologue at high investment and + Elevated tier can gesture toward it. The game never confirms it. The player + who arrives at the connection independently has understood something true. + +**The asymmetric information structure IS the Abzu design.** Every other location in +the game gives the player information that resolves into action. Abzu gives the player +information that resolves into presence. The detective framework is preserved (gather, +evaluate, interpret) but the output is not an action. It is a state. + +--- + +## 8. Systems That Need to Interact: The Emergent Mechanic Map + +Let me map the interactions I'm most interested in — the places where systems +colliding might produce stories the designers didn't anticipate. + +| System A | System B | Interaction | Emergent story | +|----------|----------|-------------|----------------| +| Watch investment | Entry filing | Player files at investment 40; returns on second playthrough and recognizes the entry as insufficient | "I wrote this. I was wrong." | +| High-bleed gates (experienced earlier) | Recognition Event (Elevated) | Player transits a high-bleed gate on approach to Abzu; at Abzu's Recognition Event, the monologue connects the felt quality | "That's what the gates were doing. This is what it looks like from the source." | +| Unbound character (no re-embodiment) | Watch investment 80+ | Player is Unbound and has reached near-integration; death here is permanent; the player must decide if the vigil is worth it | Nigel's darkest implication made mechanical | +| Correspondent variant (Nigel's seed) | Watch mechanic | Variant C: the third correspondent is integrated and no longer identifies as one; player discovers this by watching with them | "They stayed. Now I'm watching with them. I understand now what staying meant." | +| Relational playstyle hook | Stay/leave | The person the player came for has reached integration; leaving them is leaving them permanently | "Do I stay for them? Or because they're why I understand what staying means?" | +| Political playstyle hook | Entry filing | Player has enough for leverage; they must choose between the accurate entry and the strategically useful one | The only real moral choice at Abzu is about the entry | + +--- + +## 9. What I Would Cut, and Why + +Good design requires scope discipline. Not every mechanic I've described above should +ship on the first pass. Here's my priority ranking: + +**Must ship (Abzu doesn't work without these):** +1. The watch zone as a navigable location (the disorienting layout, the shift schedule) +2. The watch investment counter (invisible, but drives everything) +3. The threshold-adjacent tile lighting zone +4. The entry documentation system (field notes → filing → propagation) +5. The gate departure monologue (investment-scaled) +6. Fog-expansion bleed event (the core "what bleed looks like" expression) + +**Should ship (makes the system rich):** +7. The Recognition Event (Elevated tier; the signature experience of Abzu) +8. The monologue register shift system (the feedback loop for investment) +9. Per-shift documentation with investment-scaled note content +10. Entry propagation to Reach-wide Meridian record + +**Can defer (depth content, not structural):** +11. Founding record archive unlock (investment 60+) +12. Non-human shift indicator thermal event (Elevated 80+) +13. Correspondent interaction variants (seed-dependent) +14. Per-playstyle hooks (the investment hooks for tycoon, political, relational paths) + +**Cut or redesign:** +- Any visual effect that announces bleed dramatically. If bleed looks like a horror + game event, it breaks the tone. The fog-expansion event should be subtle enough + that some players miss it. That is the correct experience. +- Any dialogue option that lets an NPC explain the vigil. They cannot. The game + should not simulate this as a dialogue option that fails. It should simply not + be an option. The community's warmth without explanation is mechanical: they + don't have a conversation topic for "what are you watching." + +--- + +## Summary: The Mechanical Contract with the Player + +Abzu asks the player to do something the game has not asked before: be present without +optimizing. + +The player's toolkit — investigation, information gathering, social manipulation, economic +leverage — all works at Abzu, but none of it produces the main thing. The main thing +requires staying and watching. The game does not explain this until the player is already +experiencing it. + +The watch mechanic translates the vigil into a player experience that is simple in its +rules (be here, during this window, long enough) and complex in its effects (monologue +register shift, tier-scaled perception events, community relationship deepening, entry +quality accumulation). + +The Adams & Ford entry is the decision surface: when to file, what to include, what +register to file in. It is the only irreversible choice at Abzu, and what it communicates +to the rest of the Reach is the permanent record of what the player understood. + +The stay/leave decision is not a choice the game presents. It is a choice the player +makes through behavior. The game's job is to make sure the player knows, when they +approach the gate, exactly what they are choosing to leave. + +The game has been teaching the player to look. Abzu is where looking was never +the point. Being present was. Every mechanic above is designed to produce that +recognition — not announce it.