- T-1070: scaffold_bodies.py heightmap link now conditional (bake criteria per import_heightmaps.py); surgical removal of the dead image line from all 2,131 body pages lacking the file (267 with the file keep theirs) - T-1071: 26 real link breaks fixed (knowledge/→concepts/, pre-governance decision anchors, 9 phantom catalog companions unlinked, cygni relink to the corporation page, wrong design-doc path); wiki/index.md counts fixed (301 systems) + Economics nav section; corporations/index.md regenerated from frontmatter (all 155, tier1.toml grouping — corrects 4 misfiled tier-1 corps); 25 orphaned station GTTRs linked from 11 system pages (own ##-heading so atlas sync cannot absorb it); GOVERNANCE.md + star-system template rewritten to the generated model (DB owns structured fields, wiki owns prose); triangles/index.md added - Sol markers conversion REVERTED before commit: atlas_viewer.gd:433 still renders the legacy geometry schema, so conversion would drop Sol's Atlas overlays — split to T-1073 (convert together with the client read path) Broken relative links: 2,180 → 25 (all remaining are intentional _templates/ placeholders). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
24 KiB
title, description, slug, category, status, created, updated, members, triangle_type, social_sites, tags, decision_refs, cross_refs
| title | description | slug | category | status | created | updated | members | triangle_type | social_sites | tags | decision_refs | cross_refs | |||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Hub Power | Triangle 1 (shift supervisor / THE FRIEND / ring coordinator) — volume escalation fork with three smuggler paths that change investigation timing and observability | hub-power | triangle | canonical | 2026-02-12 | 2026-02-13 |
|
entangled |
|
|
Triangle 1: Hub Power — Volume Escalation Fork
Triangle: Shift Supervisor / THE FRIEND / Ring Coordinator Fork Type: Smuggler decision (3 paths, self-contained) Trigger: Ring coordinator's escalation demand, delivered by on-station coordinator Ticket: #377 Decision Reference: D-053 / A-17 (self-contained forks)
1. Triangle Overview
Triangle 1 is the hub's power structure under pressure. The shift supervisor has positional authority on the floor but takes operational orders from the ring coordinator (off-stage) through intermediaries. THE FRIEND (dock worker) is caught between their immediate boss and the off-station coordinator who brought them into the ring. The triangle's resting tension: the ring coordinator pushes for higher volume, the shift supervisor wants stability, THE FRIEND wants everyone to calm down.
The Volume Escalation Fork activates this tension. The ring coordinator demands a double-volume shipment. The smuggler — positioned between all three — must decide how to handle it. The choice reshapes the triangle's internal dynamics and changes what the detective can observe, without altering what the detective ultimately discovers. All three paths lead to the ring. The fork changes when and how.
NPCs involved:
- Ring Coordinator (Off-Stage, GHOST+HANDLER): Manages off-station coordination. Present only through lattice messages.
- Shift Supervisor (Tier 2, SYSTEM+OPERATOR): Adjusts shift schedules to create coverage gaps. Takes a cut. Terrified of escalation.
- THE FRIEND (Tier 1, FRIEND+OPERATOR): Dock worker. Caught between the ring coordinator and the shift supervisor. Secretly trying to exit the ring.
- On-Station Coordinator (Tier 2, THRESHOLD+HANDLER): Delivers the ring coordinator's message to the smuggler.
2. Trigger: The Escalation Demand
Context
Minutes 5-10 of the vertical slice. The on-station coordinator approaches the smuggler during a routine shift at the logistics hub. There is a lattice message from the ring coordinator. The next shipment is double volume. More hands and wider timing windows are needed. The shift supervisor has to adjust the schedule to create a bigger coverage gap. The smuggler is asked to help convince the shift supervisor — or handle the extra volume personally.
The Lattice Message (Ring Coordinator to THE FRIEND, relayed through on-station coordinator)
Ring coordinator's voice: direct, authoritative, strategic. Efficient — no wasted words, no sentiment that isn't load-bearing.
Next cycle, we're doubling the load. Two containers instead of one, same transit window. I've already confirmed with the supply side — it's handled.
I need the shift supervisor to widen the gap by forty minutes. Night transition, not day. Tell them it's temporary. Tell them whatever they need to hear.
Get your friend involved. The one who's good with routing. I trust your judgment on people — always have. But this shipment doesn't wait.
The money's there. Enough for everyone to feel it. The shift supervisor gets the usual plus fifteen percent. Your crew splits the operational bonus.
Don't let the shift supervisor talk out of this. Worries too much about things that haven't happened yet. We've run bigger loads through worse windows. This is manageable.
I'll check in after transit. Stay sharp.
Authoring notes: "I trust your judgment on people" is genuine and instrumentalizing simultaneously — the ring coordinator's praise functions as both compliment and directive. The message is 6 lines of authored content (excluding the sign-off).
On-Station Coordinator's Delivery
The on-station coordinator approaches the smuggler at the hub, low voice, professional demeanor shifted to operational mode.
"Message from upstream. They want to double the next run. Need the shift supervisor to stretch the window — forty minutes, night shift transition. And they want you on routing. Here."
Passes the lattice message (or relays its contents verbally, depending on operational security context).
"Read it. Then we need to talk about the shift supervisor."
3. The Decision Fork
The smuggler has three options. Each is self-contained within Triangle 1 — no cross-triangle cascade per D-053 / A-17.
Path A: Side with the Ring Coordinator (Escalate)
Decision trigger: The smuggler agrees to help push the double shipment through. Convinces the shift supervisor to widen the window, takes on the extra routing work, follows the ring coordinator's plan.
NPC Responses
Shift supervisor reaction — resentful compliance, anxiety spiking:
"Forty minutes. You're asking me to leave a forty-minute hole in the night rotation. Do you know what that looks like to anyone paying attention?"
"Fine. Fine. I'll move the south bay crew and pull night cover from elsewhere. But if this blows up, I was never part of this conversation."
"Another 'adjustment.' Every cycle it's another adjustment. One day there won't be anything left to adjust."
THE FRIEND reaction — relief mixed with unease:
"They got their way. Alright. At least the pressure's off for now — won't be messaging me every hour."
"You sure about this? Double volume through one window... that's a lot of containers to explain if someone's watching."
Ring coordinator follow-up message (post-shipment, lattice):
"Clean run. Good work. Tell the shift supervisor they did fine — and there's a bonus. People work better when they're not afraid."
Detective Consequences
The investigation accelerates. The shift supervisor's anxiety produces observable disruption:
- Manifest discrepancies spike (schedule reworks are visible; the freight scheduler notices).
- The shift supervisor's behavior becomes erratic — clipped responses, avoidance of the break room during ring operations, nervous schedule adjustments.
- The detective reads organizational stress:
"The shift supervisor changed the night rotation. Third time this week. Two workers reassigned without explanation. The freight scheduler has noticed too — manifest revision rate is tracking the schedule changes."
"Manifest revisions are up forty percent since last cycle. The shift supervisor is reprocessing more than the freight volume justifies."
Mechanical Outcomes
| Attribute | Change |
|---|---|
exposure_risk |
Increases globally for the ring |
cover_integrity (ring) |
Drops to "thin" |
Shift supervisor behavior_flags |
"nervous,schedule_changes,evasive" |
Shift supervisor position_integrity |
"thin" |
THE FRIEND behavior_flags |
Unchanged (pressure relieved) |
| Wow moment #2 (Character's Eye) | Triggers EARLIER in timeline |
Smuggler Monologue
"The ring coordinator's money. The shift supervisor's schedule. My routing. Everybody's got their piece. ...The shift supervisor looked like they wanted to throw up when I told them."
"More volume means more exposure. But the ring coordinator doesn't think about exposure — they think about throughput. And now I'm thinking like them."
"THE FRIEND is breathing easier. That's something. One less thing eating at them."
Path B: Side with the Shift Supervisor (Stabilize)
Decision trigger: The smuggler backs the shift supervisor's position. Rejects or delays the double shipment. Tells the on-station coordinator (or the ring coordinator through them) that the window can't support double volume without unacceptable risk.
NPC Responses
Shift supervisor reaction — surprised relief, cautious gratitude:
"You told them no? ...I didn't think anyone told the coordinator no."
"Good. The schedule stays clean. Nobody has to explain anything to anyone. That's how it should work."
"Just — don't expect them to forget this. The coordinator doesn't forget when people push back."
THE FRIEND reaction — increased anxiety, pressure redirected:
"They're not going to like this. They'll go around us — straight to me. And I can't... it's harder when they're asking directly."
"You did the right thing. I think. But this is going to become my problem now."
Ring coordinator follow-up message (lattice, to THE FRIEND directly — the smuggler hears about it through THE FRIEND):
"Your friend made a decision. I respect that. But the shipment still needs to move. You and I need to talk about alternatives. Contact me tonight."
Detective Consequences
The investigation slows. The hub runs quiet. But THE FRIEND's internal pressure builds and produces different tells:
- Fewer manifest discrepancies (the shift supervisor's schedule stays clean).
- THE FRIEND's distraction increases — more lattice checking, shortened conversations, visible tension without an organizational cause.
- The detective reads personal stress, not organizational disruption:
"The hub's been quiet. But the dock worker — they've checked their lattice eleven times this shift. That's not work communication. That's someone waiting for something they don't want to arrive."
"No schedule anomalies this cycle. The shift supervisor's relaxed. But the dock worker — carrying something. Personal? Professional? Filing it."
Mechanical Outcomes
| Attribute | Change |
|---|---|
exposure_risk |
Stays low (ring remains quiet) |
cover_integrity (ring) |
Unchanged — "solid" |
Shift supervisor behavior_flags |
"reliable,punctual" (baseline restored) |
THE FRIEND behavior_flags |
Escalates faster: "lattice_checking,distracted,evasive" |
THE FRIEND trust_level (from ring coordinator) |
Drops — coordinator applies pressure directly |
| THE FRIEND contradiction | Hits HARDER (under more personal strain, tells amplify) |
Smuggler Monologue
"The shift supervisor can breathe. The schedule's clean. ...So why do I feel like I just made this worse?"
"THE FRIEND's been on their lattice all shift. The coordinator called them directly. I took the pressure off the shift supervisor and dropped it straight onto THE FRIEND."
"I said no to protect the operation. But THE FRIEND's the one paying for it."
Path C: Mediate (Compromise)
Decision trigger: The smuggler proposes a middle ground — half the volume increase, phased across two shipments instead of one. Neither side gets what they want. The smuggler positions it as operational prudence.
NPC Responses
Shift supervisor reaction — temporarily calmed, skeptical:
"Half volume. Phased. ...That's something I can work with. Twenty minutes instead of forty. Tighter, but doable."
"Don't tell me this is the new normal. One compromise turns into two, and then the coordinator is running double loads through my schedule anyway."
THE FRIEND reaction — confused, uncertain:
"Half? They asked for double and you're offering half? They're going to think you don't trust them."
"I don't know. Maybe it works. But the coordinator doesn't do 'maybe.' They do yes or no."
Ring coordinator follow-up message (lattice, to THE FRIEND — cooler tone):
"Half volume, phased. Your friend's being careful. I can respect careful — up to a point. But careful doesn't move product, and product is what keeps everyone paid. We'll try it this way. Once. Then we revisit."
Detective Consequences
The investigation reads organizational confusion. Mixed signals — some disruption, then quiet, then disruption again. The detective reads this accurately as internal disagreement:
"Something's off. Last night extra cargo, tonight normal. There's no pattern, and that's the pattern."
"Inconsistent operational tempo. If someone's running an operation through this hub, they're either changing methods or arguing about them. Either way — disorganization is observable."
Mechanical Outcomes
| Attribute | Change |
|---|---|
exposure_risk |
Moderate (some exposure, not full) |
cover_integrity (ring) |
Slightly degraded: "solid" to "thin" (marginal) |
Smuggler operational_trust (from ring coordinator) |
Drops — coordinator loses confidence in the smuggler |
Shift supervisor behavior_flags |
"cautious" (mild stress, manageable) |
THE FRIEND behavior_flags |
"uncertain,distracted" |
| Second decision point | Creates a follow-up fork later in timeline (see implementation note below) |
Implementation note: Path C's deferred second decision point (when the ring coordinator revisits after the one-cycle trial) requires a follow-up fork that is not specified in this document. Options: (1) scope the follow-up fork as a separate ticket, (2) let the trial period expire unresolved within the session timeline, treating the unresolved tension as authored ambiguity. The self-containment rule (Section 6) applies — this deferred fork must not gate other triangles.
Smuggler Monologue
"Split the difference. Half now, half later. Nobody's happy, but nobody's exposed. ...The coordinator is going to remember this."
"THE FRIEND looked at me like I'd spoken a different language. Half. They don't understand half — the people running this ring operate on all-or-nothing."
"Bought time. That's all this is. The second shipment's still coming, and the coordinator will be less patient when it does."
4. NPC State Changes per Path
Shift Supervisor
| Attribute | Path A (Escalate) | Path B (Stabilize) | Path C (Mediate) |
|---|---|---|---|
behavior_flags |
"nervous,schedule_changes,evasive" |
"reliable,punctual" |
"cautious" |
position_integrity |
"thin" |
"solid" |
"solid" |
trust_level (from smuggler) |
"reliable" |
"reliable" |
"reliable" |
risk_assessment (detective) |
"high" |
"low" |
"moderate" |
tell_observed (detective) |
"nervous_schedule_adjustments,break_room_avoidance" |
(none new) | "cautious_scheduling" |
moral_weight (smuggler) |
"compromised" |
"compromised" |
"compromised" |
THE FRIEND (Dock Worker)
| Attribute | Path A (Escalate) | Path B (Stabilize) | Path C (Mediate) |
|---|---|---|---|
behavior_flags |
"reliable,punctual" (baseline) |
"lattice_checking,distracted,evasive" (accelerated) |
"uncertain,distracted" |
trust_level (from ring coordinator) |
"trusted" |
"uncertain" (coordinator pressures directly) |
"uncertain" |
risk_assessment (smuggler) |
"low" |
"moderate" (visible strain) |
"moderate" |
loyalty_assessment (smuggler) |
"solid" |
"solid" (but strained) |
"uncertain" |
| THE FRIEND arc timing | Normal pace | Accelerated (tells arrive sooner) | Normal pace |
Ring Coordinator (off-stage, tracked through references)
| Attribute | Path A (Escalate) | Path B (Stabilize) | Path C (Mediate) |
|---|---|---|---|
trust_level (toward smuggler) |
"trusted" (delivered results) |
"suspicious" (defied directive) |
"uncertain" (half-measure) |
| Pressure vector | Through shift supervisor (operational) | Through THE FRIEND (personal) | Through THE FRIEND (revisit demand) |
| Follow-up action | Bonus payment, continued partnership | Direct contact with THE FRIEND, bypasses smuggler | One-cycle trial, second decision point |
Smuggler (PC state)
| Attribute | Path A (Escalate) | Path B (Stabilize) | Path C (Mediate) |
|---|---|---|---|
operational_trust (from ring coordinator) |
High — reliable operator | Low — defiant | Moderate — cautious, untested |
operational_trust (from shift supervisor) |
Moderate — complies but resents | High — smuggler protected them | Moderate — temporary reprieve |
| Exposure position | Higher personal risk | Lower personal risk | Moderate, with deferred risk |
| Follow-up fork | None (resolved) | None (resolved, but THE FRIEND strained) | Yes — second decision when coordinator revisits |
5. Detective Observation per Path
The detective does not know the smuggler's choice. The detective observes consequences.
Post-Escalation (Path A)
Observable signals: Manifest discrepancies spike. The shift supervisor's schedule revisions increase. Night shift personnel reassignments without clear operational justification. The shift supervisor avoids the break room during transition windows.
Detective monologue:
"The shift supervisor changed the night rotation. Third time this week. Two workers reassigned without explanation. The freight scheduler has noticed too — manifest revision rate is tracking the schedule changes."
"The shift supervisor is managing something that isn't on the schedule. Whatever it is, it's getting bigger."
Monologue implications: The detective's investigation accelerates toward the shift supervisor as the institutional weak point. The shift supervisor becomes the thread to pull. The ring's operational footprint expands, making pattern detection easier.
Post-Stabilize (Path B)
Observable signals: Hub runs quiet. No schedule anomalies. But THE FRIEND's personal behavior shifts — lattice checking increases, social interactions shorten, visible tension without an organizational cause.
Detective monologue:
"The hub's been quiet. But the dock worker — they've checked their lattice eleven times this shift. That's not work communication. That's someone waiting for something they don't want to arrive."
"No schedule disruptions. No manifest flags. Everything's clean on paper. But the dock worker — carrying something. Personal? Professional? Filing it."
Monologue implications: The detective's investigation slows on the institutional side but builds a behavioral case against THE FRIEND specifically. THE FRIEND's tells become the primary signal. When the contradiction arc arrives, it hits harder because the detective has already been watching.
Post-Mediate (Path C)
Observable signals: Inconsistent operational tempo. One night shows excess cargo movement; the next is normal. The detective reads this as internal disagreement or experimental timing.
Detective monologue:
"Something's off. Last night extra cargo, tonight normal. There's no pattern, and that's the pattern."
"Inconsistent tempo. If someone's running an operation through this hub, they're either changing methods or arguing about them. Either way — disorganization is observable."
Monologue implications: The detective reads organizational confusion. This provides a different kind of evidence — not volume (Path A) or personal behavior (Path B), but structural inconsistency. The detective infers internal disagreement within the operation, which is accurate.
6. Self-Containment Declaration
This fork is self-contained within Triangle 1 (Hub Power: Shift Supervisor / THE FRIEND / Ring Coordinator).
Per D-053 / A-17: Self-contained forks are independent decision state machines with shared NPC state. Triangle 1's outcome modifies the shift supervisor's and THE FRIEND's behavioral attributes and does NOT gate Triangle 2 (Worried Knowledge), Triangle 3 (Bar Tensions), Triangle 4 (Worried Partner), or Triangle 5 (Informant Question).
What crosses triangle boundaries: NPC state changes are observable by other triangles' logic, but this is emergent, not scripted cascade. If the shift supervisor's behavior_flags change to "nervous,schedule_changes,evasive" (Path A), Triangle 2's manifest clerk can observe this through normal NPC observation mechanics. But Triangle 2's fork (if one exists) is not gated on Triangle 1's outcome.
What does NOT cross:
- Triangle 1's decision does not unlock or lock content in T2, T3, T4, or T5.
- Triangle 1's decision does not modify NPCs outside the triangle (manifest clerk, bar owner, THE FRIEND's contacts, etc.) except through standard observation.
- Triangle 1's decision does not alter the detective's investigation path — it alters the timing and observability of evidence, not its existence.
Design principle: The fork changes WHAT the detective sees first, not WHAT the detective discovers. All three paths lead to the ring. The smuggler's choice determines whether the detective arrives via institutional signals (Path A), personal behavioral tells (Path B), or organizational inconsistency (Path C).
7. Content Requirements
Authored Lines Summary
| Content Type | Path A | Path B | Path C | Shared |
|---|---|---|---|---|
| Ring coordinator lattice message | -- | -- | -- | 6 lines (trigger message) |
| Ring coordinator follow-up message | 1 line | 1 line | 2 lines | -- |
| On-station coordinator delivery | -- | -- | -- | 2 lines (shared) |
| Shift supervisor reaction dialogue | 3 lines | 3 lines | 2 lines | -- |
| THE FRIEND reaction dialogue | 2 lines | 2 lines | 2 lines | -- |
| Smuggler monologue | 3 lines | 3 lines | 3 lines | -- |
| Detective monologue | 2 lines | 2 lines | 2 lines | -- |
| Subtotal | 11 | 11 | 11 | 8 |
Total authored lines: ~41 lines across all paths and shared content.
Ring Coordinator Lattice Message (Shared — Trigger)
Written above in Section 2. Six lines of authored content in the ring coordinator's voice: direct, authoritative, strategic. "I trust your judgment on people" is the one warm note — genuine and instrumentalizing simultaneously.
On-Station Coordinator Delivery Dialogue (Shared)
Written above in Section 2. Two lines: the relay and the redirect to the shift supervisor question.
Shift Supervisor Reaction Dialogue (Per Path)
Path A (3 lines): Anxiety about the forty-minute gap, resentful compliance, fatalistic observation about "adjustments."
Path B (3 lines): Surprised relief, cautious gratitude, warning about the coordinator's memory.
Path C (2 lines): Pragmatic acceptance of half-volume, skepticism about whether it stays at half.
THE FRIEND Reaction Dialogue (Per Path)
Path A (2 lines): Relief that the coordinator's pressure is off, unease about double volume risk.
Path B (2 lines): Anxiety about the coordinator going directly to them, acknowledgment that it was the right call but at personal cost.
Path C (2 lines): Confusion about the half-measure, warning that the coordinator doesn't do compromise.
Ring Coordinator Follow-Up Messages (Per Path)
Path A (1 line): Praise, bonus confirmation, instruction to reassure the shift supervisor.
Path B (1 line): Cool acknowledgment, redirected pressure onto THE FRIEND, "we'll talk about alternatives."
Path C (2 lines): Measured response, "I can respect careful up to a point," one-cycle trial with implied revisit.
Smuggler Monologue (Per Path)
Path A (3 lines): Operational satisfaction shadowed by the shift supervisor's visible fear; alignment with the coordinator's logic; noting THE FRIEND's relief.
Path B (3 lines): Shift supervisor protected but THE FRIEND exposed; recognition of transferred pressure; guilt about the cost.
Path C (3 lines): Bought time, not resolution; THE FRIEND's confusion; awareness that the coordinator will return with less patience.
Detective Monologue (Per Path)
Path A (2 lines): Shift supervisor's schedule changes as institutional signal; manifest revision rate as data.
Path B (2 lines): Hub quiet but THE FRIEND's lattice activity as personal behavioral signal; clean paper vs. dirty behavior.
Path C (2 lines): Inconsistent tempo as organizational signal; disorganization as evidence.
Cross-References
- Entity Attributes — Canonical
known_attributeskeys referenced in state tables - Monologue Guide — Tag taxonomy, prerequisite format, voice discipline