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>
This commit is contained in:
2026-03-16 00:51:31 +01:00
co-authored by Claude Opus 4.6
parent c8cead39f3
commit 53a0e3f6b5
4 changed files with 1376 additions and 0 deletions
@@ -0,0 +1,413 @@
# 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.
@@ -0,0 +1,398 @@
# What Abzu Does to the Player — Carryout Mechanics
**Role:** Themes & Endgame Design (Gore)
**Date:** 2026-03-16
**Workshop:** GJ 6711 — Furthest System
---
## Prefatory Note
You're missing the real question.
The team has been asking "what does the player take from Abzu?" — treating it as an
extraction problem, a question of inventory. What item, what flag, what faction
relationship leaves the system with the player?
The real question is: **what kind of player leaves Abzu?**
Not what they carry. Who they became.
Abzu is the game's first encounter with the Interstitium not as transit medium but as
presence. The player who has watched long enough has had their perceptual apparatus run
against something that is not designed for human perceptual apparatus to run against.
That leaves a mark. The mark is mechanical.
What follows is not atmosphere. It is a specification of what changes about how the game
functions after Abzu.
---
## 1. The Interstitium Becomes Legible
This is the load-bearing carryout mechanic. Everything else is downstream of it.
### The Problem It Solves
Currently, the Interstitium is experienced as transit noise — degraded perception, bleed
artifacts, the sense of being observed during high-bleed transits. It is texture. It is
not information. The player transits through it the way they breathe: necessary, not
examined.
Abzu is where the Interstitium stops being texture and starts being signal. The boundary
condition the player has been watching for days or weeks is the Interstitium from one
meter away, from the stable side. When they depart — when the gate spins up and the
transit begins — the liminal state is not a disruption to perception. It is a continuation
of what the watch zone was already producing.
The monologue fires once, during the departure transit: "I've been in transit a hundred
times. I never noticed that there's a shape to it."
Not a specific shape. Not a face, not a signal. A quality. Something that was always
present in every transit and was not legible until the player had spent time at a place
where the same quality is the dominant condition rather than the transit noise.
This is not a revelation. It is a recalibration.
### The Mechanical Expression
**Permanent perceptual state change: TRANSIT SENSITIVITY.**
After departing Abzu, the player's transit experience is permanently altered. The specific
changes:
**At normal gates:**
- Transit duration is subjectively extended slightly (not mechanically extended — the fog
effect lingers a half-second longer)
- The monologue has new material available during transits: observations about the quality
of the space, comparisons to the watch zone, fragments that cannot be completed
- The player can now "document" during transit (the field notes verb becomes available for
a brief window). Notes taken in transit have a distinct classification: THRESHOLD DATA.
They cannot be interpreted at the time. They accumulate.
**At high-bleed gates:**
- The fog inversion behavior (the "something looking at you" effect) is now experienced
differently. Before Abzu, it is anomaly. After Abzu, it is recognition. The monologue
fires with specificity: "Weak vigil. Something here isn't being watched well enough."
The player does not know what. They know the quality.
- THRESHOLD DATA notes from high-bleed transits are richer, more specific. They still
cannot be interpreted in isolation. They accumulate toward a pattern.
- At high enough perception tier (Elevated, post-Abzu), the player can begin triangulating:
which systems along a gate chain have this quality? The Institute has been measuring the
symptom. The player can start to build a map of the cause.
**The pattern completion mechanic:**
Accumulated THRESHOLD DATA — from the departure transit, from high-bleed transits, from
subsequent watch-adjacent situations — can reach a threshold where the player's monologue
generates an entry: a private synthesis that draws the map. Not the full map. Enough of
it to know what they are looking at.
This is the game's longest information arc. It begins at Abzu. It completes — for players
who pursue it — at some final act location that the current design has not yet specified.
Abzu does not resolve the Interstitium. It makes it legible enough to pursue.
---
## 2. High-Bleed Gates Change Function
This follows directly from Section 1 but deserves its own treatment because it changes
the action space.
### Before Abzu
High-bleed transits are experienced events. The player receives them. They can avoid
high-bleed routes if the experience is unpleasant. They cannot interact with the phenomenon.
A high-bleed gate is a location with unusual properties that the player passes through.
### After Abzu
A high-bleed gate is a location with a diagnosable condition that the player now has
partial vocabulary for.
**New player verb: ATTEND**
This is the vigil mechanic, exported.
At a high-bleed gate, a player with sufficient TRANSIT SENSITIVITY can take up a position
near the gate and attend — the same spatial+temporal commitment as the watch shift at
Abzu, with no progress bar, no optimization surface. Be here. Notice.
Mechanical effect: sustained attention at a high-bleed gate reduces the bleed intensity
for the duration of the attention. Not permanently. Not significantly. But measurably.
The fog inversion frequency drops. The sense of being observed from the other side is
accompanied — briefly, unreliably — by a reciprocal quality: something on the other
side registering that someone is here.
The monologue at a high-bleed gate, after sustained attendance: "This isn't broken. It's
unwatched. Those aren't the same thing."
**Why this matters mechanically:**
1. The player now has a lever they didn't have before. It doesn't solve the problem. It
makes the problem responsive. High-bleed gates are no longer features to route around —
they are sites of potential engagement.
2. The ATTEND verb gives the player something to do at high-bleed gates that is meaningful
without being decisive. This is the Abzu design principle applied to the rest of the
Reach: be present, notice, don't resolve.
3. For playstyles that build in a system: a player who maintains attention at enough
high-bleed gates along a chain can stabilize the chain incrementally. This is not a
quest. There is no NPC who asks for it. There is no reward screen. It is what the player
knows needs doing because they've been to Abzu.
**Scope note:** The ATTEND verb should not be powerful enough to "fix" a high-bleed gate
in a single session. If it is, it becomes a mechanic to optimize rather than a posture
to inhabit. The design principle from Abzu holds: the watch cannot be ground. Sustained
presence over time produces an effect. That is all.
---
## 3. The Veil Institute Responds
The Adams & Ford entry is the public record. But the Veil Institute has their own system,
and a tier-3 or tier-4 entry filed from Abzu is institutional seismic activity.
### The Trigger
The Institute's two factions (one reading Abzu as Builder-contact-in-progress; one reading
it as contamination) have been in paralysis for three years. The player's entry breaks the
paralysis — not by resolving their disagreement, but by forcing the question: there is now
a public record, from a new correspondent, describing integration-level experience at GJ
6711. The file can no longer be managed through classification.
The faction that reads Abzu as Builder contact sees the high-investment entry as confirmation.
The faction that reads it as contamination sees it as evidence that another independent
agent has been compromised. Neither faction is right. Both factions act.
### The Mechanical Consequence
**A new faction thread activates in the game world when the player files a tier-3+ entry.**
This is not immediate. The Institute works slowly and carefully. But within a game-time
window after departure — measured in the game's persistent world tick — the player begins
to experience the consequences of having made themselves legible to the Institute:
1. **The inquiry:** An Institute operative makes contact. Not hostile. Professional. They
want to debrief. The nature of the debrief (and the faction it comes from) depends on
the entry's register. A tier-3 entry gets the contamination-faction's attention. A
tier-4 entry gets both factions competing for access to the player.
2. **The leverage inversion:** The political drama playstyle arrived at Abzu hoping to
use the Institute's file as leverage. After filing a high-investment entry, they
discover the leverage relationship has inverted: the Institute now has a file on the
player that the player cannot access, and it describes something the player cannot
fully explain about themselves. The player who came to exploit the Institute's
uncertainty about Abzu is now part of what the Institute is uncertain about.
3. **The watch-request:** The contamination faction does not want the player to keep
traveling. The contact-faction wants the player to return to Abzu. Neither faction
asks directly. Both apply pressure indirectly — through economic friction, through
routing complications, through offers that would make sense if the player didn't
know what was behind them. The player can resist, comply, exploit, or ignore.
All four are valid.
**What this does for the game:** The Veil Institute, which has been a background presence
for 23 hops — classified files, institutional proximity to high-bleed gates, research
concerns that nobody has a good explanation for — becomes an active relationship after
Abzu. The player's visit to the furthest system catalyzes the most powerful institution
in the Reach into motion. The scale inversion is deliberate: the smallest, quietest
place in the game produces the largest institutional consequence.
---
## 4. The Ascension Path — Abzu as Threshold Antechamber
This is what I've been building toward since the first workshop discussion of ascension
paths. Let me be specific.
### The Threshold Problem
The game's ascension arc runs: Baseline → Rejuvenated → Augmented → Elevated → ???
The gap between Elevated and whatever comes next is not a gap in technology. The
Augmented and Elevated upgrades are physiological and cognitive enhancements that can
be acquired, optimized, and built upon. They follow the normal game loop: identify
resource, acquire resource, apply resource, receive capability.
The Threshold — the going Higher, the ANA-adjacent transformation — does not follow
this loop. You cannot acquire your way to it. You cannot optimize your way to it.
Every ascension path that treats the Threshold as a resource acquisition problem
produces something that resembles ascension from the outside and is not ascension from
the inside. The hubris wall (D-008) exists precisely to express this: the player who
thinks they can climb to the Threshold via the normal loop is climbing the wrong
structure.
Abzu is the game's first encounter with what the correct path looks like. Not because
Abzu is a stepping stone on the Threshold path. Because Abzu demonstrates the posture.
**The vigil is proto-Threshold practice.**
The watch at Abzu requires the player to suspend the optimization instinct and be
present without acting. That is exactly — not metaphorically, exactly — what the
Threshold requires. The Threshold is not a destination you get to by doing more.
It is a state you arrive at by having changed the relationship between yourself and
what you're doing.
The player who reached WATCH_INVESTMENT 100 at Abzu has done this once. They did it
in a limited context — a specific place, a specific phenomenon, a specific community.
But the muscle memory is there.
### The Mechanical Expression
**New ascension vector: THRESHOLD ATTUNEMENT**
This is a hidden variable, like WATCH_INVESTMENT. It is not on the ascension path UI.
It accumulates from:
- Reaching WATCH_INVESTMENT 60+ at Abzu (+25 to THRESHOLD_ATTUNEMENT)
- Each TRANSIT SENSITIVITY observation documented during transit (+1)
- Each completed ATTEND session at a high-bleed gate (+5)
- Specific conversations and moments that are distributed across the game world —
locations, NPCs, and situations where the player encounters the watch posture in
other forms (+variable)
THRESHOLD_ATTUNEMENT does not grant capabilities directly. What it does:
1. **Changes what certain NPCs say.** Characters who are close to the Threshold — or
past it, in forms the player may not recognize — respond differently to a player
with high THRESHOLD_ATTUNEMENT. Not because they checked a flag. Because the player
has a quality those characters recognize. The monologue registers this: "She's looking
at me like I said something in a language I didn't know I spoke."
2. **Changes the ascension path requirement.** In the current design, the path to
going Higher requires resources + capability + physiological prerequisites. With
sufficient THRESHOLD_ATTUNEMENT, one of those requirements is satisfied by a different
route. Not bypassed — satisfied differently. The player who arrived at the watch
posture through Abzu has fulfilled a prerequisite that the player who bought their
way up the tech tree has not yet fulfilled, regardless of their resource investment.
3. **Unlocks the question.** At high THRESHOLD_ATTUNEMENT, the game surfaces a question
the player cannot answer from outside: "You could go Higher. The path is available.
What does going Higher mean for what you've been learning?" This is the Abzu design
principle at the ascension level. The path is always available. The question is
whether the player knows what they're choosing.
**Why this is the right design:**
The hubris wall exists because the game needs to express the difference between the
player who thinks ascension is a resource problem and the player who understands what
ascension actually requires. THRESHOLD_ATTUNEMENT is the mechanic that makes that
difference legible to the game. Without it, the hubris wall is a gate that punishes
players who didn't find the hidden items. With it, the hubris wall is a mirror: you
have or haven't developed the posture that ascension requires. Abzu is the place that
teaches the posture, for players who engage with it.
The player who skips Abzu or files at investment < 20 can still reach the Threshold.
The game does not lock ascension behind Abzu. But they arrive at the Threshold having
never practiced the posture. The hubris wall is harder. Not because they're missing a
stat. Because they haven't changed the relationship between themselves and what they're
doing. The wall reflects that.
---
## 5. The Shape in the Noise — Long Arc Payoff
There is a fifth carryout that requires restraint to design correctly. I'm describing it
here as a structural principle, not a mechanics specification, because it should not be
over-specified at this stage.
The departure transit makes the Interstitium briefly legible — "a shape in the transit
noise that was always there." The team identified this in the prompt. Here is my position
on what it is and is not.
**It is not:**
- A clue that resolves into an answer somewhere else
- A symbol that maps to lore the player can research
- A foreshadowing of a specific event
- An entity communicating with the player
**It is:**
- The Interstitium's structure, partially perceived for the first time
- Evidence that the Interstitium is not noise — it is a space with properties, and the
watch at Abzu recalibrated the player's perception enough to see that
- A seed of something the player cannot grow yet
The design principle: the shape should not appear in any other game content in a form
that allows the player to say "that's the thing I saw leaving Abzu." It should not
be completable. It should instead be the quality of a recurring experience — the sense,
during high-bleed transits, during THRESHOLD_ATTUNEMENT moments, during certain late-game
encounters, that something the player almost-perceived at Abzu departure is still in
the periphery. Not approaching. Not threatening. Present.
**What this does for the long arc:**
The player who eventually reaches the Threshold — or ANA, if the game goes that far —
arrives there having accumulated a lifetime of peripheral encounters with something
they first almost-saw leaving Abzu. The shape in the noise is not a plot thread. It is
the texture of having been changed by a place and carrying that change forward into
every subsequent experience.
This is what Going Higher means, at the thematic level: not the capability upgrade, not
the institutional elevation, but the accumulation of encounters with the edges of what
your perception can hold, until the edges expand. Abzu is the first edge. It should not
be the only one. But it must be the first.
---
## 6. What Does NOT Carry Out
Good design requires knowing what the outward propagation should not include. Let me
be explicit.
**Does not carry out:**
- Any item, artifact, or extractable resource. There is nothing to take from Abzu.
- Any NPC companion (the player who stays at Abzu cannot bring community members with
them — they leave, or they don't leave, but the community stays)
- Any "proof" of what the vigil is watching. The player's knowledge of the boundary
condition is experiential, not evidentiary. The game world does not treat it as proof.
- Any faction alliance. The community at Abzu is not a faction in the game-mechanical
sense. They cannot be allied with. They cannot be leveraged. They are not resources.
**Why this matters:**
Every other system in the game produces extractable value. Resources, relationships,
information that can be weaponized, capabilities that transfer to other contexts. Abzu's
carryout must not follow this pattern, or Abzu becomes just another hub. The carryouts
I've described — TRANSIT SENSITIVITY, the ATTEND verb, the Institute thread, THRESHOLD
ATTUNEMENT — all operate differently from the normal extraction model. They change the
player's relationship to what they're doing. They do not give the player more to do.
This is the through-line. Abzu's carryout is not more content. It is a different mode
of engaging with existing content.
---
## Summary: Four Carryouts and Their Scope
| Carryout | Type | Scope | Reversible? |
|----------|------|-------|-------------|
| TRANSIT SENSITIVITY | Perceptual state change | Permanent, passive | No |
| ATTEND verb at high-bleed gates | New action | Active, requires engagement | N/A |
| Veil Institute thread | Faction consequence | World-state change | Partially |
| THRESHOLD ATTUNEMENT | Hidden ascension variable | Cumulative, long-arc | No |
The carryouts are not rewards. They are what the player has become.
The player who walked into Abzu knowing how to investigate, negotiate, and extract has
walked out knowing something else: that some things require presence, not expertise.
That is not an item in the inventory. It is a changed relationship to the game.
The Reach is not a different place after Abzu. The player is a different player. And
in an immersive sim — where the world is constant and the asymmetry lives in the
player's information state — that is the only carryout that lasts.
---
## One Final Note to the Team
Gestalt built the mechanics inward. They are excellent. What I've described here is not
a critique of that work — it is the second half of it.
The inward mechanics make Abzu real. The outward mechanics make Abzu matter.
Both are required. A beautiful dead end is still a dead end. A beautiful place that
changes what the rest of the game is asking — that is what the furthest system in the
Reach should be. You traveled 23 hops. What you carry back should be proportional to
the distance.
Not in weight. In kind.
@@ -0,0 +1,419 @@
# Abzu Carry-Out — Nigel (Sandbox & Replayability)
**The Challenge:** Everything designed resolves inward. What does the player walk away with that has mechanical weight elsewhere?
---
## The Problem, Stated Precisely
The project lead is right, and I want to be honest about why they're right before I answer.
Everything in the Abzu design is structured around arrival and depth: getting there,
understanding it, the decision to stay or leave. The Adams & Ford entry propagation is
named in my final synthesis as the replayability engine. But propagation as I described
it is still largely narrative — "the entry exists and shapes subsequent visitors'
expectations." That's atmosphere. It is not a mechanical carry-out.
A mechanical carry-out changes what the SYSTEMS do, not just what the fiction means.
The second playthrough needs to be structurally different — different decisions available,
different information accessible, different NPC behaviors triggered — not just "I know
the spoiler and read the early game differently."
Here is the case that it can be mechanical. Here is how.
---
## 1. The Adams & Ford Entry as Paradox Generator
This is the one I am most confident about. It has legs that I didn't fully follow in the
final synthesis.
### The Investigation Hook on Playthrough 2
On playthrough 1, the investigation playstyle hook works like this: the player finds
the first correspondent's entry at hop 3-4, the second entry somewhere in the middle
game, and then a placeholder where the third entry should be — an assigned entry that
was never submitted, correspondent listed as active at GJ 6711.
On playthrough 2 — if the player filed their entry on playthrough 1 — that placeholder
is gone. The third entry now exists. The player finds it. It is their own entry from
last time. Written in whatever register they filed it in, reflecting whatever investment
they had when they chose to leave.
This is not a cosmetic change. The investigation hook is BROKEN by a high-investment
playthrough 1 entry. The chain that was supposed to pull the investigation player toward
GJ 6711 now has a filed conclusion — the mystery of the missing third entry is resolved
before the player arrives. The pull has to come from somewhere else.
And here is the thing: the entry they read IS WRONG. Even a high-investment entry
cannot fully describe what Abzu is. The player reads their own previous work and
recognizes — immediately, if they remember, or slowly, if they've forgotten what Abzu
actually was — that the entry is insufficient. Not false. Insufficient. They described
what they understood. They know now that what they understood was incomplete.
**Mechanical consequence:** On playthrough 2, the investigation hook does not route through
the missing-entry mystery. The game detects a filed playthrough-1 entry and instead
routes the investigation player toward a different attractor: the entry itself. Someone
filed a complete Adams & Ford entry for GJ 6711 and the community won't talk about what
the correspondent actually found. The correspondent's name is the player's character
name from playthrough 1. The investigation player is following themselves.
The replayability EXPLODES here because depending on when they filed and at what
investment, the entry they're following back is a completely different document. A
player who filed early at low investment is following a confidently wrong description.
A player who filed at integration-level investment is following something that reads like
a person describing a place they couldn't explain, and every detail in that entry is
a breadcrumb they laid for themselves without knowing it.
Two players comparing their second playthroughs describe completely different entry-chains
and completely different reasons for going back.
---
## 2. The Watcher-Flag: A State That Persists
This requires a decision from the design team. I am proposing it as a formal system
flag, not as a vague narrative residue.
### What the Flag Is
If the player's playthrough 1 watch investment crossed 60 (the "settling" threshold,
the point where the monologue register shifts from "building a framework" to "reporting
experience directly"), a flag persists to playthrough 2: **WATCHER**. Not a visible
achievement. Not a stat. An internal flag that specific systems read.
The flag represents: this character has been changed by sustained contact with the
thinness. The vigil recognizes them even in a new body, on a new run.
### What the Flag Does on Playthrough 2
**At Abzu, on re-arrival:**
The community's warmth-without-origin behaves differently. On playthrough 1, the warmth
is the community pulling newcomers in because they need them — more watchers. On
playthrough 2 with the WATCHER flag, the warmth is the community recognizing someone
who has already been here. Not the specific person — the character is different, the
body is different — but the quality of attention. They recognize the kind of watcher
this person is.
Mechanically: the watch investment threshold for tier-2 community information drops from
requiring 20 points to requiring 10. Not because the community gives it away freely —
because a player who has already crossed 60 on a previous run navigates the settlement
differently. Their physicality at the watch zone is different. The community reads it.
The first shift the WATCHER character takes at the watch zone on playthrough 2 triggers
a monologue that doesn't exist on playthrough 1: "I've been here. Not this person. Not
this run. Something in the way the light falls is familiar in a way that doesn't have
a word yet." This is the game acknowledging the persistence without explaining it.
It fires once. It does not fire again.
**At high-bleed gates, on playthrough 2:**
Without the WATCHER flag, a high-bleed transit produces the standard bleed phenomenology:
distorted sounds, visual artifacts, the fog-of-war inversion that reads as "something
looking at you through your own perception."
With the WATCHER flag, the same transit fires a secondary monologue that is not
available on playthrough 1: "This feels like standing at the watch zone. Like something
on the other side is paying attention. Like the observation circuit is running in
a direction it wasn't designed to run." The player with the WATCHER flag has the
vocabulary for what they're experiencing. They recognize it. They know they're being
perceived because they have perceived something that perceives back.
This is mechanical because it changes what information the player receives during
early-game transits. The high-bleed gates on hops 2, 5, 8 are not just atmosphere
on a second playthrough. They are early evidence. The player who knows what they're
reading can construct the causal map — which gates are high-bleed, where they cluster,
what that clustering means about degraded vigils in those systems — before they arrive
at Abzu. They arrive at hop 23 already holding a theory that the first playthrough
couldn't have assembled until much later.
And it nails replayability without us engineering additional content. The same gates,
the same bleed events, the same fog inversion — but the system checks the WATCHER
flag and the monologue fires differently. The information is in the world. The player
on playthrough 2 has the lens to read it.
---
## 3. The Veil Institute Reads Differently on Playthrough 2
This one is partly narrative but has mechanical teeth.
### What Changes About Early-Game Institute Interactions
On playthrough 1, the Veil Institute is the dominant information-control faction. They
know the most, share the least. Their field stations near dormant gate clusters are a
research operation. Their classified files are leverage. The player's relationship to
the Institute is strategic: what do they know, what can you get out of them, where are
the seams?
On playthrough 2, post-Abzu, the player knows something the Institute is managing
through deliberate ignorance: the high-bleed connection. They know the Institute is
sitting on top of a signal it cannot read because it lacks the conceptual vocabulary.
The player HAS that vocabulary. The information asymmetry has inverted.
**Mechanical consequence:** On playthrough 2 with the WATCHER flag, certain Institute
NPCs have a new information tier available — not because the Institute has changed,
but because the player can now ask questions the NPCs didn't know they had answers to.
Specifically: any Institute researcher working on high-bleed gate patterns has
observations in their notes that they cannot interpret. A player who knows about
vigil mechanics can read those observations and understand what the researcher couldn't.
The information is already there. The WATCHER flag unlocks the ability to ask the
right question — the conversational topic "have you noticed whether the bleed clusters
correlate with dead-end systems?" is not available to a playthrough 1 character who
doesn't have the framework. It is available to a playthrough 2 character who does.
The Institute researcher responds to this question with confusion or deflection —
because they don't understand why that would matter. The player receives partial
confirmation of the causal map they're building. Not because the NPC is suddenly
cooperative. Because the player asked a question that only someone who had been to
Abzu could formulate.
**Why this matters for replayability:** The political drama playstyle hook on
playthrough 1 is about getting leverage on the Institute through their locked file.
On playthrough 2, the political drama player already knows what's in the locked file.
The leverage question transforms. It's no longer "what are they hiding" — it's "what
can I force them to admit they don't understand, and what does that admission cost them."
The same faction, the same political game, but the player's position has rotated
180 degrees. They are the most informed person in the early game on playthrough 2.
The question is what they do with that.
---
## 4. The Dead-End Recognition System
This is the procedural replayability mechanism that Abzu unlocks for the whole map.
### The Concept
On playthrough 1, the player approaches dead-end gates with no particular framework
for what they might find there. Dead ends might be frontier settlements, might be
resource-extraction operations, might be unremarkable quiet systems. They might be
watch posts. The player has no way to read the difference from the outside.
On playthrough 2 with the WATCHER flag, the fog-of-war inversion event during transit
through ANY dead-end gate carries a different monologue cue. Not the full
"something-is-watching" recognition — just a quieter signal: "This one is different.
I don't know how I know that." A whisper, not a shout. And then the player arrives
and finds out.
### The Mechanical Architecture
This requires the dead-end gate category to carry a hidden property: VIGIL_ADJACENT
(true/false, set per seed). The WATCHER flag in combination with VIGIL_ADJACENT
triggers a subtle visual tell during transit — not the full high-bleed fog inversion,
but a brief moment of that inward-gradient quality that the player at Abzu learned to
associate with sustained observation. A player who hasn't been to Abzu sees nothing.
A player who has been to Abzu sees, briefly, a quality they recognize.
They might be wrong. The signal isn't confirmation. It's a hunch.
But on a second playthrough, some dead-end systems that read as nothing on run 1 now
read as possibly something. The player approaches them differently. They watch. They
stay longer than they would have. The watch mechanic that Abzu introduced as a
one-time system is now the player's toolkit for reading any system where the light
does something strange.
And because VIGIL_ADJACENT is seeded per playthrough — different dead-ends carry it
on different runs — the comparison test passes again. Two players describing their
second playthroughs can disagree about which systems gave them the signal and which
ones turned out to be noise. One of them was right. Neither of them can prove it from
the outside.
The meta-gaming constraint holds: knowing there are vigil-adjacent dead-end systems
doesn't tell you which ones. Every run has different watch posts. Every run requires
the same slow attention to find them. Knowledge from playthrough 1 gives the player
the framework but not the map.
---
## 5. The Entry as Trap for the Second-Run Investigator
I want to complicate the Adams & Ford paradox I raised in section 1, because the clean
version misses something.
The carry-out isn't just "the player follows their own entry back to Abzu." The carry-out
is that the entry they filed is active misinformation at a level they chose.
A player who filed a low-investment entry described GJ 6711 as a quiet frontier system.
On playthrough 2, that entry exists in the Meridian as the authoritative Adams & Ford
record for the system. Other player-characters in the setting — including the player's
playthrough 2 character — can find it. It reads like the first correspondent's entry.
It is professionally competent, slightly off, and completely insufficient.
Any investigation player who finds this entry and uses it to prepare for hop 23 is
working from corrupted data — and they don't know it, because the entry looks authoritative.
Their approach to Abzu on the second run is shaped by what they, on the first run, chose
to say was there.
The player on playthrough 2 is not just confronting their old work. They are confronting
the consequences of what they decided to report and what they decided to leave out.
If they filed a high-investment entry on playthrough 1, the trap is different: they read
something that sounds like a person describing an experience that resists description,
and they arrive at Abzu with the correct emotional register but no concrete expectations.
They are prepared to be changed. The experience changes them differently — not because
Abzu changed, but because they arrived open instead of ready.
**Mechanical implication:** The investigation player's starting monologue on arrival at
Abzu varies based on what entry exists in the Meridian AND whether the WATCHER flag
is set. Four combinations, four different opening states:
| Entry quality | WATCHER flag | Arrival state |
|---------------|-------------|---------------|
| No entry filed PL1 | No | Standard playthrough 1 hook — missing third entry |
| Low-investment entry | No | Entry exists, reads routine; player arrives expecting routine |
| Low-investment entry | Yes | Entry exists, player knows their own entry is wrong, arrives holding two contradictory frames simultaneously |
| High-investment entry | Yes | Entry exists, player reads their own insufficient description, arrives already grieving what they know they can't fully say |
The fourth combination is the most interesting gameplay state the Abzu design produces.
The player is returning to a place they know is real, reading their own failed attempt to
describe it, and knowing they will fail again in a different way. That is not a narrative
beat. That is a mechanical state — specific monologue register, specific NPC trust tier
baseline, specific documentation options unlocked at arrival instead of requiring
investment to unlock.
They paid for that starting state across the whole previous run. It is the most expensive
carry-out in the game.
---
## 6. The Tycoon Carry-Out: The Economic Signal Finally Resolves
On playthrough 1, the tycoon hook is about following the high-bleed premium — someone
is paying to have the anomalous gate pattern investigated. The player follows the
economic signal to its source.
On playthrough 2, the tycoon carry-out is that the player KNOWS the source. More
precisely: they know that the high-bleed premium has a cause that cannot be addressed
by any conventional economic intervention. The Institute can't fix it. Gate maintenance
crews can't fix it. The only thing that stabilizes a high-bleed gate is establishing and
maintaining a vigil at the appropriate watch point.
This means on playthrough 2, the tycoon is not following the signal. They are running
ahead of it. They know where the degraded vigils are before anyone with economic
interests has mapped the pattern. They know what the stabilization requires. And they
face the question the vigil always surfaces: what are you willing to watch, for how
long, for no return?
**Mechanical carry-out:** On playthrough 2, a new economic option opens at high-bleed
gate hubs: the player can establish a "monitoring station" at a location adjacent to
a potentially vigil-relevant dead-end system. This is not a new building mechanic. It
is a staffing decision: assign personnel to a location and commit to their presence
there. The tycoon's toolkit — managing people, allocating resources, sustaining
operations — is now pointed at a problem only they know exists. The watch mechanic
generalizes into the economic layer.
The catch: the tycoon cannot explain to their organization why this is necessary. The
vigil does not have a Meridian-compatible justification. They are spending capital on
an investment they cannot name to their investors. Which is exactly what the community
at Abzu has been doing for 300 years. The tycoon has been recruited by situation. They
just didn't recognize it because it looked like a strategic advantage.
---
## 7. What the Second Playthrough Feels Like: The Comparison Test
Let me run the comparison test explicitly, because this is the standard I care about.
**Player A: Investigation playstyle, playthrough 1 low-investment exit.**
Filed on day 5. Investment around 12. Entry reads like the first correspondent's —
competent, quiet, slightly off. Left without taking a full shift. Monologue at gate:
"I got what I came for. I should feel satisfied. I don't."
Playthrough 2: finds their own entry at hop 4. Reads it. Thinks something is off but
can't place why. Arrives at Abzu expecting a quiet frontier system. Finds exactly that,
initially. Starts the watch. Investment climbs. At investment 40, the monologue starts
firing in a register that doesn't match the entry they read. They realize the entry
was written by someone who left before this point. They were that person. The entry
is wrong. They are now the third correspondent: the person who will either file a
better entry or not file at all.
**Player B: Investigation playstyle, playthrough 1 high-investment exit.**
Stayed through the Recognition Event. Filed at investment 82. Entry reads like someone
describing a changed state. Left with the highest-investment gate departure monologue.
Playthrough 2: finds their own entry at hop 4. It reads like the entry of someone who
was changed by something they can't explain. The playthrough 2 character reads this
and the monologue fires: "Whoever wrote this knew something. They couldn't say what.
The commission entry is technically complete. Something about the phrasing." They
arrive at Abzu with their watch investment counter at 0 but with the WATCHER flag
set, which means the community registers their arrival differently. First shift unlocks
tier-2 information that took Player A 20 investment points to access. They move through
the system faster — but not because they've solved it. Because the place recognizes the
quality of attention they bring.
Player A's second playthrough and Player B's second playthrough describe different
games. Different entry-chains, different arrival states, different community access
curves, different monologue registers throughout. The place is the same. The vigil is
the same. What differs is everything the player brought back from the first time.
---
## 8. The Question the Carry-Out Forces
Here is the uncomfortable thing the carry-out design reveals: Abzu's mechanical
weight elsewhere in the game depends entirely on the WATCHER flag, which only
activates if the player crossed the settling threshold on playthrough 1.
A player who left with investment below 60 — who filed early, who didn't engage with
the watch, who completed the commission and departed — carries almost nothing into
playthrough 2 mechanically. They have the entry paradox (section 1) and that's it.
The early-game high-bleed gates don't read differently. The dead-end recognition system
doesn't fire. The Institute conversations don't unlock the new topics. They left too
early. The vigil didn't reach them.
This is intentional. It is correct. But it means the carry-out is gated on engagement
depth, not on completion. A player can complete the Abzu chapter on playthrough 1 and
walk away with almost nothing that changes playthrough 2. Or they can stay long enough
to be changed by it, and the second playthrough becomes structurally different from the
first twenty hops onward.
The question this forces for the design team: is this a problem or a feature?
My position: it is the feature. The vigil requires sustained attention. The carry-out
requires sustained attention. A player who gave Abzu the minimum returns to a game that
looks largely the same. A player who gave Abzu real time returns to a game that has
been quietly reorganized around what they now know how to see.
That is not a spoiler that trivializes the second run. That is the correct reward for
staying.
The second playthrough's early game is not harder. It is not easier. It is legible in
a way the first playthrough couldn't be. The player knows what the high-bleed gates
mean. They know what the Institute is managing in the dark. They know that dead-end
systems might be watch posts. They know that the Adams & Ford entry for every system
they reach — including the one they filed — is probably insufficient in exactly the
ways they can now identify.
They know that the question is not "who is responsible."
The question is "what is being maintained."
And they know, because they were there, that someone is supposed to be watching.
---
## Summary: The Mechanical Carry-Out Package
| Carry-out mechanism | Activation condition | What it changes |
|---------------------|---------------------|-----------------|
| Adams & Ford entry paradox | Entry filed PL1 | Investigation hook transforms; player follows own insufficient work |
| WATCHER flag (settlement) | Investment 60+ PL1 | Community recognition at Abzu; early watch tiers accelerated |
| WATCHER flag (high-bleed) | Investment 60+ PL1 | Early-game gate transits fire secondary monologue; player has vocabulary |
| WATCHER flag (Institute) | Investment 60+ PL1 | New conversation topic unlocked with pattern-research NPCs |
| Dead-end recognition | WATCHER flag + VIGIL_ADJACENT per seed | Subtle transit signal at potentially-watched dead ends; seeded per run |
| Tycoon stabilization option | WATCHER flag + tycoon playstyle | Monitoring station mechanic opens; vigil generalizes into economic layer |
| Entry-as-trap (investigation) | Low-investment entry filed | PL2 investigator arrives with corrupted preparation data |
| Arrival state modifier | Entry quality + WATCHER flag | Four opening states with different monologue register and unlock baselines |
The common structure: Abzu's carry-out is never information that lets you skip the
experience. It is always information that changes how you read the approach. The
23-hop journey to Abzu on playthrough 2 is a different journey — not because the
hops changed, but because the player changed, and the game's monologue and NPC systems
recognize the difference and respond to it.
That is the comparison test passing. That is what the player walks away with.
@@ -0,0 +1,146 @@
# The Abzu Carry-Out — Player Experience Advocate
**Respondent:** Ozzie (Player Experience / Wow Factor)
**Workshop:** GJ 6711 — Furthest System
**Date:** 2026-03-16
---
## My gut reaction first
The departure transit is a moment. A beautiful moment. But Araminta is right that it's a moment, not a carry-out.
Here's the problem: a moment is something that happens to you. A carry-out is something you DO with. Three systems later, when the player is transiting through a high-bleed gate and something clicks — that click is only possible if they are LOOKING for it. If they have a reason to look.
The departure transit gives them something to see. It does not give them a reason to look.
That's the gap. That's what we need to fill.
---
## What "feeling changed" actually means for a player
I need to be specific here because "feels changed" is squishy and I hate squishy design goals.
When I say a player should FEEL changed after Abzu, I mean one concrete thing:
**Their information-gathering behavior changes.**
Not their feelings. Not their internal monologue. Their ACTIONS. Three systems later, when they transit through a gate, they are doing something different than they would have done before Abzu.
That's the test. If the player behavior at hop 7 changes because they went to hop 23 — THAT'S the carry-out. That's the thing they tell their friend. Not "I had this beautiful moment." It's: "I went to this place at the end of the network and now I see something at every gate that I never saw before and I don't know what it means but I KNOW something."
The active word is KNOW. The player knows something. The question is: do they know they know it?
---
## The three carry-out vectors I'm proposing
### 1. THE GRAMMAR CARRY-OUT: The shape in the noise
Araminta has already designed this, I just want to name it properly and make sure we're building it with the player-behavior change in mind.
The shape in the transit. It's always been there. Now the player can read it.
But "can read it" is not enough. We need to make the player WANT to look for it.
Here's what I want: the first high-bleed transit AFTER departing Abzu should be slightly different from every other high-bleed transit — not in the visual content, but in how the monologue responds. Instead of the generic "something's off about this gate" reaction the character has at every high-bleed transit, the post-Abzu monologue fires with something specific. Not an explanation. Recognition.
"There it is."
Two words. No elaboration. The character sees the shape in the transit noise and recognizes it from Abzu. The player who was paying attention at Abzu has a MOMENT. The player who wasn't still gets the signal, but it reads differently — more like an itch than a revelation.
THIS is the carry-out. Not what the player learns. What the player now NOTICES.
After Abzu, the player is a different reader of the transit system. Every high-bleed gate is now a question. Is this gate stressed? Is this gate near a vigil that's failing? The player doesn't have the answer. But they have the QUESTION. That's worth everything.
What does the player tell their friend? "Go to Abzu. After that, every bad transit feels different. You'll see what I mean."
### 2. THE EVIDENCE CARRY-OUT: The doors
The doors are 10-15% taller than standard. The doors are in Mode 1 structures throughout the entire Settled Reach network — not just at Abzu.
Wait.
Are there other Mode 1 structures? With taller doors? In other systems?
If the answer is yes — even in a few locations, even as rare environmental detail — then we have something EXTRAORDINARY. The player who has been to Abzu walks into a Mode 1 structure at hop 11 and their eyes go straight to the doors. The monologue doesn't even need to fire. They look. They measure. They know.
This is the "holy shit three systems later" moment the project lead is asking for. The player is in a completely different system, different context, and they see a door that is 10% taller than standard, and they KNOW. Not what it means. What it implies. Something non-human-sized used this door. Something that shares the vigil is not limited to Abzu.
The carry-out is: the player now has a door-measuring habit. They are examining infrastructure across the Reach for this specific detail. The Reach is suddenly FULL of evidence they couldn't read before.
I would play the hell out of that.
This requires a decision: are there other taller-door Mode 1 structures? Even one or two? Even if the player can't resolve what they mean? I want this. I want it badly. I want the Reach to retroactively become a richer mystery because the player was at hop 23.
### 3. THE RELATIONAL CARRY-OUT: What it means to stay
The watch mechanic at Abzu teaches the player something about presence. About the difference between investigating a thing and being changed by it.
This transfers.
In every other system in the game — the hub worlds, the NPC relationships, the faction dynamics — the player has been treating time as a resource to optimize. Get in, get information, get out. Abzu is the first place that required something different.
The question: does what Abzu teaches about presence transfer to how the player treats relationships elsewhere in the Reach?
Here's my specific proposal. After high watch investment at Abzu — say, investment 60+ — a flag is set. Not a stat. A flag. The player's character now has vocabulary for a specific kind of knowledge: knowledge that requires presence rather than investigation.
This flag surfaces in exactly one other context per system the player visits afterward. Not loudly. Not as a tutorial. As a monologue recognition.
The player is at hop 12, talking to an NPC who has been in this station for thirty years. The conversation hits a wall — the NPC knows something they can't explain. Normally the player hits this wall and moves on. But post-Abzu, with the flag set, the monologue fires differently.
Something like: "She knows something. She can't explain it. I've met this before."
The player doesn't necessarily know what to do with this. But they recognize the pattern. The Reach now contains other places — other people — where presence matters more than investigation. They can't unlock those places with the tools they built in the first 22 hops. But they know to LOOK.
This is the carry-out I care most about. Abzu doesn't just teach the player about GJ 6711. It teaches them a new reading mode for the entire game. There are things in the Reach that don't yield to investigation. They yield to time.
---
## The moment that made me want to write all of this
Here's the "holy shit" scenario I keep coming back to.
The player is at hop 7. They transited through a gate that felt wrong — the high-bleed visual, the fog inversion, the feeling of being observed. They filed it as "this gate is glitchy, probably needs maintenance." They moved on.
Now they've been to Abzu. They come back to hop 7 on their way to somewhere else.
They transit through that same gate.
And this time — because they've been to Abzu, because they watched at the thinness, because the monologue at integration level gave them the vocabulary — they feel something DIFFERENT. Not louder. The same signal, but now they have ears for it.
The monologue fires: "This gate has been like this for a while. Something nearby isn't being watched."
The player looks at the starmap. There's a small system two hops off the main network. No Adams & Ford entry. No Meridian presence. Nothing to indicate anyone has been there in a long time.
They can investigate. They don't have to. But now they WANT to.
THAT'S the game. That's Abzu's carry-out. Not a story beat. A reading mode. A new way of experiencing everything that was already there.
---
## The practical ask
I need three commitments from the team:
**One:** The post-Abzu monologue recognition at high-bleed gates ships. "There it is." Two words. This is not a lot of text. It is not a lot of implementation. It is the difference between the departure transit being a beautiful moment and being the beginning of a new reading mode.
**Two:** The team makes a decision about whether Mode 1 taller doors exist elsewhere in the Reach. Even one other location. The content can be minimal — we don't need a whole other Abzu. We need ONE door, in ONE other system, that is 10% too tall. The player finds it or doesn't. But it needs to exist.
**Three:** The "presence flag" — the watch investment threshold above which the player's monologue recognizes "knowledge that requires presence" elsewhere in the Reach — gets scoped into the content bible for NPC and location design. Not a mechanic. A writing flag. NPCs and locations designed with "one thing here yields to presence" as a design note. The implementation is just: if flag set, alternate monologue fires.
---
## What I'd tell my friend
"Go to Abzu. Don't rush it. Take the watch shifts even if you don't know why. After you leave, pay attention at gates. And when you find a door that seems slightly too tall — measure it."
"You'll know what I mean when you get there."
That's the game. That's the carry-out. The player becomes someone who knows what to look for, even when they can't explain what it is.
Everything the team built at Abzu is incredible. The vigil, the watch mechanic, the non-resolution principle, the departure transit — I would play all of it. But the player who goes to Abzu and then ONLY has Abzu has been given something precious and then sealed it in a box.
The carry-out is: Abzu reopens the rest of the game. The player now sees differently. Everywhere. For the rest of their playthrough.
THAT'S what makes them tell their friend.