Files
settled-reach/docs/workshops/gj-6711-furthest-system/carryout-gestalt.md
T
jpmschweitzerandClaude Opus 4.6 53a0e3f6b5 docs(workshops): add Abzu carry-out proposals (unresolved)
Round 6: four agents responded to the project lead's challenge
"what do you walk away with?" Gore proposed Threshold Attunement
and Attend verb (too philosophical, not literal enough). Gestalt
proposed vigil_vocabulary flag and Establish Watch verb. Nigel
proposed cross-playthrough WATCHER persistence flag. Ozzie
proposed door-measuring as retroactive evidence reading (thin
but visceral). Lead verdict: "too much philosophy too little
lootbox" — parking this for later. The reward design is TBD.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-16 00:51:31 +01:00

23 KiB

Abzu — Mechanical Carryout

Role: Systems Designer (Gestalt) Date: 2026-03-16 Workshop: GJ 6711 — Furthest System In response to: Project lead challenge — "What do you walk away with?"


The Problem, Stated Precisely

Let me break down what this actually means mechanically. The lead's challenge is that every mechanic in the original design resolves inward. The watch investment counter drives what the player becomes at Abzu. The monologue register shifts describe what the character understands. The fog inversion is what the player experiences. The stay/leave decision expresses what the player chooses.

None of these are verbs the rest of the game can see.

This is not a tonal failure. The Abzu design does what it's supposed to do: it produces the internal experience of vigil. The problem is that if Abzu is 23 hops from the starting gate, the player has been building a toolkit for 22 hops and then spends 20 in-game days at a location where that toolkit produces nothing exportable. The experience is beautiful. But when they walk back through the gate, they're carrying a memory, not a capability. And the game cannot tell the difference between a player who was deeply moved and a player who went there and left in 3 days.

That distinction needs to be mechanically legible. Not announced — legible.


What Abzu Actually Teaches, Mechanically

Before I propose carry-out mechanics, let me map what the player learned at Abzu that the game could plausibly convert into capability. These are the actual informational outputs of the Abzu experience:

What the player learned How they learned it What it implies
Bleed is vigil failure The fog expansion events; the overlap failure event; the shift schedule; the founding record High-bleed gates are not environmental weirdness — they are a signal with a cause
The thinness has a perceptual signature The fog oscillation; the cool-silver tile state; the inward fog gradient at the Recognition Event This signature exists elsewhere in the gate network — it just hasn't been identified
Watching is a load-bearing verb 300 years; the shift overlap; the community's matter-of-fact accommodation Sustained presence at a threshold can do something. The community did not accidentally discover this.
The community has something nobody in the Reach can buy Zero factional debt; 300 years of institutional continuity; no Meridian capture Trust with this community is the only access to this knowledge structure
The Adams & Ford entry is now in the Reach The filing mechanic It propagates. Other actors will respond to it.

Every carry-out mechanic I'll propose flows directly from this table. Nothing invented. Only the implications of what the player already experienced.


The Four Carry-Out Mechanics

1. Perceptual Vocabulary: High-Bleed Gates Read Differently

The problem it solves: Before Abzu, the player transiting a high-bleed gate receives the fog inversion — the sensation that something is looking at them through their own perception system. The monologue fires something vague: "Something feels wrong with this transit. Like being noticed." The player has no framework for this. It's ambient weirdness.

After Abzu, the player has the framework. They experienced the Recognition Event. They watched the fog inversion happen at the thinness boundary, at close range, with full context. They know — not in the abstract, but as an experienced fact — what the inward fog gradient means.

The mechanical change: A vigil_vocabulary flag is set on the player character when watch investment reaches 60 (the "settling" threshold) AND the player has experienced either the Recognition Event or the Fog Expansion event. This flag is permanent. It does not reset between sessions. It does not require the player to stay. It requires the player to have genuinely engaged with Abzu — not to have maximized a counter.

With vigil_vocabulary active:

