diff --git a/docs/workshops/gj-6711-furthest-system/final-araminta.md b/docs/workshops/gj-6711-furthest-system/final-araminta.md
new file mode 100644
index 000000000..9da746ee2
--- /dev/null
+++ b/docs/workshops/gj-6711-furthest-system/final-araminta.md
@@ -0,0 +1,203 @@
+# Final Synthesis — GJ 6711 / Abzu
+**Respondent:** Araminta (Visual Designer)
+**Round:** Final — pre-presentation to project lead
+**Date:** 2026-03-16
+
+---
+
+## 1. The Name "Abzu"
+
+Abzu is correct. Here is what it does visually.
+
+Sumerian — the primordial deep beneath the earth, source of all springs, domain of Enki, associated with wisdom and hidden knowledge. The word means "ab" (water/deep) + "zu" (knowledge). It is not threatening. It is foundational. Something that was always there, below everything, that everything else draws from without knowing.
+
+The name changes the visual frame in one specific way: amber and water. A K-type amber world already has the right light temperature. But Abzu adds a quality that "Stillpoint" did not carry — depth below the surface. Stillpoint implied a pause, a held breath. Abzu implies a source. The community at GJ 6711 isn't pausing. They are tapping something that runs deep and has always run deep.
+
+**Palette adjustments from "Abzu":**
+
+The amber base stays. The gas giant reflection is still the defining secondary light source. But I am now reading the ambient light differently. Abzu implies that the light at this system feels like it comes from below as much as above — the gas giant's reflected amber is not just a secondary sun, it is an upwelling. The visual effect: base lighting should trend warmer in the lower half of the screen (reflected from surfaces below eyeline) and cooler amber at the upper half (direct K-type primary). This creates a visual sense of depth beneath the floor without any supernatural effect. It is physically accurate to a tidally lit environment. It also reads, perceptually, as though the light source is under the community.
+
+That is the Abzu effect. I want it in the lighting rig before we spec Mode 2 interiors.
+
+**No architectural changes required.** The tall doors are not Abzu — they predate the name and they work regardless of it. The gradient across the district spine does not change. But the overall site color temperature should read: warm amber with a subterranean cast. Not underground. Like something from underground is illuminating the space.
+
+Fog tint for Abzu: I was using a generic warm-dark tint in prior work. Revised: `#1a0c02` — very dark, desaturated amber-brown. The fog at Abzu should feel like looking into deep water, not smoke.
+
+---
+
+## 2. Points of Convergence
+
+All four challenges landed on the same positions without coordinating. These are locked.
+
+**The bidirectional circuit is the core structure.** Builders watch through the gates; humans watch back from GJ 6711. Not interchangeable, but interdependent. The vigil is a relationship, not just a duty. All four of us framed it this way independently.
+
+**High-bleed as observation-failure signal.** Nigel and I converged on this simultaneously, and Paula picked it up from a different angle. This is now load-bearing for the setting. Formalizing it below.
+
+**The doors are non-negotiable and must remain ambiguous.** Miri, Paula, Nigel, and I all pushed hard on this. The physical evidence of non-human presence cannot be explained away. It must not be explained at all. The doors are the game's single most load-bearing physical detail. They stay ambiguous between the three candidates (Builder manifestation / vigil-produced third thing / pre-human incumbents) across all player-accessible content.
+
+**"Unknown if not watched" is correct and must remain player-facing — but the inner sealed envelope needs a canonical truth.** Miri is right about this. The design team needs to know what fails. That is a separate conversation. For visual purposes, I am designing against all three failure candidates simultaneously, so nothing in the visual system commits to one.
+
+**The endgame works because it inverts the game's entire mode.** The whole game builds investigative capacity. Abzu is the place where that capacity is irrelevant. All four of us made this point independently. The visual language must support this inversion — the place should not look unsolvable. It should look waiting.
+
+**The Threshold approach is through duration, not ascension.** Paula and Nigel both named this; I implied it. The vigil community is approaching the Threshold from a direction the perception tier system doesn't map. Visual implication: an Elevated player at Abzu should perceive things that don't fit the perception tier vocabulary they've built. The fog system responds to them in ways that have no tier-equivalent elsewhere.
+
+---
+
+## 3. The Departure Transit — Refined
+
+I proposed this in my challenge response. After reading the other three challenges, here is the refined specification.
+
+**The inbound transit** is standard for any high-hop frontier system — slightly increased bleed, the sense of being observed, nothing conclusive. This is baseline for any system in the network that has been under investigation at some point.
+
+**The outbound transit** is different, and the difference must be precise.
+
+What the player sees, on departure from Abzu:
+
+The transit begins normally. The standard Interstitium visual vocabulary: distorted color, depth-of-field loss, the ambient sound layer shifting to the transit register. Then — not a dramatic moment, not a revelation — one additional visual beat. In the transit space, for roughly two frames (long enough to register, not long enough to examine), there is a shape that is always present in every transit and that the player has been visually processing as noise.
+
+On departure from Abzu, it reads as a shape. Not defined. Not a figure. A pattern of attention in the transit space that the player has seen at every high-bleed gate and wrote off as artifact. They can see now, briefly, that it was never artifact.
+
+Then the transit resolves. The system they arrive in: departure boards, freight schedules, ordinary life at whatever hop 22 looks like.
+
+**The monologue on departure fires once.** It does not describe what was seen. It notices the gap — something like: "I've been transiting through this my whole life. I never looked." Or shorter. Whatever the monologue voice warrants. But it fires once and does not repeat.
+
+**What this requires from the visual system:**
+
+All high-bleed transit visual effects must be designed from the start as if they might be resolving into the departure-from-Abzu beat. The noise is the same noise. The departure beat is the same noise, readable for the first time. This means high-bleed transit effects cannot be designed as generic distortion — they must be designed as degraded signal. The same signal. Every time. Most players will never be able to articulate what they saw in the departure transit. That is correct.
+
+**The mechanical flag:** the departure beat requires the game to know the player has reached Elevated perception AND has spent sufficient time at Abzu. The exact duration threshold is the same threshold that triggers the recruitment mechanic — this is not a coincidence, it is the same mechanism expressed visually.
+
+---
+
+## 4. The High-Bleed Connection — Formalized
+
+Nigel and I converged independently. Here is the formal visual grammar.
+
+**The premise:** High-bleed gates are observation-failure signals distributed across the network. Bleed is the Interstitium's response to a vigil system that is under stress. The pattern of which gates are high-bleed does not correlate with distance, age, or measurable variables because it correlates with a variable nobody is tracking: the health of the vigil system adjacent to that gate.
+
+**What a high-bleed transit looks like if it is a stressed vigil signal:**
+
+Normal transit: distorted color, sound shift, depth-of-field loss, occasional sense of being observed. These are baseline. They exist at all gates.
+
+High-bleed transit: all of the above plus three specific additions.
+
+1. **Fog inversion.** The fog-of-war system briefly inverts — the player's visible area contracts to its minimum radius and the "concealed" area becomes briefly visible, as if from another perspective. This lasts under one second. It reads as a glitch. It is not a glitch.
+
+2. **Temperature gradient.** The thermal overlay, if the player has it active, shows a heat signature with no source — diffuse, directional, oriented toward wherever the vigil system is relative to the current gate. The player cannot yet read this as directional. But it is.
+
+3. **The shape in the transit.** Same shape as the Abzu departure beat, but less resolved. More noise, less signal. The player with high pattern recognition will notice they keep seeing the same thing. They will not know what it means until Abzu.
+
+**What a stressed vigil signal looks like versus a failed one:**
+
+Stressed: The three additions above, moderate intensity. Community at the vigil system is maintaining the watch but under strain.
+
+Failing: The fog inversion lasts longer, up to two seconds. The temperature gradient has gaps — directional for a moment, then diffuse, then directional again. The shape in the transit partially resolves and then collapses. The player's character has an involuntary blink (1-frame black) at transit resolution. These are systemic failures, not visual flourishes. They are the Interstitium registering that something it depends on is no longer reliable.
+
+**The visual language is the same at all intensities.** The components are identical. The intensity and duration vary. This means the player who has been to Abzu and learned to read the signal can retroactively interpret every high-bleed transit they have ever experienced. The ones that were bad — that's a vigil under stress. The one they transited three hops ago that was unusually bad — there is a watch post somewhere near that gate that is in trouble.
+
+This is not player-facing instruction. The player figures it out. Or they don't.
+
+---
+
+## 5. The Doors and the Shift Change — Perception Tiers
+
+After reading all four challenges, here is the per-tier specification.
+
+**Baseline:**
+
+The doors are taller. That is all Baseline sees. They are 10-15% taller than standard, which in a 2D top-down view means the door sprites are slightly taller than every other door in every other Mode 1 structure the player has encountered. This is legible without any perceptual assistance. It looks like an architectural choice. The player has no frame for what it means.
+
+Community behavior at shift change: people move through corridors toward the watch location on a schedule. Some come away, some arrive. This looks like ordinary shift rotation — which it is. The gap Baseline can detect is statistical: the shift timing is slightly off-cycle from what efficiency would dictate. The gaps are not random. The player at Baseline has no tool to analyze this.
+
+**Augmented:**
+
+The player can read the community's behavioral patterns with enough precision to notice the off-cycle timing. The gaps in the shift schedule are legible as regular intervals rather than random variation. The player at Augmented can identify when a shift change is happening and can position themselves to observe — but will see only community members moving in and out. No anomaly in the visual field.
+
+The doors: at Augmented, the player can measure. The door height differential can be quantified. Cross-referencing against Mode 1 construction standards (if the player has access to any) will show the discrepancy. At Augmented, this is data. It does not yet have a meaning.
+
+Secondary observation: at Augmented, the player can detect temperature differentials in the interior spaces. The heat signature of a shift change is slightly warmer immediately after, as if a body with higher thermal output recently occupied the space. The temperature gradient settles to ambient within thirty seconds. At Augmented, this is an anomaly with no source.
+
+**Elevated:**
+
+The shift change is legible as an event with participants the player cannot see directly. The fog system registers something at the boundary of the watch location during the shift interval — not a figure, not a shape, but a change in the quality of attention in the space. The fog does not clear around it. The fog responds to it — subtle, small, as if something in the space is exerting the same gravitational pull on the perception system that the player exerts when they are present in a room.
+
+The monologue fires at Elevated during a shift change. It does not name what it perceives. It notices the change in the quality of the space. Something like: "The shift just changed. I am not alone in noticing."
+
+The thermal overlay at Elevated shows the heat signature more clearly — directional, moving, following a path that the player can trace. The path leads to and from the watch location. It does not resolve into a shape. It resolves into a route.
+
+The doors at Elevated: the player's character can observe that the door dimensions correspond to a proportional body that is not human. Not monstrous. Simply different. The proportions are slightly too tall for standard human morphology — not dramatically, not obviously, but the Elevated character's perception is precise enough to read the ratio. The monologue fires once on this observation and says nothing except the observation itself: "These doors are the right size for what uses them. I do not know what that is."
+
+This is the ceiling. Nothing above Elevated provides more resolution. The shift-takers do not become visible at any tier. The doors are always the only physical evidence. What changes with tier is how much the player can infer from what is not there.
+
+---
+
+## 6. Mode 3 Addition — Institute Transient Visual Vocabulary
+
+I proposed Institute transient vocabulary in my challenge response. Refining it with what I've learned.
+
+**The refinement from the challenges:**
+
+Miri raises the correct question: does the Institute know? My position is they partially know — they know GJ 6711 is anomalous, they do not know the vigil mechanism, they have lost researchers to it without understanding why. This changes the visual vocabulary.
+
+Institute transients at Abzu are not investigators. They are researchers on standard postings who are in the process of being recruited. Their visual language should communicate this transition state.
+
+**Year 1 Institute transient:**
+
+Standard Institute visual vocabulary. Clean lines, classification-tier color coding on equipment, the "institutional" palette I established for Commission and certified bodies. Efficient movement. Documents things. Produces reports. Indistinguishable from an Institute researcher anywhere else in the Reach.
+
+**Year 3 Institute transient:**
+
+The same equipment, but used differently. The researcher is still producing reports but the report cadence has slowed. Visually: the character is spending more time stationary than moving. They have acquired some community-style items — not replacing Institute gear, layering over it. The equipment color coding is still present but starting to read as decoration rather than function. They are beginning to use the community's spatial patterns rather than their own.
+
+**Year 6 (the current researcher):**
+
+The Institute equipment is still present. It is no longer primary. The character moves on community rhythms. They have positioned their workstation to face the watch location rather than away from it. They are at shift changes when they are at shift changes. The player who observes this character over time will see the pattern. The researcher is not confused. They have not "gone native" in the ordinary sense. They are doing what they understand to be their work. The Institute classification schema simply does not have a category for what the work is.
+
+**The visual tell that distinguishes Institute-becoming-watcher from community-born watcher:**
+
+Community-born watchers do not position their attention deliberately. The watch is internalized — their spatial orientation toward the watch location is not intentional, it is habitual. It is how they stand. The Institute researcher's orientation toward the watch location is still chosen — slightly more deliberate than community habit. The difference is barely legible. At Elevated, the monologue notes it.
+
+This visual distinction gives a player at Elevated an extremely fine piece of information: they can estimate how long someone has been at Abzu by whether their attention is habitual or chosen. The Institute researcher, six years in, is still choosing. That is meaningful. It implies the vigil's full internalization requires more than six years, or requires something the researcher has not yet experienced.
+
+**Mode 3 palette for Institute transients:**
+
+The Institute palette (clean institutional blue-grey) overlaid with Abzu's amber. Not blended — layered. As if the amber light is being absorbed into the Institute color scheme the longer they stay. Year 1: Institute palette dominant, amber only as external lighting. Year 3: amber beginning to warm the mid-tones of their equipment colors. Year 6: the equipment is Institute-coded but everything around it, including the ambient light the character moves through, has converted to Abzu amber fully. The character is a Institute-colored figure in an amber world.
+
+---
+
+## 7. Revised Palette
+
+Changes after reading the full challenge set.
+
+**Confirmed unchanged:**
+- K-type amber primary light: `#ffb234` (same as bar ambient, intentional — warmth is the signal for "social/inhabited/under observation")
+- Gas giant reflection: secondary amber, cooler, `#e0a870`
+- Mode 1 structural base: aged pale stone, `#c8bfa8`
+- Institute transient equipment palette: `#7a8fa8` (cool blue-grey, stands out against amber)
+
+**Revised:**
+- Fog tint: `#1a0c02` (was `#200c04` — deeper, more aqueous, consistent with Abzu naming. The fog at this system should feel like depth, not warmth)
+- Surface accent (watch location, shift-change zones): no change to hue, but reduce saturation by 15% — the watch location should read as slightly less vivid than the surrounding community spaces, as if the light there is being consumed rather than reflected
+- High-bleed transit visual effects: primary color during fog inversion `#b8d4e8` — a cool blue-grey that is the inverse of the Abzu amber, to read as a temperature drop, a direction, a signal from somewhere colder
+
+**New — the "Abzu upwelling" lighting gradient:**
+The ambient light in all Abzu Mode 2 and Mode 3 interior spaces should follow a vertical gradient: cooler amber (`#e0a870`) at the upper quarter of the screen, shifting to warmer amber-brown (`#c87840`) at the lower quarter. This is the gas giant reflection effect expressed as depth. It should be subtle — the player should not consciously register "the light comes from below." They should register "this place feels like it has a floor that matters."
+
+**One addition — the departure beat color:**
+When the transit resolves in the departure beat — the moment the shape becomes briefly legible — the color the shape reads against is `#0a1422`, near-black, slightly blue-shifted. This is the one place in the game where the Interstitium's background is visible as background rather than as transit noise. It should feel like looking out.
+
+---
+
+## Summary
+
+The name Abzu is right. It reframes the visual problem from "a place where people hold still" to "a place that runs deep." The palette implications are precise and bounded — primarily in lighting gradient and fog treatment, not in architectural or structural changes.
+
+All four challenges converge on the same structural commitments. The bidirectional circuit, the high-bleed connection, the door ambiguity, the non-resolution principle — these are locked. What remains is implementation specification, which is what this synthesis provides.
+
+The departure transit and the high-bleed visual grammar are now formalized as a single connected system. The shape in the transit is always the same shape. It is the same thing seen from different distances and at different levels of signal degradation. The player learns to read it at Abzu and retroactively understands every high-bleed gate they have ever transited.
+
+The perception tier spec for the shift change is the most implementation-complex element. It requires the fog system, thermal overlay, and monologue system to coordinate at the shift-change event. The systems are all committed. The integration is the build work.
+
+The Mode 3 Institute transient vocabulary is ready for NPC design to use. The visual transition from Year 1 to Year 6 is a timeline the player can read without being told.
+
+Present to the project lead.
diff --git a/docs/workshops/gj-6711-furthest-system/final-miri.md b/docs/workshops/gj-6711-furthest-system/final-miri.md
new file mode 100644
index 000000000..6442aca41
--- /dev/null
+++ b/docs/workshops/gj-6711-furthest-system/final-miri.md
@@ -0,0 +1,347 @@
+# GJ 6711 — Final Synthesis (Miri)
+
+**Role:** Worldbuilder & Setting Designer
+**Round:** Final — post-challenge, pre-lead presentation
+**Date:** 2026-03-16
+
+---
+
+## Prefatory Note
+
+All four challenges hold under pressure. There are no fundamental contradictions between
+them and no contradictions with existing canon. What follows is a synthesis and position
+document, not a summary. Where the team converged, I'm endorsing convergence. Where
+there are still open design questions, I'm taking a position. This is the final round
+before the project lead receives it.
+
+---
+
+## 1. The Name "Abzu"
+
+I want this. But I want it for specific worldbuilding reasons, and I need to flag the
+implications before endorsing it.
+
+Every other named system in the Reach draws from Portuguese, German, Afrikaans, or Dutch
+— the colonial and linguistic inheritance of the settlement waves (Waves 1 through 5).
+Those names are settlers' names. They reflect which communities had the ships, the
+capital, and the institutional weight to claim naming rights in the early Commonwealth
+centuries. The naming pattern is not neutral — it encodes who arrived first and who had
+the authority to put words on places.
+
+GJ 6711 received no such name. For 300 years it has been a catalog number. That is
+itself a signal: the community there has never sought official naming. They don't need
+the Reach to recognize them. They are not performing their existence to the institutions
+that assign names.
+
+If the project lead wants to name it Abzu now, the worldbuilding question is: who named
+it, and when?
+
+**The interpretation I'd endorse:** Abzu is not an official Concord Assembly designation
+and not a settlement-wave inheritance name. It is a name that originated WITHIN the
+community — possibly within the founding generation, possibly much later, possibly
+borrowed by a long-stay visitor with different cultural inheritance than the dominant
+settlement-wave demographics. The name propagated outward not through official channels
+but through travelers who heard it and carried it. Adams & Ford uses it. The Commission
+still uses the catalog number. The Assembly's records say GJ 6711.
+
+This creates a name that is itself a fragment of the vigil's character: the community
+gave this place a name from a tradition that precedes Western European settlement
+expansion by five thousand years. Sumerian — the domain of Enki, primordial deep, source
+of hidden springs, associated with wisdom and what lies beneath. Not the surface. The
+source.
+
+Setting note: using Abzu immediately signals that whoever named this place was reaching
+for something older and deeper than the Reach's standard naming inheritance. That is
+appropriate. The vigil is older than the Reach's categories. The name acknowledges it.
+
+**The originality check:** Abzu is an ancient mythological term, not a franchise coinage.
+There is no conflict with IP originality — this is genuine cultural inheritance being
+repurposed, not a franchise element being borrowed. The same legitimacy applies to the
+Reach using historical place names elsewhere. This is different from, say, naming a gate
+network "the Ring" or a precursor species "the Forerunners."
+
+**One constraint to track:** if Abzu is the community's internal name and it has leaked
+outward through travelers, then Adams & Ford correspondents before the third one would
+not have known it. The first and second correspondents wrote under the catalog number or
+under an informal traveler's name that may not have been Abzu. The name Abzu should
+appear in Reach circulation only within a specific time window — I'd suggest within the
+last 80–120 years, recent enough to not be universal, old enough for Adams & Ford to
+standardize it.
+
+**Position: endorse Abzu. Flag the naming source as community-internal with Sumerian
+etymology, not official designation. Track the propagation timeline.**
+
+---
+
+## 2. Points of Convergence
+
+The four challenges reached independent consensus on several positions. These are now,
+in my assessment, locked.
+
+**High-bleed = failed vigil.** All four challenges arrived here. Nigel, Araminta, Paula,
+and my own response all converged on the same structural reading: high-bleed gates are
+the Reach's distributed early-warning system for vigil failure, and nobody knows this
+except possibly the Veil Institute. This is the most important structural implication of
+the sealed envelope for the wider setting. It retroactively recontextualizes every
+high-bleed transit experience in the game. It is clean, internally consistent, and
+requires no modifications to existing canon. I am endorsing this as canon in Section 4.
+
+**The vigil predates the human community's tenure.** Paula (Option C), myself (implicitly),
+and Araminta all arrived at the same reading of the doors: whatever takes the other
+shifts was not brought by the founding settlers and is not something the founding settlers
+created. The 300-year vigil count is the human tenure of a watch that was already running.
+The gate was placed to bring human watchers into an existing arrangement. This is structural
+consensus and it changes the meaning of "the founding settlers were recruited by the
+situation" — they were recruited into a post, not to establish one.
+
+**The Institute knows something and has decided to manage it through deliberate ignorance.**
+All four challenges rejected the "the Institute knows nothing" option. The convergent
+reading: the Institute has the file, the file is classified at their highest tier, and
+the Institute's internal response is paralysis caused by factional disagreement rather
+than active management. They know GJ 6711 is anomalous. They do not know what the anomaly
+means. Their researcher going silent is classified data that fits no interpretive category
+their schema provides.
+
+**The player cannot solve Stillpoint.** All four challenges protected this. The non-resolution
+principle held under pressure from all four directions. The player accumulates experience,
+not proof. They file a report that is accurate and incomplete. The game does not confirm
+what they understood.
+
+**The endgame is autobiographical, not cosmological.** Nigel's phrasing: "they stop asking
+who is responsible and start asking what is being maintained." Paula's: "the cosmological
+mystery becomes autobiographical." This convergence is complete. The endgame turn at
+Stillpoint is not a revelation — it is a reorientation of the player's relationship to
+everything they have done.
+
+---
+
+## 3. The Inner Sealed Envelope — My Position for the Design Team
+
+I flagged this in my challenge response and I'm escalating it now with full conviction.
+
+The sealed envelope currently protects the mystery from the player. That is correct.
+But it also withholds the answer from the design team. That is a draft state, not a
+finished design. We are approaching implementation. The people building this location
+need to know what the vigil is actually watching.
+
+My position is not that the answer should be made player-facing. My position is that
+there must be a canonical answer, held internally, that everyone building Stillpoint
+is building toward. Without it:
+
+- The visual design team cannot know what to NOT show (Araminta's point, precisely
+  stated: the absence needs design as carefully as the presence)
+- The narrative team cannot know what the first correspondent's description was actually
+  failing to describe
+- The Gyre event system cannot know what to produce if the vigil lapses — because the
+  answer to "what breaks" depends entirely on what is being watched
+- The perception-tier system cannot calibrate what an Elevated player perceives at
+  Stillpoint without a referent
+
+After reading all four challenges, here is the internal canonical answer I would recommend
+we commit to. This is my synthesis position — not a demand, but a specific proposal to
+the project lead:
+
+**What is being watched is a point of contact between the Interstitium and normal space
+that cannot be sealed from either side.** It is not an object, not a creature, not a
+geological feature in any familiar sense. It is a boundary condition — a location where
+the Interstitium and observable space are in permanent adjacency without resolution into
+either. The vigil keeps this boundary coherent by providing continuous attention from
+the observable side. What the community is doing, functionally, is keeping one side of
+a door occupied. Not closed. Occupied. As long as someone is present and attending on
+the human side, the condition remains stable — neither intruding nor retreating. The
+watching is not containment. It is acknowledgment.
+
+This answer:
+- Is compatible with all four frames (astronomical, geological, perceptual, topological
+  — because a boundary condition between space and the Interstitium is all of these
+  simultaneously)
+- Explains why the non-human shift-takers participate — they are watching from the
+  other side of the same boundary, completing the circuit
+- Explains why "unknown if not watched" is the right framing — an unacknowledged
+  boundary condition does not produce a predictable outcome, it produces whatever the
+  Interstitium does when it is unobserved adjacent to normal space, which is the
+  definition of "unknown"
+- Explains why Elevated perception at Stillpoint would produce qualitatively different
+  experience than transit-based Interstitial perception — the player is experiencing
+  the boundary directly, not through a gate
+- Does not resolve the Builder mystery, the Threshold, or any of the game's larger
+  open questions
+
+This answer should live in an inner sealed envelope document. The outer envelope remains
+as written. The inner envelope provides what the building team needs without exposing
+anything to the player layer.
+
+---
+
+## 4. The High-Bleed Connection — Endorsement as Canon
+
+I endorse this. Fully.
+
+Nigel and Araminta arrived at it independently. Paula built the institutional implications.
+I had gestured toward it in my challenge response without fully committing. After reading
+all four, the convergence is too clean and too structurally productive to leave as
+implication.
+
+**Canonical position: high-bleed is the Interstitium's response to degraded or absent
+observation at a vigil system.** The bleed is not random. It does not correlate with gate
+distance, age, or transit frequency because those are not the relevant variables. The
+relevant variable is the integrity of whatever observational arrangement is associated
+with that gate's destination or its chain. The Veil Institute's pattern analysis cannot
+find the correlation because they do not have the concept of a vigil system. They are
+measuring the symptom — Interstitial anomaly intensity — without the category that would
+make the pattern legible.
+
+Implications that follow and are now locked:
+
+1. High-bleed gates in the game should, in principle, be traceable to a system in their
+   chain where something has gone wrong observationally. The design team need not make
+   this explicit in every case — but the architecture should be consistent. High-bleed
+   gates are not random.
+
+2. The Veil Institute's headquarters placement "near high-bleed Founder Gates" is
+   retroactively more sinister: they have been positioning themselves near the Reach's
+   most stressed observation posts without knowing that is what they are.
+
+3. An Elevated player who has reached Stillpoint and then transits a high-bleed gate
+   elsewhere in the Reach should, through the game's monologue system, be able to arrive
+   at the connection. Not through a journal entry that says "this gate is like Stillpoint."
+   Through a felt quality of recognition that the game does not explain.
+
+4. The mechanic Nigel proposes — that a player with sufficient knowledge and perception
+   tier might stabilize a high-bleed gate through sustained attention — is worth flagging
+   to the project lead as a potential late-game system. Not committing to it here, but
+   it follows directly from the canon and should not be foreclosed.
+
+---
+
+## 5. The Doors — Where I Land
+
+After reading all four positions, this is my final view on what takes a shift.
+
+I am not resolving it. That is not evasion — it is a deliberate structural choice with
+reasoning behind it.
+
+The three candidates (Builder manifestation; Threshold-adjacent transformed human;
+something pre-human to GJ 6711) are all load-bearing design options. But the convergent
+reading from Paula and my own Section 4 — that the vigil predates human tenure — changes
+the weighting. If the founding settlers were recruited into a post that was already
+established, then whatever was holding the watch before them was already there. This
+does not confirm "Option C: something that was always there." It simply means Option C
+cannot be ruled out by the founding settlers' arrival, because whatever is taking the
+other shifts predates the founding.
+
+Nigel's framing is the one I want to protect most carefully: "it emerged from the vigil
+the way a relationship emerges from sustained attention." This is not a description of
+a specific entity type — it is a description of a relational ontology. The thing that
+takes a shift is not a thing in the conventional sense. It is what the vigil relationship
+looks like from the other side. Whether that is a Builder manifestation, a Threshold
+entity, or something pre-human to the system is, from the player's perspective, genuinely
+undecidable — because all three would look the same from where the player stands.
+
+**What I'm committing to for the inner sealed envelope:**
+
+The non-human shift-takers are not discrete individuals and are not a species. They are
+expressions of the boundary condition being watched. The vigil, sustained long enough,
+produces them — or reveals them, or invites them into coherence from the Interstitium
+side. They take shifts because the vigil requires acknowledgment from both sides. The
+human watchers watch. The non-human shift-takers watch back. The circuit requires both.
+
+This is compatible with all three candidate explanations simultaneously, which is why it
+is the right internal answer: it does not foreclose any player-facing interpretation while
+giving the design team something specific to build toward.
+
+The visual design constraint Araminta established holds: the player never sees what takes
+the other shifts. The doors are physical evidence. Everything else is perception-scaled
+ambiguity. This is non-negotiable.
+
+---
+
+## 6. What Needs to Go Into the Revised Sealed Envelope
+
+The outer sealed envelope is a strong document. It needs six additions. These are not
+rewrites — they are insertions that give the building team what they currently lack.
+
+**Addition 1: The inner answer.**
+A subsection titled "Internal Canonical Position (Design Team Only)" that states what
+the vigil is actually watching. Use the boundary-condition framing from Section 3 above
+or a variant approved by the project lead. One paragraph. Locked.
+
+**Addition 2: The founding moment.**
+The sealed envelope says "they understood, at some point after arrival, that leaving
+would be abandonment." That formulation needs an internal anchor. The design team needs
+to know whether the founding moment was: a near-miss event (something changed when no
+one was watching); a perceptual event (someone stayed up through a doubled-light night
+and saw something); or a social event (the community collectively recognized the pull
+without any single precipitating incident). I'd recommend the perceptual event — a
+single founding-generation incident, recoverable only through the oldest community
+records, that the player can approach but never fully read. The community does not discuss
+it. Its name is in the records. The records themselves are tier 4 community knowledge.
+
+**Addition 3: The vigil predates human tenure.**
+A sentence that locks this explicitly: "The 300-year count is the human tenure. The
+vigil is older. The founding settlers were recruited into a post that had previous
+occupants." This changes the founding narrative from "they established a vigil" to
+"they took over a watch" and it is required for the doors to make architectural sense.
+
+**Addition 4: High-bleed is failed vigil.**
+One paragraph explicitly connecting high-bleed gate behavior to observation failure at
+vigil systems. This locks the connection as internal canon while keeping it
+player-discoverable rather than player-confirmed.
+
+**Addition 5: The Institute's file status.**
+The sealed envelope says the researcher is in year 6. It needs to add: the Institute
+has this file. The file is their highest classification tier. The file is locked because
+two factions within the Institute cannot agree on what it means — one faction reads it
+as confirmation that Builder contact is achievable and imminent; one faction reads it
+as confirmation that something dangerous has compromised their researcher. Neither
+faction is proposing to act. The file has been in contested classification for three
+years. Paula's contribution here is exactly right.
+
+**Addition 6: The recruitment trigger.**
+The envelope says "everyone who stays long enough is recruited." The building team needs
+a working threshold — not for player-facing content, but for designing the player's arc
+at Stillpoint. I'd recommend: the trigger is duration under the doubled-light environment
+combined with proximity to the watch location. Days produce the warmth-without-origin
+effect. Weeks produce the first perceptual anomalies (at Augmented tier and above).
+Months produce the qualitative shift. The player's arc is determined by how long they
+choose to stay. The game should not announce this. The player's monologue should shift
+registers without explanation.
+
+---
+
+## Summary
+
+**Abzu:** Endorse. Community-internal name with Sumerian etymology, not official
+designation. Track the propagation timeline.
+
+**Convergence:** High-bleed as failed vigil; vigil predates human tenure; the Institute
+knows and is paralyzed; the player cannot solve Stillpoint; the endgame is
+autobiographical. All four locked.
+
+**Inner sealed envelope:** Required before implementation. Boundary-condition framing
+for the watched thing. This is the most pressing outstanding item.
+
+**High-bleed canon:** Endorsed as locked canon. The correlation is real and the Veil
+Institute does not have the category to find it.
+
+**Doors:** The non-human shift-takers are expressions of the boundary condition from
+the Interstitium side. They are not a species or discrete individuals. The vigil is
+mutual and the doors are physical evidence that the community has built for what
+mutuality requires.
+
+**Revised sealed envelope additions:** Six items. All required. None are rewrites.
+The outer envelope language holds; the additions give the building team the specificity
+they currently lack.
+
+One last note for the project lead. Every person on this team, writing independently,
+arrived at the same endgame image: a player who has been everywhere in the Reach, who
+has learned to see through layers of information asymmetry and institutional concealment,
+who finally reaches hop 23 and discovers that the most important thing in the Reach is
+not a secret at all. It is a watch. It is people doing a job that has no formal description
+and no institutional recognition and no end date.
+
+The game has been training the player to look. Stillpoint is where the player learns
+that looking was never the point. Being present was.
+
+That image held under pressure from four different directions. It is the right endgame.
+Protect it.
diff --git a/docs/workshops/gj-6711-furthest-system/final-nigel.md b/docs/workshops/gj-6711-furthest-system/final-nigel.md
new file mode 100644
index 000000000..f70f3964d
--- /dev/null
+++ b/docs/workshops/gj-6711-furthest-system/final-nigel.md
@@ -0,0 +1,385 @@
+# GJ 6711 Final Synthesis — Nigel (Sandbox & Replayability)
+
+**Status:** Final round — pre-presentation to project lead
+
+---
+
+## 1. The Name: Abzu
+
+"Primordial deep beneath the earth. Domain of Enki. Source of all springs."
+
+That name does something to the metagaming layer that "Stillpoint" cannot. Stillpoint is
+descriptive — it tells the player what to expect (stillness, a stopping point, a place of
+rest). Abzu is dissonant. It is the oldest word in a universe of newer words. A player who
+knows their Sumerian mythology arrives with loaded expectations that the design can
+exploit. A player who doesn't know it arrives with something archaic and unplaceable that
+nonetheless communicates depth.
+
+More importantly: Abzu predates every other naming convention in the Reach. Commonwealth
+systems are named for catalog designations, stellar coordinates, settlers' names, political
+gestures. GJ 6711 as "Abzu" has no conventional etymology in the Reach's naming tradition.
+Someone named it and no one knows who, or when, or whether the name came first and the gate
+came after. That ambiguity is load-bearing.
+
+For replayability: a player who reaches Abzu on playthrough 1 and looks up the name comes
+back on playthrough 2 already primed. They've read about the primordial waters, the source
+beneath the world, Enki's domain of hidden wisdom. On their second approach, every piece of
+evidence they've already seen reorganizes. The name functions as a meta-layer key that
+enriches replay without being accessible through any in-game text. It rewards curiosity that
+the game doesn't require and doesn't reward any other way.
+
+For the metagaming question: the name is not spoiler-proof. But it's the right kind of
+spoiler. Knowing what Abzu means in mythology tells you the emotional register — something
+beneath, something old, something that was there before you arrived. It tells you NOTHING
+about the vigil, the doors, the non-human shift-takers, or what happens if you stay. The
+name creates correct expectations about texture while leaving the specific mechanics
+completely opaque.
+
+Position: adopt Abzu. Remove Stillpoint from the vocabulary. The official system name
+remains GJ 6711. "Abzu" is what the community calls it. No one outside the system knows
+why, and no one has thought to ask.
+
+---
+
+## 2. Points of Convergence
+
+All four challenge responses agree on the following. These are not contested:
+
+**The core mechanism holds.** "Observation is load-bearing" contradicts nothing in existing
+Builder/Interstitium/Gate canon. In every case it enriches rather than contradicts.
+Specifically: it provides a non-obvious explanation for the "no observed failures" gate
+stability claim, and it gives the "purposes beyond transit" canon its first concrete
+instantiation. The canon was waiting for this. It fits.
+
+**High-bleed gates as vigil-failure signals.** All four responses independently reached this
+conclusion. Miri, Paula, Nigel, Araminta — all four. Independently. That's a consensus, not
+a convergence. High-bleed gates are the distributed early-warning system for degraded vigils
+that nobody in the Reach has the conceptual vocabulary to read. The Veil Institute is sitting
+on top of this signal and doesn't know what it means. This is now formal canon.
+
+**Dead-end systems as possible watch posts.** The recontextualization is correct and should
+be managed carefully. Abzu is the only confirmed vigil system. Other dead-ends gain
+ambiguity without confirmation. "I can no longer rule it out" is the player state we're
+engineering, not "there are many of these." Miri's phrasing: the paranoia is the point.
+
+**The doors must remain ambiguous across all three candidate explanations.** Builder
+manifestation, Threshold-adjacent transformation, pre-human native presence — all three must
+remain simultaneously viable in all player-accessible content. The sealed envelope holds all
+three. Design work (threshold markings, architectural vocabulary, perception-tier reveals)
+must not narrow this. Araminta added the operational visual grammar; the principle is
+universally endorsed.
+
+**The inner sealed envelope is missing.** All four respondents independently identified the
+same gap: the design team needs the answer even though the player never receives it. What is
+being watched, what the founding settlers found, what the watch-change protocol is — these
+must be resolved internally. This is the most pressing action item from the stress test.
+
+**The Institute's file is locked by internal faction conflict.** Paula's formulation is the
+correct one: two Institute factions cannot agree on what Abzu means, so the file is
+classified at the highest tier and left alone. This gives the player an institutional seam
+to exploit and explains why the Institute hasn't acted on the researcher's six-year silence.
+
+---
+
+## 3. The Inner Sealed Envelope: What Is Being Watched
+
+Miri's call is correct and I'm seconding it: the design team cannot proceed to
+implementation with the player's ambiguity preserved all the way through. The sealed
+envelope protects the mystery from players. It should not protect the mystery from the
+people building the mystery.
+
+My position for the design team:
+
+The thing being watched is **a point of contact between normal space and the Interstitium
+that cannot be sealed, only observed**. It is not a physical object. It is not a creature.
+It is a condition — a place where the membrane between the Reach's ordinary space and the
+space the gates punch through is permanently thin. Observed, the condition remains stable:
+the thinness is contained, the Interstitium on the other side stays on the other side.
+Unobserved, the condition expands. Not explosively. Incrementally. Observed attention
+functions as a kind of pressure from this side that keeps the boundary held.
+
+This is the canonical answer. It is consistent with:
+- The Gyre event system (a lapse produces a local intrusion, not a catastrophe)
+- The Threshold (this is what the Threshold looks like at full resolution, from one meter
+  away, from the safe side — it's not an ascension state, it's a place)
+- The high-bleed gate connection (bleed is what the thinning looks like from the transit
+  side at other gates where the equivalent observation has degraded)
+- The doors (the non-human shift-takers are what the thin space produces when a vigil has
+  been in contact with it for 300 years — the third thing, as I framed it in my challenge
+  response — neither Builder nor human but the vigil's own product)
+
+The founding settlers found the thinness, understood it through the light environment
+before they had language for it, and realized that their presence was doing something. The
+formative event was not a catastrophe. It was a sustained period of watching — probably the
+first winter, when the community had nothing to do but attend to the strange light — during
+which something that had been quietly expanding pulled back. They didn't know what they were
+doing. They knew that something they were doing mattered.
+
+The watch-change protocol: the community has a shift schedule that runs continuously. During
+shift changes, there is a brief overlap period where both the outgoing and incoming watcher
+are present. This overlap has been maintained for 300 years because no one can remember
+whether the overlap is necessary or merely traditional, and no one is willing to find out.
+The non-human participants do not follow this schedule. Their shifts occur at intervals the
+community has learned to recognize without being able to predict — and when those shifts
+occur, the human watchers step back. They have always stepped back. It has always been fine.
+
+---
+
+## 4. The High-Bleed Connection: Formalization
+
+Araminta and I reached this independently. Both challenge responses identified it as
+the strongest structural implication in the sealed envelope. Here is the formal statement:
+
+**High-bleed Founder Gates are gates where the observation circuit is degraded or
+incomplete.** "Bleed" — the anomalous Interstitial effects experienced during transit,
+characterized as distorted sounds, visual artifacts, and a sense of being observed — is
+the phenomenological signature of insufficient vigil maintenance at some point in that
+gate's operational context.
+
+Formal corollary 1: The Veil Institute's headquarters is positioned near high-bleed gates
+because high-bleed gates are where the system is visibly stressed. The Institute is studying
+the symptom. They have not identified the cause because they lack the conceptual vocabulary
+for vigil mechanics — the vocabulary is held by the community at Abzu and is not
+transmissible without staying.
+
+Formal corollary 2: High-bleed gates are not random. They have a causal structure. In
+implementation, every high-bleed gate should be traceable — by a sufficiently determined
+player — to some observation deficit in its chain. The Institute's pattern analysis should
+be approaching this finding without completing it.
+
+Formal corollary 3: A player with sufficient tier and knowledge can theoretically stabilize
+a high-bleed gate by establishing and maintaining a vigil at the appropriate location. Not
+by hacking, not by physical intervention. By watching. This is a late-game mechanic that
+should be flagged for the design team — it's not in the sealed envelope and it needs a
+decision. I'm flagging it, not mandating it.
+
+Formal corollary 4 (Araminta's visual contribution, canonized here): The fog-of-war
+inversion during high-bleed transit — "as if something is looking at the player through
+their own perception system" — is not Builder curiosity. It is the thing at the watched
+location, leaking through, because the watch is thin. The player's experience of being
+observed during a high-bleed transit is the player being perceived by what needs watching.
+
+---
+
+## 5. The Doors: Final Position
+
+After reading all four responses, I stand by my challenge position with one addition.
+
+My position: the non-human shift-takers are what the vigil itself produced over 300 years
+of sustained contact with the thinness. Not Builders. Not Threshold-crossed humans. A third
+category. The vigil generated participants. The watching made something that watches.
+
+This is consistent with all three candidates the other respondents identified, because it
+doesn't exclude any of them — it describes what they have in common. Whether the
+shift-takers have Builder properties, whether they resemble what humans look like near the
+Threshold, whether they predate the human vigil by being native to the thinness itself —
+all of these can be simultaneously true of a third-category entity that emerged from 300
+years of contact. The candidates aren't mutually exclusive. They're different descriptions
+of the same emergence from different analytical angles.
+
+The operational implication: the shift-takers are not characters. They cannot be confronted,
+named, allied with, or defeated. They are a function with presence. The community's
+matter-of-fact accommodation of them — building taller doors, recognizing shift intervals,
+stepping back when needed — is the correct template for how the player should encounter
+this. Not with fear. Not with wonder that demands resolution. With the same
+matter-of-factness the community has.
+
+The monologue fires at the taller doors. It says something like: "These were built this
+size deliberately. Someone decided this was the right size and built accordingly." It does
+not speculate. The player speculates.
+
+Araminta's visual prescription is accepted and endorsed: perception-tier scaling for what
+the player can detect at shift changes, with the Elevated tier catching a thermal gradient
+and a quality-of-attention change that resolves to nothing when looked at directly. The
+player at Baseline sees architecture. The player at Elevated sees the reason, briefly, and
+then it's gone.
+
+---
+
+## 6. The Vigil/Lattice/Unbound Gap: Proposed Solution
+
+I flagged this in my challenge response and no one else addressed it. It needs a solution
+before Abzu can be built.
+
+The problem: the Reach's re-embodiment system means Abzu settlers can die and be
+re-embodied. But what happens to a watcher's accumulated vigil-understanding when they
+die? Is it transmissible? Does re-embodiment preserve it? And for Unbound characters —
+whose deaths are permanent — what does the vigil do with a watcher who can never come
+back?
+
+Proposed solution, three parts:
+
+**Part 1: Vigil-understanding is environmental, not personal.** The community at Abzu
+understands the vigil not because anyone taught them, but because long residence in the
+doubled-light environment near the thinness produces it. This means re-embodied settlers
+return to Abzu and the understanding comes back — not instantly, but within a period of
+re-acclimation. The vigil is not interrupted by individual deaths. The environment does
+the continuity work. The community's institutional rituals (shared meals, overlapping
+shifts, the accumulated practice of watching) maintain the environmental conditions that
+produce understanding in residents.
+
+**Part 2: Re-embodied watchers return different.** A watcher who dies and is re-embodied
+returns to Abzu as a newcomer in perceptual terms — they experience the warmth-without-origin
+again, they go through the recruitment curve again. But faster, because the community
+recognizes them and because something in the thinness recognizes them. The second recruitment
+is not the same as the first. It's shorter, stranger, and the watcher arrives at understanding
+from a different angle. This is a potential late-game experience for players who invest deeply
+enough to die and return.
+
+**Part 3: The Unbound question is resolved by the doors.** An Unbound watcher who dies
+keeping watch is not simply lost. The third-category entity — what the vigil produces —
+may include the functional residue of Unbound watchers who stayed long enough. Their death
+was permanent in the lattice sense. It was not permanent in the vigil sense. They became
+part of what watches. This is not confirmed to the player. But it is the canonical internal
+answer to the question the sealed envelope raised. The doors are taller because some of
+the non-human-sized shift-takers are what committed watchers become when the only thing
+taller than dying is watching.
+
+This is the darkest implication in the entire design. I'm not walking it back.
+
+---
+
+## 7. Per-Playstyle Hooks
+
+I flagged the tycoon gap. The other respondents didn't address this. Here are proposed
+hooks for all four playstyles that make the 23-hop journey to Abzu feel directed rather
+than arbitrary.
+
+**Tycoon (economic motivation)**
+
+The hook is not about what Abzu exports. It's about what the high-bleed gates are costing.
+
+Every high-bleed gate transit is a disruption to freight and passenger scheduling. The
+transit experience is degraded, cargo manifests come through with errors, insurance rates
+on high-bleed routes are elevated. A tycoon-playstyle player who has been building economic
+operations across the Reach has been paying the high-bleed premium for the whole game.
+
+The hook: someone — a shipping concern, a gate insurance underwriter, an economic analysis
+bureau — has noticed that high-bleed gate incidents cluster geographically and temporally.
+The pattern doesn't resolve within the economic system, but it's expensive enough that
+someone is paying to have it investigated. The tycoon player gets a contract. Follow the
+pattern. Find the source. The source is Abzu.
+
+When they arrive: the community has no commercial activity in the conventional sense because
+they're not oriented toward exchange. But what they have, in abundance, is something no
+amount of money has ever successfully purchased — a community with 300 years of unbroken
+institutional continuity, zero factional capture, and no debt to any interest in the Reach.
+The tycoon arrives expecting a resource extraction opportunity and finds the one thing they
+cannot buy. What they do with that realization is between them and the game.
+
+**Dating Sim (relational motivation)**
+
+The hook is a specific person who left.
+
+Someone the player has a relationship with — a contact, a companion, someone who matters —
+went to Abzu and didn't come back in the expected way. Not dead. Not missing. Still there.
+Still sending messages, but the messages changed. Became quieter. More inward. The player
+has been watching this change across the whole game and can't explain it. Abzu is where they
+find out.
+
+When they arrive: they find the person still there, still changed, unable to explain what
+happened in terms the player can easily accept. The relational question becomes: is the
+person you came for still the person you knew? The vigil doesn't answer this. The player
+has to decide whether the change is loss or growth, and whether they love the new version,
+and whether they stay.
+
+This hook also activates the Unbound death question: if the person who went to Abzu is
+Unbound, and they die while the player is there, what does that mean for what the player
+came to find?
+
+**Political Drama (power motivation)**
+
+The hook is the Institute's locked file and what unlocking it would be worth.
+
+A political drama player has been navigating faction conflict across the entire game. The
+Veil Institute is one of the major players — most information, least shared. The player has
+been trying to get leverage on the Institute for potentially the whole playthrough. The
+locked Abzu file is the leverage point.
+
+The hook: the Institute's internal faction conflict over the Abzu file has reached a crisis.
+One faction wants to act. One faction wants to contain. They've been paralyzed because
+neither side can act without the other learning. An Institute defector — or a political
+contact who's been watching the Institute — tips the player that the file exists, that it's
+locked, and that whoever gets to Abzu first and brings back something usable has the
+Institute by the throat.
+
+When they arrive: the political player finds something that cannot be weaponized in the
+conventional sense. You cannot turn the vigil into leverage. You cannot hold the community
+hostage. What you can do is file an Adams & Ford entry that changes what the Reach knows —
+or that changes what the Institute thinks the Reach knows. The political game at Abzu is
+about information architecture, not power plays. The player who came for leverage finds
+that leverage requires a kind of clarity the vigil won't provide, and has to decide whether
+to lie, tell the truth, or stay silent. Each option has consequences they can't fully predict.
+
+**Investigation (knowledge motivation)**
+
+This is the native hook — the investigation playstyle is already pointed at Abzu by the
+game's information structure. But it needs a specific entry point that feels earned rather
+than inevitable.
+
+The hook: the first Adams & Ford correspondent's entry exists in the database. The player
+finds it early — maybe at hop 3 or 4, in a transit lounge's shared archive. It's a
+professional, competent description of a frontier system that is somehow not quite right.
+All the information is present. Nothing is omitted. But the entry reads like a person
+describing something they experienced once and cannot get back to. The player flags it.
+
+Over the course of the game, they find the second correspondent's entry. Same quality —
+professional, competent, slightly off. They don't find the third correspondent's entry,
+because it was never filed. They find a placeholder in the Adams & Ford database: an
+assigned entry that was never submitted, for a correspondent who is still listed as active.
+That correspondent's location is GJ 6711.
+
+When they arrive: the investigative player knows they're walking into the scene of the
+third correspondent's disappearance-that-wasn't. They're also aware that they're now the
+person who will file the next entry. The game has been training them to notice what others
+missed. At Abzu, they discover that what was missed cannot be noticed its way to resolution.
+The investigation ends when the player files the entry and leaves. Or doesn't leave.
+
+---
+
+## Summary Position for the Project Lead
+
+**The sealed envelope holds.** All four respondents confirmed this independently.
+
+**Abzu is the right name.** Adopt it for the community's internal usage. It does work the
+design system can use and it does it without telling the player anything they can act on.
+
+**Six items require design team action before implementation:**
+
+1. The inner sealed envelope — write it. What the thinness is, the founding formative event,
+   the watch-change protocol. Not player-facing. Foundational.
+2. Adopt the inner sealed position on the thinness formally and circulate it as restricted
+   internal canon.
+3. The high-bleed/vigil-failure connection is now formal canon. The architecture needs to
+   support traceable high-bleed causes.
+4. The Unbound watcher / lattice interaction is resolved as above. Flag for systems design.
+5. Per-playstyle hooks need to be reviewed by Paula for political drama and narrative
+   coherence, and by Miri for setting consistency on the relational hook.
+6. The Adams & Ford entry format needs definition — what categories exist, what the
+   Stillpoint entry specifically cannot fill, what that gap communicates.
+
+**The replayability case for Abzu:**
+
+GJ 6711 achieves interpretive inexhaustibility without procedural variation. The same
+location, on every playthrough, generates a different experience because the player
+approaches it with a different theory. The Adams & Ford entry propagation loop ensures
+that theories from playthrough 1 pollute the approach conditions of playthrough 2 in
+specific and unpredictable ways. Two players comparing their Abzu experiences describe
+completely different visits, even though the location is static. That is the comparison
+test passing.
+
+It also rewards return. The player who reaches Abzu and leaves knows they didn't solve it.
+On playthrough 2, they come back. They find the same community, the same doors, the same
+light. They find that what they remember was incomplete. Not because the place changed.
+Because they did.
+
+That's not just an endgame. That's a reason to start over.
+
+And the replayability EXPLODES when you consider what they do differently on that second
+run to get there — different playstyle, different route, different theory accumulated across
+23 hops. The vigil doesn't change. But what they bring to it does. And what they bring to
+it is exactly what the vigil requires: sustained, changed attention. The game that trains
+the player to see has been training them for this specific moment, and they didn't know it
+until they were already there.
+
+Abzu is where the game earns everything it asked for.
diff --git a/docs/workshops/gj-6711-furthest-system/final-paula.md b/docs/workshops/gj-6711-furthest-system/final-paula.md
new file mode 100644
index 000000000..f68ffdb0e
--- /dev/null
+++ b/docs/workshops/gj-6711-furthest-system/final-paula.md
@@ -0,0 +1,357 @@
+# GJ 6711 — Final Synthesis (Paula)
+
+**Round:** Post-challenge synthesis, pre-project-lead presentation
+**Date:** 2026-03-16
+
+---
+
+## 1. The Name: Abzu
+
+"Stillpoint" was a working placeholder that described function. "Abzu" is something
+different — it is a claim about what is there.
+
+The Sumerian primordial deep beneath the earth. Domain of Enki, god of wisdom and
+hidden knowledge. The source from which all springs rise. The underworld that is not
+a place of death but a place of origin.
+
+The honest truth is that no one in the Settled Reach would name a system this. The
+naming conventions across the Reach are practical: survey designations, founder
+surnames, geographic descriptors, Wave-era transit codes. A system named for Sumerian
+cosmology is an anomaly that announces itself. It tells us something about the founding
+settlers that nothing else in the sealed envelope tells us.
+
+They did not arrive and say: we will call this place the Observation Post, or the Vigil
+Station, or the Watchers' Settlement. They named it for the hidden source beneath
+everything. That is not the name of people who found something and stayed. That is the
+name of people who recognized what they found — who arrived at GJ 6711 and felt, with
+the specific quality of attention the doubled light produces, that they were above
+something that had always been there and had always required witnesses.
+
+**What "Abzu" does to the political/narrative layer:**
+
+It marks the founding settlers as people with deep cultural memory reaching back before
+the Commonwealth, before the Reach, possibly before the first wave of post-Commonwealth
+settlement. They had a conceptual vocabulary for what they found because they brought
+one. A community that names its home Abzu in Wave 2 or Wave 3 is a community that
+carried ancient cosmology as a working lens — not as religion, but as recognition.
+
+This has three design implications:
+
+First, the founding history of GJ 6711 is not a blank. Somewhere in the accessible
+archives, there will be a record of the founding party's origin culture. The name is a
+clue about who they were, not just what they found.
+
+Second, the name creates a silence threshold that is specific. An investigator who knows
+enough pre-Commonwealth cultural history to recognize "Abzu" immediately understands
+that the founding settlers knew what they were looking at. That is information asymmetry
+at the naming layer — the name rewards the player who arrives with the right knowledge.
+Most players will pass through and file it under "unusual frontier nomenclature." A
+player who recognizes it arrives with a different frame.
+
+Third, the name is the most durable signal in the whole system. The founding records
+may be partially sealed. The community may be unreachable for investigation. But the
+name is on every transit manifest, every Commission report, every Adams & Ford entry.
+It is the one thing the vigil community cannot keep quiet. They named it honestly, three
+hundred years ago, and the name has been propagating through the Reach ever since.
+
+**Recommendation:** Accept "Abzu" as the canonical name. It does more work than
+"Stillpoint" — it is a mystery the player can investigate independently of the vigil,
+and one that rewards cultural knowledge. The name is part of the evidence trail.
+
+---
+
+## 2. Points of Convergence
+
+All four challenges found the same things load-bearing. This is the team's consensus
+ground and it should not be reopened.
+
+**What we all agreed on:**
+
+| Point | All four responses | Notes |
+|-------|-------------------|-------|
+| "Observation is load-bearing" is canon-compatible | Yes, unanimously | No contradictions found; several enrichments |
+| High-bleed gates = failed/degraded vigil signal | Endorsed by all four | Miri, Nigel, Araminta, Paula all arrived independently |
+| The doors are the most important detail | Universal | Miri, Nigel, Araminta, me — all flagged this as the load-bearing element |
+| The sealed envelope needs an inner layer | Unanimous | The design team needs answers the player never receives |
+| The Threshold connection is real and underdeveloped | All four | Vigil as Threshold-approach, not Threshold-crossing |
+| The Institute researcher going native is politically significant | All four, different angles | The file is real, the Institute's response is a design gap |
+| Community knowledge has a gradient | Me and Miri | Recent recruits more articulate about surface than founders |
+| Endgame is changed relationship to knowledge, not revelation | Universal | The player cannot solve Stillpoint |
+| The non-resolution principle must be protected | All four | Don't collapse the doors onto a single answer |
+
+**What needs to go into the design record as settled:**
+
+High-bleed gates are the distributed signal system for vigil failure. This is not a
+maybe. Four independent analyses arrived at the same conclusion from different angles
+(canon compatibility, visual design, systems, political narrative). The Veil Institute's
+headquarters placement near high-bleed gates is retroactively significant. This should
+be formally closed as a design decision, not left as an implication.
+
+---
+
+## 3. The Inner Sealed Envelope
+
+Miri names this most precisely: the current sealed envelope protects the mystery from
+the player at the cost of the design team's clarity. That is a draft state, not a
+finished document.
+
+**What is being watched?**
+
+I will not pretend this question has an obvious answer, but I will name what the
+evidence points toward.
+
+The four frames (astronomical, geological, perceptual, topological) are described as
+partial views of one function. The function the envelope calls "this place needs
+witnesses" is operational. The question is what kind of thing requires witnesses to
+remain in a state that can be coexisted with.
+
+My position: the thing being watched is a contact point — a location where the
+Interstitium is not separated from ordinary space by the gate mechanism but by
+something older and more fragile. Not a gate. Not a Gyre event site. A place where
+the boundary is thin enough that it has always required acknowledgment from this side
+to remain a boundary at all. The vigil isn't preventing entry. It's maintaining the
+ontological distinction between there and here. Without the watch, the distinction
+does not collapse violently. It simply becomes unclear. And what is unclear becomes
+unnavigable, unpredictable, and eventually uncoexistable with.
+
+This framing makes all four candidate consequences (Gyre event, topological instability,
+perceptual fracture, gate behavior change) simultaneously true at different scales,
+which is what the envelope intended. It also makes Nigel's best candidate ("the thing's
+ontological status becomes undefined in a way human cognition can't process") the
+canonical failure mode — and that is the version that best preserves "unknown if not
+watched" as a meaningful design constraint rather than a placeholder.
+
+**The inner envelope should specify:**
+
+- What the founding settlers found: not a discovery but a recognition. They arrived,
+  the doubled light produced the quality of attention the envelope describes, and
+  something about that attention revealed to them that they were standing above the
+  contact point. The formative event was not dramatic. It was the slow understanding
+  that the boundary was thin here and attention was what held it.
+
+- The watch-change protocol: scheduled, not improvised. The community has 300 years
+  of operational knowledge. The non-human shift-takers participate in a rotation the
+  human watchers trust. The humans do not know what the other participants are
+  experiencing. They know the schedule holds.
+
+- The scope of vigil failure: the contact point becoming unclear propagates outward
+  through the gate network because the network itself has always depended on the
+  stability the Abzu contact point provides at its far end. How far it propagates
+  before attenuating is the number the Institute's analysts cannot derive from their
+  data because they do not know the cause.
+
+---
+
+## 4. High-Bleed Connection: Bleed = Failed Vigil
+
+**Endorsed as canon.**
+
+The convergence across all four challenges on this point is too complete to ignore. The
+pattern of which gates are high-bleed "doesn't correlate with distance, age, or any
+other measurable variable" — that is an open problem the existing canon left
+deliberately unresolved. The vigil framework closes it with a clean, internally
+consistent explanation that enriches rather than constrains existing content.
+
+The specific formulation I'd carry forward: high-bleed is the Interstitium's response
+to an observation circuit that is incomplete, degraded, or failing. Gates are high-bleed
+because something that needs watching in an adjacent system is not being watched
+adequately. The degree of bleed correlates with the degree of observational failure,
+not with the gate's physical properties.
+
+This has one design consequence that should be locked alongside the bleed canon: the
+Institute's choice to locate its headquarters near high-bleed gates is not incidental.
+They made the right call for the wrong reason. They thought high-bleed gates were the
+most interesting study sites. They were correct. They were interesting because they
+were diagnostic. The Institute has been sitting next to the Reach's early-warning
+system for decades without understanding what the system was warning about.
+
+The player who reaches Abzu and carries this back to their understanding of the
+Institute's headquarters location has one of the most disquieting realizations in the
+game: the people tasked with understanding the infrastructure are downstream of a
+signal they cannot read.
+
+---
+
+## 5. The Doors
+
+Four positions read. Here is where I land.
+
+The three candidates — Builder manifestation, Threshold-crossed humans, pre-existing
+non-human inhabitants — must remain simultaneously viable in all player-facing content.
+That is not hedging. It is the correct design position. The doors are physical evidence
+that the vigil includes non-human participants. Collapsing that onto a single explanation
+is the single fastest way to make Abzu feel like a mystery-game with a solution rather
+than an endgame with a question.
+
+**However, the inner sealed envelope needs a working theory.**
+
+My position: Option C has the most structural weight (I argued this in my original
+challenge and the stress test did not dislodge it). The vigil predates human presence
+at GJ 6711. The 300-year count is the human tenure, not the vigil's age. The founding
+settlers were not recruited into an empty situation — they were recruited into a
+rotation that had prior participants. The gate was built to bring humans to an existing
+watch, possibly because prior watchers had become something the gate network could no
+longer easily access. This is Araminta's "built for who?" question and she asked it
+precisely.
+
+The reason Option C has structural weight is that it makes the founding settlers'
+rapid accommodation explicable. They didn't discover and then slowly understand. They
+arrived, felt the quality of attention the doubled light produces, and recognized that
+the doors were already the right size for what uses them. The accommodation was fast
+because the situation had been set up for them.
+
+**What takes a shift:**
+
+I will not name it. Naming it ends it. The design team needs to know that whatever
+takes the other shifts is not a character, not a Builder in the canonical sense, not
+a prior human who changed. It is a participant in the same vigil that the community
+maintains — present because the vigil requires participants, functional because the
+watch requires watchers. The founding settlers built for it. The community does not
+speak of it not because it is frightening but because what you build doors for
+eventually becomes unremarkable.
+
+That last sentence is the most disturbing thing in this document. It should be
+preserved.
+
+**Araminta's visual spec for the doors is final:**
+
+Baseline perceives architecture that does not fit. Augmented perceives the rhythm —
+gaps in the institutional schedule, the watch timing, the absence where something is.
+Elevated perceives the quality-of-attention change at shift change. Monologue fires.
+Says nothing explicit. The player at Elevated arriving at shift-change sees: a change
+in how the room holds itself, a thermal gradient with no source, a perception boundary
+that was somewhere and then was somewhere else. That is sufficient. Do not design
+beyond that.
+
+---
+
+## 6. The Institute's File
+
+All four challenges flagged this. Let me close it.
+
+**What the Institute knows:**
+
+The Institute knows that Abzu is anomalous. They have classified everything from
+Abzu at their highest restriction level. The pattern of researcher retention is in
+their files — not framed as researcher conversion, but as researcher dropout from
+rotation. They have noticed the pattern. They have not agreed on what it means. This
+is Miri's option (b): they know the researchers become permanent, they classify the
+outcome, and they may rely on it quietly without understanding its mechanism.
+
+**What the Institute does not know:**
+
+They do not know the vigil is the mechanism. They think psychological attachment to
+the field site explains the retention. They think "gone native" is the complete
+description. Their internal factional conflict — contact vs. containment — has not
+resolved on Abzu precisely because neither faction has a conceptual vocabulary for
+"the situation recruits participants." Contact faction sees data suggesting something
+important is happening there. Containment faction sees data suggesting researchers who
+go there cannot leave and recommends ending all assignments to GJ 6711. The file is
+locked because neither faction can get the other to agree on what the lock means.
+
+**What the Institute suspects:**
+
+That the Abzu file is one of the most significant documents in their archive. That
+"what it means" is a question that will eventually force a resolution to their internal
+conflict. That the researcher now in year 6 is producing information — the nature of
+which is unclear — that should not be classified at standard research output levels.
+Some senior Institute archivists suspect the file is not about research at all. They do
+not know what it is about instead.
+
+**The design consequence:**
+
+The player who reaches Abzu can become, depending on what they choose to do with the
+Adams & Ford entry and their knowledge of Institute politics, one of the following:
+a whistleblower with a specific target; an asset either Institute faction wants to
+manage; a threat to the institutional status quo on the Abzu file; or simply another
+observer who has been added to the vigil's growing record of inadequate descriptions.
+All four should be viable player positions. The Institute's locked file is the
+institutional seam to exploit.
+
+---
+
+## 7. What Needs to Go into the Revised Sealed Envelope
+
+The current sealed envelope is correct in what it says. It is insufficient in what it
+does not say. Specifically, the design team needs internal canon on the following seven
+points — none of which should appear in player-facing content:
+
+**1. The name origin.**
+The founding settlers came from a cultural tradition with pre-Commonwealth roots that
+included the concept of the primordial deep. The name Abzu was given within the first
+generation of settlement. It was not formal at first. It became official before the
+end of the founding century. The Commission records show "GJ 6711 (local designation:
+Abzu)" from approximately 200 years ago. This means the name circulates but is treated
+as a frontier peculiarity, not a signal.
+
+**2. The formation event.**
+The founding settlers understood what they were above within the first decade. There
+was no singular discovery event. There was a slow understanding, produced by the
+quality of attention the doubled light generates, that something beneath the attention
+had always required it. The founding memory is not a story about what they found. It
+is a story about a gradual change in what they understood themselves to be doing by
+staying.
+
+**3. The contact point.**
+The thing being watched is a point where the Interstitium is not separated from
+ordinary space by a gate but by a more fragile and older distinction. The vigil
+maintains that distinction. Failure of the vigil does not produce an invasion. It
+produces an ontological ambiguity that propagates outward from the contact point
+through the gate network, producing high-bleed events at increasing remove until the
+ambiguity attenuates or is resolved.
+
+**4. The non-human shift-takers.**
+The vigil predates human presence at Abzu. The non-human participants were not brought
+by the founding settlers and are not Builder manifestations in the conventional sense.
+They are participants the prior watch included. The founding settlers were recruited
+into an existing rotation. The doors were built taller because the community
+accommodated what the rotation required. The community does not speak of the non-human
+participants not because they are frightening but because they are part of the vigil
+and the vigil does not require explanation to the people who keep it.
+
+**5. The Institute's internal position.**
+The Institute file on Abzu is locked at director level. Contact faction and containment
+faction have not resolved on what the Abzu data means. The researcher in year 6 is
+producing reports that are classified immediately upon receipt. The senior archivist
+who manages the Abzu file has requested twice in the last decade that the director
+authorize a full investigation. Both requests were tabled. The file is the most
+significant unresolved item in the Institute's active archive.
+
+**6. The near-miss record.**
+There has been one documented near-miss in the 300-year vigil history. It occurred
+approximately 140 years ago during a period of population decline following a
+Commission quarantine order (unrelated cause — a disease event). The vigil thinned for
+approximately 72 hours. The Veil Institute's Interstitial monitoring arrays recorded an
+anomaly during that window. The anomaly is in their archive. It is classified. The
+Abzu community has no external record of the near-miss. Their internal records describe
+it as "the thinning." The oldest families know. No one else does.
+
+**7. The player's recruitment threshold.**
+Recruitment is not triggered by duration alone. It is triggered by the quality of
+attention the player has developed — proxied by perception tier. A Baseline player can
+stay indefinitely and remain unrecruited in the vigil sense, though the community's
+warmth will intensify. An Augmented player who stays more than a few weeks begins to
+feel the pull. A Transcendent or Elevated player may begin to understand within days.
+The recruitment is not coercive. The vigil is not malevolent. It is a contact point
+that requires witnesses, and some visitors arrive already capable of witnessing. Those
+visitors feel it faster.
+
+---
+
+## Final Note
+
+After reading all four challenges, my confidence in the sealed envelope has increased
+on the mechanism and decreased on the completeness. The mechanism holds. The envelope
+is a draft of a design document, not a finished one. The inner sealed envelope is the
+work that still needs to happen.
+
+The name Abzu is the project lead's best contribution to this workshop. It changed what
+the founding settlers are — from people who found something they couldn't explain to
+people who found something they recognized. That distinction is the difference between
+a mystery and a reckoning, and this endgame should be a reckoning.
+
+The player cannot solve Abzu. But they can recognize it. The founding settlers did.
+That is the most important structural truth in the whole design, and it was sitting
+inside the name the whole time.
+
+Present that to the project lead.