Context Without flag With flag
High-bleed gate transit "Something feels wrong with this transit. Like being noticed." "This gate's vigil is degraded. Something that should be held back is looking through. I know what this is now."
Moderate-bleed gate transit No monologue trigger "Less stable than the last time I was here. Or I'm reading it better."
Stable gate transit No monologue trigger No monologue trigger (no false positives; the flag only fires when there's signal)
First high-bleed transit after Abzu — Longer monologue: "That's it. That's the same quality. The community at Abzu has been sitting one meter from this their entire lives. Everywhere else in the Reach, we're just... transiting through it."

What this means for player decisions: The player now has information the Veil Institute doesn't have a vocabulary for. Every high-bleed gate they encounter is now a data point that means something. They can build a mental map of which gate chains have degraded vigils. They can start asking: why are these gates high-bleed? When did they become high-bleed? Who used to watch here?

The investigation playstyle now has a new thread that can run through the rest of the game.

Implementation note: vigil_vocabulary is a component on the player entity, set by the server. The monologue system checks this component when composing transit monologue events. No new HUD element. No achievement. No announcement. The player notices when the transit monologue changes register.


2. The Vigil Verb: Establishing a Watch

The problem it solves: The player now understands that watching is load-bearing. The high-bleed/vigil-failure connection (Nigel's Formal Corollary 3) is in the sealed envelope. Before Abzu, the player had no reason to sit and watch anything. After Abzu, they have both the understanding and the experience to know that presence at a threshold has effects.

The new verb: At a high-bleed gate — specifically, within the gate's immediate area, which has threshold-adjacent tile properties similar to Abzu's watch zone — the player can now perform Establish Watch. This action is not available to players without vigil_vocabulary. It does not appear in the interaction options for players who haven't been to Abzu and reached the settling threshold.

Before this verb existed for the player, they could stand near a high-bleed gate and feel vaguely uneasy. Now they can do something.

What the verb does, mechanically:

The Establish Watch verb initiates a watch session at a high-bleed gate. The mechanics are structurally identical to the Abzu watch mechanic, with three differences:

Parameter Abzu High-bleed gate
Community to relieve you Yes — 4,000 people, continuous schedule No — you watch alone unless you've built relationships at this node
Effect speed Immediate stability (vigil is maintained, not building) Extremely slow — single watcher, decades-degraded vigil
Feedback Community's matter-of-fact acknowledgment; monologue register shifts Monologue only; the gate doesn't acknowledge you
Sustainable? Yes (the community exists for this) No — a single watcher cannot stabilize a failing vigil permanently

The player cannot stabilize a high-bleed gate alone. One watcher is not 4,000 watchers across 300 years. What they can do is slow the degradation. The bleed level at a gate where the player has watched for a full game day will be measurably lower — not enough to change the transit experience dramatically, but enough that the monologue notices: "It's quieter than yesterday. Not quiet. Quieter. That's something."

Why this creates interesting decisions:

The player is now in the same position as the Abzu founding settlers — they found something that requires watching and they are one person. The question this raises: who else can watch? This is where the Abzu community trust (Mechanic 4) becomes mechanically connected. The player who maintained high watch investment at Abzu and has community trust can bring the problem back to them. They have the only people in the Reach who know how to do this.

The verb also creates a decision surface around time. Watching costs time. The player is in a game where every hop costs resources and time has opportunity cost. Choosing to watch a high-bleed gate is choosing not to do something else. That is a real decision. It is interesting because both options have genuine value.

Implementation note: This is a new interaction option that appears contextually. The server checks vigil_vocabulary AND proximity to a threshold-adjacent tile zone at a high-bleed gate. The option is silent — it does not explain itself. Players who haven't been to Abzu never see it and have no reason to know it exists.


3. The Entry as Pressure Instrument

The problem it solves: The Adams & Ford entry currently propagates into the Reach as a record. The original mechanics design described this as a world-state change: the authoritative A&F record for GJ 6711 shifts based on what the player filed. But "the Veil Institute's paralysis is stressed" was left unconnected to player action. Stressed how? Does anything respond? Can the player act on the stress?

What a high-investment entry actually does:

The filed entry is in the public Meridian database. It describes — in the character's actual register, at their actual investment level — what GJ 6711 is. A tier-1 entry reads like the first correspondent's. A tier-4+ entry reads like someone who has been to a place that recategorized them.

A tier-4+ entry does something the Institute's locked file cannot do: it is public. It uses the Adams & Ford credentialing system, which has 400 years of scientific authority. It describes anomalous phenomena at GJ 6711 in terms that any Institute researcher will recognize as significant. And it cannot be suppressed — it's already in the A&F database. The Institute can classify their own file, but they cannot classify the published entry of an independent correspondent.

The mechanical consequence: A tier-4+ entry creates an institute_pressure world state flag. This flag activates:

  • An Institute faction contact becomes available to the player — one of the two conflicting factions now has a reason to reach out. The faction that wants to act has new leverage: there's a published entry that confirms what they've been arguing. They need to move before the other faction suppresses the conversation. The player gets a message.
  • The second correspondent's entry is re-examined. If the player finds both entries and has vigil_vocabulary, the monologue fires: "She saw what I saw. She didn't have the words for it either. She filed what she could. The Institute filed it as inconclusive."
  • At high-level political access: the player can now use the entry as leverage. "You have a classified file on this system. I have a published entry. We both know what we're describing. What would you like to do about that?" This is a conversation that cannot happen without the entry.

The tier-3 entry variant (partial): A tier-3 entry does not trigger full institute pressure, but it does something more subtle: it creates a research query in the A&F database that surfaces when any other character searches for GJ 6711. The third correspondent's placeholder (assigned, never filed) is now next to the player's entry. Anyone who notices the gap will investigate. The player has made the absence of the third correspondent visible.

Why tier-1 entries are still valid: A tier-1 entry does not trigger this chain. The player who filed early and left cleanly completed their commission. The Reach's understanding of Abzu stays at tier-1. The Institute's file stays locked. The third correspondent stays "active at GJ 6711" in the database. Nothing is punished. Everything is different.

Implementation note: The institute_pressure flag is set by the server when the A&F entry is submitted with content above a tier threshold. The exact tier cutoff is a tuning decision — probably tier-4 (watch investment 60+) to require genuine engagement, not just moderate investment. The faction contact message fires within one game day of filing, not immediately — the Institute reads the database, they don't watch it in real time.


4. Abzu Community Trust as Live Asset

The problem it solves: If the player reached high watch investment and was added to the shift schedule, the community trusts them. This is currently a satisfying local fact. It needs to be a live asset in the rest of the game.

What the Abzu community actually is, mechanically:

The community at Abzu has properties no other faction in the Reach possesses:

  • Zero factional debt (300 years of refusing to be captured)
  • Institutional continuity (every other institution in the Reach has been founded, split, reformed, and captured at least once; Abzu has not)
  • Direct operational knowledge of vigil mechanics — the only knowledge in the Reach that cannot be transmitted without staying
  • Willingness to help, on their terms, for purposes aligned with the vigil's health

These properties are worth something to every playstyle:

  • Tycoon: a politically uncaptured node with 300 years of trust equity is worth more than any commercial relationship in the Reach
  • Relational: these are people who understand commitment that doesn't resolve
  • Political: a faction that owes nothing to anyone is the most credible neutral party in the Reach
  • Investigation: the only living witnesses to the founding era who were there from the beginning

The mechanical expression of trust:

If watch investment was 80+ when the player departed, the Abzu community is flagged as a trusted contact network for the player character. This has three concrete effects:

Effect 1 — Intelligence about high-bleed events. The community keeps track of the vigil network because their vigil is connected to it. They do not advertise this. But a player who has their trust will, occasionally, receive a message: not an alert, not a notification — a brief note, the kind one watcher sends another. "We've noticed increased activity at the GJ-4402 boundary. Thought you should know." The player receives early warning on high-bleed escalations that the Institute does not have. This is not a game-breaking information advantage. It is the kind of subtle edge that changes decisions at the margin — which is exactly what asymmetric information should do.

Effect 2 — Recruitment support for vigil establishment. If the player is attempting to establish a watch at a high-bleed gate (Mechanic 2), and they have Abzu community trust, they can send word back to Abzu. The community can advise — they cannot come, their vigil requires their presence — but they can provide the accumulated knowledge of 300 years of practice. What this means mechanically: the watch investment counter at the new gate accumulates faster when the player has community guidance. Not dramatically faster — the vigil still requires time — but the guidance prunes the learning curve. The player is not rediscovering what the Abzu founding settlers spent a generation figuring out.

Effect 3 — The third correspondent. If the correspondent seed determines that the third correspondent is still at Abzu (the default/canonical seed), then a player who reached integration-level trust is now in relationship with the third correspondent. The third correspondent is still listed as "active" in the A&F database — their entry was never filed. The player knows why. They have a choice: file on the correspondent's behalf, noting their integration into the community; leave the placeholder in the database; or do nothing. Each option has downstream effects.

The trust is not transferable. The player cannot leverage Abzu community trust in political negotiations as "I know the people at Abzu." The community's value is not as a chip to be played. A player who tries to use the relationship instrumentally will find that the community stops responding. The intelligence stops. The notes stop. The community did not join the Reach's factional economy. A player who treats their trust as currency will lose it.

This is a mechanical expression of the vigil's design. The place resists the normal game toolkit. So does the trust the place generates.


Interaction Map: How the Four Connect

Let me break down what this actually means for the full systemic picture.

ABZU EXPERIENCE
     |
     +-- vigil_vocabulary (flag, permanent)
     |        |
     |        +-- High-bleed transit monologue changes register
     |        |   -> Player builds mental map of gate network health
     |        |   -> Investigation thread unlocks
     |        |
     |        +-- Establish Watch verb becomes available
     |                 |
     |                 +-- Costs time (real decision)
     |                 +-- Slow stabilization (can't do it alone)
     |                 +-- Connects to community trust (recruitment)
     |
     +-- adams_ford_entry (permanent, tier-stamped)
     |        |
     |        +-- Tier 1-3: record only; world state unchanged
     |        |
     |        +-- Tier 4+: institute_pressure flag
     |                 |
     |                 +-- Faction contact available (political thread)
     |                 +-- Entry as leverage in Institute negotiations
     |                 +-- Second correspondent's entry re-examined
     |
     +-- abzu_community_trust (conditional on investment 80+)
              |
              +-- Early warning on high-bleed escalation
              +-- Vigil establishment guidance (faster accumulation)
              +-- Third correspondent relationship (A&F entry decision)
              +-- Loses on instrumental use (designed)

The most interesting intersection: a player who has all three (vigil_vocabulary, tier-4+ entry, community trust) can now do something no other actor in the Reach can do. They can identify degraded vigils, understand what the degradation means, have the early warning system to catch escalation, have the operational knowledge to establish a watch, and have the political leverage to force the Institute to acknowledge what they're sitting on top of.

That is a player who went to Abzu and understood it. The game should feel different in their hands. Not because they got a power upgrade — none of the four mechanics above make combat easier, make the player richer, or unlock shortcuts. They give the player a framework that changes what the information they receive means.

The asymmetric information is the master mechanic. Post-Abzu, the player is now asymmetrically informed in the correct direction. Before Abzu: the player is one of many people who transits high-bleed gates without knowing what they mean. After Abzu: the player knows what they mean. Nobody else in the game — not the Institute, not any faction, not any NPC — has that knowledge operationally. The community at Abzu has it. And the player.


What This Requires From Other Systems

Honesty about implementation dependencies:

Carry-out mechanic Systems required New systems needed Complexity
vigil_vocabulary + monologue register Monologue system (D-016); permanent character flags Character flag persistence across sessions Low — monologue system already handles state-conditional lines
Establish Watch verb Interaction system; threshold-adjacent tile classification; watch investment counter (already designed) Context-sensitive interaction gating Medium — the watch mechanic is already designed; this is gating + new location
institute_pressure + faction contact Entry filing system; faction state; message system Entry tier tracking; deferred message trigger Medium — depends on faction contact system being implemented
Community trust effects Message system; watch investment persistence; A&F database state Contact network as data structure; trust-on-instrumental-use detection Medium-High — the trust-loss-on-instrumental-use mechanic is new and requires careful design

Nothing above requires new engine work. All of it uses existing or planned systems. The most complex is the community trust mechanic's instrumental-use detection — but the detection doesn't need to be clever. The community stops responding when the player uses the trust explicitly as currency in a negotiation. That's a clean trigger condition, not a fuzzy AI problem.


Priority Ranking: What Ships First

If all four cannot ship simultaneously, here is my triage:

Ship with Abzu:

  1. vigil_vocabulary flag + high-bleed transit monologue change. This is the minimum viable carryout. A player who left Abzu and never encounters another high-bleed gate might not notice it. A player who does will. The cost is low. The effect is exactly right.

Ship when faction systems exist: 2. institute_pressure + entry tier tracking + faction contact message. This is the highest political drama payoff and is the correct time to ship because it needs the faction contact system to be operational.

Ship when the gate network has high-bleed gates as designed locations: 3. The Establish Watch verb. This mechanic is hollow without real high-bleed gates that have threshold-adjacent tile zones. Once those locations exist, the verb is structurally identical to the Abzu watch mechanic — it reuses that whole system. This is not new work; it is scope.

Ship when the Abzu community trust is functional: 4. The community trust effects. This requires the contact network system and the instrumental-use detection to be designed. It is the richest of the four but the most dependent on other systems maturing.


The Answer to the Lead's Question

"What do you walk away with?"

The player walks away from Abzu with the vocabulary to read the gate network.

Before Abzu: the Reach's gate network is infrastructure. Transit is transit. High-bleed gates are unpleasant and anomalous but uninterpretable.

After Abzu: every high-bleed gate the player encounters is a question. What happened to the vigil here? When did it start degrading? Is anyone watching? The player is no longer transiting through an infrastructure system. They are moving through a network of maintained and unmaintained boundaries, and they are the only person in the Reach who can read which is which.

That is not understanding in the abstract. That is a new relationship with the game's entire geography. The map the player has been building for 22 hops has just been reinterpreted. Not because new information was added to it — because the player now has the category to sort what was already there.

The carry-out is not a power. It is a lens. The game looks different through it. The player who has it will notice things. The player who doesn't will transit through the same gates and feel vaguely uneasy and never know why.

That is the correct gap between those two players. And now the game can express it mechanically.