Operator Tactics // Terra Conflictus · 2066 // Hub Supplement
The Echo
Protocol
Gorodskie Ekho // Vertical City // Flooded Towers
Gorodskie Ekho // Megacity Hub
6 Districts // Encounter Tables
4 Factions // Escalation Tracks
11 Key NPCs
4-Arc Campaign Structure
Mission: The Kitchen Job
“Altitude equals access. Everything else is water.”
— Graffiti, The Soak, level 12, author unknown
Use → / ← arrow keys, spacebar, or buttons below to navigate. Press F for fullscreen.
00
What’s in This Module
Overview
A flooded vertical megacity in active collapse — six fully detailed districts, four factions in open conflict, two simultaneous escalation tracks, eleven key NPCs, a four-arc campaign structure, and one standalone mission. Everything connects. Nothing is stable.
| Part | Content | Use |
|---|
| 1 | Gorodskie Ekho | Hub overview — city structure, three tiers, faction heat, scarcity index |
| 2 | The Six Districts | Full location entries — encounters, contacts, rumors, destabilization conditions |
| 3 | Factions | Four faction profiles, escalation tracks, contact protocols |
| 4 | The Cast | Eleven key NPCs — drives, agendas, contact levers, secrets |
| 5 | Campaign Arc | Four-arc structure — 6–8 sessions, dramatic engine, session outlines |
| 6 | The Kitchen Job | Standalone mission — five-beat structure, opposing forces, climax variables |
How to Use This Module
Run The Kitchen Job as a one-shot or opener. Drop individual districts into any OT city sandbox. Use the escalation tracks as background pressure in an ongoing campaign. Or run the full four-arc structure as a dedicated season. Every piece works independently. The city is the glue.
01
Gorodskie Ekho
Hub Location
47 vertical kilometers of rearranged architecture — a megacity inverted by the Upheaval. Pre-catastrophe street level sits 40 feet underwater. Upper floors became ground level. Clean, lit, controlled. The vertical stratification is absolute: altitude determines access to breathable air, clean water, and Syndicate approval.
| Attribute | Value |
|---|
| Location Type | Megacity — vertical, flooded, faction-contested |
| Scale | 47 vertical km / 12 million registered / 4 million unregistered (The Soak) |
| Control | Syndicate (The Dry) · EO (claimed authority) · NAF (covert) · Independents (The Soak) |
| Faction Heat | 3/5 — escalating |
| Scarcity Index | Drinkable water · stable power · analog components · upward mobility |
| Signature Threat | Rogue AI flood control · pre-Upheaval weapons in submerged vaults · posthuman research escaping The Spire |
01.1
The Three Tiers
City Structure
The Soak — The Wet Reimagined
Flooded street-level and lower commercial floors, 40 feet below the new ground. Perpetually wet, lit by chemical phosphorescence and jury-rigged solar catch-basins. No centralized power — water filtration, fermentation gardens, analog networks. Climate refugees, factory labor, people who cannot afford permits for The Current. No faction has full control. Everyone has a presence.
The Current — Where Hope Lives and Dies
Mid-levels (floors 15–35) where the city’s economic machinery runs. AI-managed factory floors, corporate workspace, transport hubs. Social credit is enforced. Faction safehouses, black-market corridors, and underground transit routes run through infrastructure. Drone surveillance is heavy but exploitable.
The Dry — Mythic Space
Upper levels (floors 36–47). Air is clean, water is guaranteed, power is stable. Executive towers, Syndicate administration, closed-circle research facilities. For Soak residents, The Dry is untouchable. Access requires Syndicate sponsorship or NAF clearance. Sealed from The Soak completely. Accessible only through controlled checkpoints.
02
The Six Districts
Hub Locations
Each district has a function, a controller, a pressure, and a breaking point. None of them are static. Roll encounters to keep operators off-balance. Let the rumors seed future missions. When a district destabilizes, the ripple hits everything adjacent.
D-01
The Bilge Kitchen
The Soak // Food Production
District-scale food production on submerged market squares and rooftop soil beds. A woman in a respirator stands on a rooftop 40 feet above the flood, hands in dark soil under a phosphorescent grow-lamp.
Controller
Soak Collective (council-driven). NAF has one embedded representative.
Risk
Mold blooms killing fermentation batches · rooftop collapse · Syndicate food cartel pressure · cascade crop failure
If Destabilized
40,000 residents lose daily meals in 48 hours. Factions arrive offering nutrition paste in exchange for access. Food is explicitly weaponized.
02.1–02.2
Signal Reach & The Lockworks
The Soak // Current
D-02
Signal Reach
The Soak // Black Market
A vertical market running through exposed elevator shafts and stairwells. Illegal tech, bootleg medical, gene-forge equipment. A teenager on a swaying rope platform examining a salvaged processor under phosphorescent light.
Controller
No single owner. Multiple independent vendor networks in uneasy détente. Every faction has enforcer presence.
Under-System
Unauthorized pneumatic tube network connecting to The Undermap. Unmapped by faction intelligence. Only 5-year veterans know the full network.
D-03
The Lockworks
The Current // Infrastructure
Pre-Upheaval industrial maintenance level. Analog systems, mechanical archives, faction-neutral space. Operators work on equipment the corporate AI network cannot track.
Controller
Nominally independent. Tacitly protected by NAF. Syndicate tolerates it because the machinery keeps The Current functioning.
Under-System
Mechanical transmission lines nobody fully understands. Prone to violent pressure spikes. An operator who reads the industrial cycle can move goods without detection.
02.3–02.4
The Spire & Drift Canal
Current // Dry
D-04
The Spire
The Dry // Restricted Research
The Syndicate’s research hub and executive center. Sealed habitation suites, climate-controlled war rooms, automated defense. The Vault is here — consciousness transfer pods in a sealed sub-level chamber.
Controller
Baroness Volstok / Syndicate (absolute). Dr. Voss runs posthuman research. NAF has 18-month deep-cover infiltration in progress.
Risk
NAF infiltration discovery · Thane’s unauthorized operations · flooding of lower Spire levels · posthuman research escape
D-05
Drift Canal
Current-Soak Border // Transit
The border zone between The Soak and The Current — a series of boat lanes, improvised checkpoints, and contested transit corridors. Control here determines who can move between tiers without Syndicate approval.
Controller
EO garrison (northern section). Independent operators (southern crossings). Nobody controls all of it simultaneously.
Under-System
Pre-Upheaval flood control tunnels running under the canal level — sealed, flooded, accessible to equipped divers. Connect to The Undermap.
02.5
The Undermap
Below the Soak
D-06
The Undermap
Below The Soak // Hidden Infrastructure
Pre-Upheaval transit system, collapsed utility infrastructure, and flooded industrial floors beneath The Soak’s waterline. The only fully faction-neutral space in The Echo. Dark. Navigable by those who know it.
Controller
NAF has established black sites here. Independent operators use it for transit. No faction has surveillance capability below a certain depth.
Under-System
Pre-Upheaval stasis chambers. Military-grade weapons in sealed vaults. An access card that Deshi has carried for decades without knowing what it unlocks.
If Destabilized
The last neutral ground in The Echo disappears. Every faction simultaneously commits resources to controlling the underground. Whatever is in the sealed vaults is now a race condition.
District Contacts at a Glance
Elena Markov (Bilge Kitchen — water systems, rooftop transit) · Kasim Patel (Bilge — smuggling, pier networks) · Sarcade (Signal Reach — black market tech, Wire Wall) · River (Drift Canal — independent checkpoint operator) · Raina (Undermap — pre-Upheaval knowledge, deep navigation)
02.6
District Encounter Reference
Running the Soak
Roll D6 day or night for each district. Cross-reference to establish rhythm. Let encounters seed rumors. Let rumors seed missions.
The Bilge Kitchen (D6)
D
Harvest labor recruitment / Syndicate buyout attempt / child theft / batch contamination / NAF documentation / rooftop structural breach
N
Nocturnal harvest crew / Syndicate sabotage of fermentation tanks / residents stealing food / rooftop transit refugees / unauthorized NAF soil samples / malfunctioning maintenance drones rupturing tanks
Signal Reach (D6)
D
Counterfeit tech sale / NAF recruiter / failed gene-forge mutation child / Syndicate clinic raid / EO turf negotiation / pneumatic tube jam
N
Anonymous gene-forge clinic / NAF datasleeve transactions / independent operator fencing / Syndicate systematic stall searches / vendor dispute escalating to weapons / Wire Wall network cascade
Key Rumors (Roll Per District)
Bilge: Syndicate has been poisoning Collective seed stock for three months · deep water below contains something alive fouling the aquifer · rooftops are sinking 6 inches per week
Signal Reach: NAF surgically enhancing operatives with unreleased gene-forge tech · a major vendor is Syndicate undercover · pneumatic tubes connect to pre-Upheaval military vaults · Syndicate planning to collapse the market entirely
When Destabilization Fires
Track which district is under pressure and advance its destabilization condition. Districts don’t recover without operator intervention. The city doesn’t wait.
03
Factions
Power Map
The Syndicate — Baroness Volstok’s Network
Hegemonic Corporate Authority // Faction Heat: 4/5
Territory: The Dry (absolute), The Spire (absolute), major Current installations, distributed enforcement throughout The Soak.
Objectives: Absolute control of The Dry and Current. Complete posthuman research before NAF or EO can acquire it. Eliminate independent operators. Maintain facade of legitimacy while operating as de facto military occupation.
Problems: NAF infiltration into The Spire. EO pressure and covert economic espionage. Rising water levels threatening research facilities. Thane’s rogue operation — which Volstok doesn’t fully understand yet.
Contact Protocol: Direct approaches are dangerous. Work through intermediaries. Payment always demanded. Betrayal is permanent.
03.1
EO & NAF
External Powers
Eurasian Oligarchy
Territorial Military Authority // Faction Heat: 3/5
Territory: Claims all of The Echo. Active garrison in northern Drift Canal. Scattered presence throughout The Current.
Assets: Military garrison (800–1,200 trained personnel) · northern checkpoint control · diplomatic legitimacy · external financial resources.
What They’re Actually Looking For: A pre-Upheaval Lumicite-based installation. They don’t know about consciousness transfer. They don’t know what they’re actually looking for.
North American Federation — Intelligence Division
Covert Intelligence Agency // Faction Heat: 3/5 (accelerating)
Territory: No formal territory. Safe houses in The Undermap, The Lockworks, Signal Reach, and The Spire.
Assets: 200–400 trained agents · advanced hacking capability · access to genetic research through Dr. Choy · external weapons and funding.
What They Know: More than EO about Thane’s activities. Hasn’t decided whether to stop him or recruit him. Sees consciousness transfer as strategic advantage if controllable.
03.2
Independent Operators & The Soak Collective
Decentralized
Independent Operators & The Soak Collective
Decentralized Community Networks // Faction Heat: 2/5 (rising)
Territory: The Soak (primary), Signal Reach, The Bilge Kitchen, The Lockworks, distributed throughout The Current and Undermap.
Approach: Community resistance and mutual aid. Maintain autonomy through economic networks, information sharing, and organized labor.
Assets: Millions of residents with varying organization · analog networks not dependent on corporate infrastructure · black markets · cultural authority and moral legitimacy in The Soak.
The Null Collective Connection: Deliberately blank. Thane’s consciousness work parallels their ideology in ways he doesn’t fully understand. They may be watching. They may be patient.
Faction Contact Summary
Syndicate: Through intermediaries only. Always costly. EO: Formal channels, military hierarchy. Honors contracts if they serve interests. NAF: Indirect recruitment through Dr. Choy, Lt. Chen, Rostov. Compartmentalized. Collective: Through Elena Markov, Kasim Patel, River, Raina. Slower to build, more stable once established.
03.3
Escalation Track 1
Syndicate Consolidation
Baroness Volstok is moving toward completing her posthuman enhancement program and establishing uncontested control over The Echo. Advance based on time passed in-world, not sessions played.
Phase 1
Current: Syndicate operatives systematically identifying independent operators and autonomous communities. Intelligence compiled on operator activities, NAF contacts, and pre-Upheaval asset locations.
Phase 2
1–2 weeks: Independent operation centers targeted with raids and arrests. Signal Reach’s Wire Wall shut down. The Bilge Kitchen subjected to heavy taxation and supply seizures. Deaths expected. Resistance treated as justification for escalation.
Phase 3
2–4 weeks: Syndicate establishes permanent military presence in The Soak. Checkpoints become constant. Food distribution controlled. Work permits required for movement.
Phase 4
4+ weeks: First generation of enhanced posthuman soldiers produced. New power imbalance emerges. If Thane completes his protocol before this, the research goes somewhere Volstok didn’t authorize.
If Operators Disrupt
Consolidation stalls. Factions remain contested. Independent operators retain operational freedom.
If Syndicate Completes
Posthuman soldiers deployed. Military balance shifts decisively. The city enters open warfare.
03.4
Escalation Track 2
The Rising Flood
Water levels are rising faster than systems can manage. Pre-Upheaval pump systems are failing. The underlying catastrophe is environmental, not political.
Phase 1
Current: Water rising 4–6 inches per week. Bilge Kitchen gardens experiencing saltwater contamination. Undermap’s flooded sections becoming impassable.
Phase 2
1–2 weeks: Major pump systems begin failing. Multiple stations go offline simultaneously. Water accelerates to 8–12 inches per week. Lower Spire sections at risk of catastrophic flooding.
Phase 3
2–4 weeks: Power generation in The Spire loses coolant from flooded lower levels. Electrical distribution fails section by section. The city is becoming ungovernable.
Phase 4
4+ weeks: The Soak becomes partially uninhabitable. Millions of residents must relocate upward. The entire social structure of The Echo is destabilized.
Dual Escalation
If both tracks reach Phase 4 simultaneously, The Echo enters permanent destabilization. Every district becomes a contested zone. This is not a failure state — it is a different campaign.
04
The Cast
Key NPCs
Eleven key NPCs. Each has a drive, a lie they tell themselves, a truth they can’t face, and a secret that recontextualizes them when operators learn it. Run them as people first and plot functions second.
Marcus Reeves
Independent Operator · The Thinking Man · Baseline
Lie: I can reach the top if I’m clever enough.
Truth: Freedom is looking around, not up.
Runs lateral. Sees systems. Catches the lies his crew misses. His weakness is that he’ll burn friendships proving he’s right. Secret: He’s terrified of having no way out — and every clever plan is a trap door he builds for himself.
In the campaign: his competence on the Dynasty job is what brings Thane’s attention. Everything that follows is, in some way, his fault.
Primary Target // Thane’s Objective
Maya Reeves
Soak Collective · De Facto Community Leader · Baseline
Lie: If I care hard enough, the system will protect people.
Truth: Care doesn’t need the system’s permission.
Runs the kitchen. Feeds people. Unmoved by faction pressure. Her weakness is isolation — she doesn’t ask for help. Thane wants her consciousness. Marcus wants her to escape. She wants neither.
Secret: She’s been documenting Syndicate food supply manipulation for months. The documentation is in the kitchen. It’s the most dangerous piece of intel in The Soak.
04.1
Thane & Baroness Volstok
Primary Forces
Primary Antagonist // Arc 1–3
Thane
Syndicate Lieutenant (Rogue) · Consciousness Architect · Synthetic Body (7th Iteration)
Catchphrase: “Consciousness survives pattern.”
Lie: I can achieve permanence through control.
Truth: Copying yourself is dying slowly, seven times.
Moves slightly wrong — expressions one beat late, breathing synchronized rather than spontaneous. His knowledge of people he’s researching is too precise. Beautiful and wrong in the same moment.
Secret: Each new body feels less like him. He’s hunting Maya’s consciousness because she’s the last thing that felt real. The collection isn’t about immortality anymore — it’s about not disappearing.
Baroness Volstok
Syndicate Supreme Command · The Dry · Power
Lie: I control what happens in The Spire.
Truth: Thane has been operating outside her authority for longer than she knows.
Calculating, ruthless, genuinely brilliant at maintaining power under three-faction pressure. Age unknown — appears fifties, augmented multiple times for longevity. Doesn’t typically work directly with operators.
Contact Lever: Volstok is interested in operators who can solve specific problems she doesn’t want to officially address. She will use operators and discard them. This is not speculation. It is policy.
04.2
Supporting Cast
Contacts & Complications
Dr. Catherine Voss
Syndicate Research Director · The Spire · Posthuman Ethics (Lack Thereof)
Director of posthuman research. Speaks about human subjects the way others speak about equipment. Genuinely sees the research as evolution. Lever: Needs someone to acquire a pre-Upheaval genetic specimen from The Undermap — still alive, barely, in a stasis chamber.
04.3
Supporting Cast
Soak Operators
05
The Echo Protocol
4-Arc Campaign
05
Campaign Overview
6–8 Sessions Core // Expandable to 10
Dramatic Engine: The crew must extract a consciousness from a synthetic tyrant’s vault before he completes his transfer protocol and becomes truly immortal — while the city floods higher and factions converge on the same prize.
The Not-Line: Thane isn’t the real enemy. The Syndicate is. And the Syndicate doesn’t know what Thane is or what he’s found. When they find out, the crew becomes a resource to be controlled or eliminated.
Tone: Cyberpunk procedural with horror underneath. The city is beautiful and drowning. The crew fights not to save the world but to save one person and prove that individual lives still matter.
05.1–05.2
Arc 1 & Arc 2
Sessions 1–4
Arc 1 — The Soak (Sessions 1–2)
Something’s Wrong With Him
The crew pulls a clean job: ghost-grab biometric data from Dynasty charity accounts during a philanthropic tour. The job looks easy because it’s adjacent to Dynasty operations, not Syndicate core. What the crew doesn’t know: Thane has been watching Dynasty accounts. He doesn’t care about the theft. He wants to know who the crew is, who they trust, who they report to. He’s looking for Maya through the crew’s network.
End Arc 1 with Maya returning from dinner with Thane and saying, quietly, “Something’s wrong with him. Something about him isn’t real.” Fade to black.
Arc 2 — The Spire (Sessions 3–4)
Maya’s Body Is a Shell
Maya is missing. Her body turns up in a morgue intake facility — processed, catalogued — but biometric markers are contaminated. Time of death inconsistent. This isn’t a murder investigation. It’s a heist. Maya’s consciousness is in The Vault. The crew breaches The Spire’s lower levels. They find consciousness transfer pods. When they try to disconnect Maya’s pod, a priority alarm fires — a kill-switch tied to Thane’s biometrics.
Not-Line: Thane wants them to succeed. He wants them to take Maya’s file and run. Because Thane’s consciousness is bigger than one body. Extraction is surrender.
05.3–05.4
Arc 3 & Arc 4
Sessions 5–8
Arc 3 — The Choice (Session 5)
What the Crew Actually Is
Maya’s consciousness file — complete or partial — is in the crew’s hands. Options: restore Maya to a synthetic body · destroy Thane’s entire Vault · sell the file to NAF or EO · surface the information to someone who can use it. None of these options are clean. All of them have costs. The choice defines what the crew actually is.
Arc 4 — The Flood (Sessions 6–8)
The City Calls In Every Debt
The escalation tracks converge. Flooding at Phase 3. Syndicate consolidation at Phase 2. The final sequence has three possible shapes depending on crew choices: Spire assault to prevent Thane’s final transfer · flood control operation to stabilize the city long enough to extract Maya · faction war where the crew has enough leverage to determine which power structure survives. There is no version where everything is saved. There is always a cost.
Climax Variable — What Was Under The Water
Deshi’s access card. The flood control system that was shut down deliberately. Whoever activated the shutdown — and why — is the final revelation. This thread extends beyond the campaign if the GM wants it to.
05.5
Session Outlines
Arc Reference
| Session | Focus | Clock | Ends When |
|---|
| 1A | The Kitchen Job (standalone) — Dynasty gala, data pull, cover maintenance | 90-minute access window | Crew exits clean. Thane has a neighborhood. |
| 1B | Soak exploration — districts, contacts, faction mapping | Escalation Track 1 Phase 1 | Maya reports something wrong with a dinner companion. |
| 2–3 | Maya missing. Investigate / breach Spire lower levels. | Track 2 Phase 2 begins | Vault found. Kill-switch triggered. Decision forced. |
| 4 | Arc 2 resolution — the file is extracted or the pod goes deeper. | Both tracks advancing | Crew has Maya’s file, or they don’t. Either way, Thane knows. |
| 5 | The Choice. No good options. The city fractures. | Tracks converging | The crew commits. Arc 4 begins. |
| 6–8 | Arc 4 — final sequence. City calls in every debt. | Phase 4 imminent | There is always a cost. |
Between-Session Mission Seeds
The Bilge Cartography · Signal Theft · The Lockworks Salvage · The Spire Reconnaissance · The Drift Canal Liberation · The Undermap Archive. Each has a client, a clock, a complication, and a payoff. Each advances or complicates one of the two escalation tracks.
06
The Kitchen Job
Mission Scenario
06
The Kitchen Job
Infiltration // Social Engineering // 90-Minute Window
Core challenge: A clean data extraction from a heavily staffed corporate venue during a narrow access window — while Thane’s agents clock the crew’s network without the crew knowing they’re being watched. The win condition is not the mission. The win condition is what the mission costs.
A Dynasty corporation is hosting a philanthropic gala at the Verdana Tower, mid-Current level. The Syndicate uses Dynasty charity accounts to move operational funds. Detective Chen has been tracking the discrepancy for six weeks. She needs the raw biometric data from the account-access nodes during the pledge period tonight. She can’t pull this herself.
What Chen doesn’t know: Thane has been monitoring Dynasty accounts for weeks. He doesn’t care about the financial data. He wants to see who comes for it, who they run back to, and who feeds them dinner when the job is done. He already knows about Maya’s kitchen. Tonight he’s running parallel surveillance, and the crew is his search term.
06.1
Mission Parameters
The Kitchen Job
| Client | Detective Chen (EO Security Forces, acting independently) |
| Primary Objective | Extract biometric account data from Dynasty server node — pledge period access window only |
| Secondary Objective | Confirm Syndicate account routing chain (bonus intel, not required for payment) |
| Tertiary Objective | Exit without trace — no faction alert, no documented intrusion |
| Window | Pledge period runs 9:00pm–10:30pm. Nodes only live during this window. After 10:30pm, secondary locks engage and nodes power down. |
| Cover | Gala attendees. Forged invitations available from Kasim Patel (quality varies). |
| Insertion | Main entrance (requires documentation) or service corridor via building’s food delivery route (simpler, noisier) |
| Extraction | Standard guest departure or fire exit on tower’s east face (4-minute alarm delay, not instant) |
| Intel Quality | High. Chen has accurate staff rotation data. Node locations confirmed. Security response time: 6 minutes from alert to floor presence. |
Ground Situation
22nd floor: 200 registered guests, 40 Dynasty staff, catering operation, 6-person private security rotating every 90 minutes. Server room is one floor below — accessible via maintenance stairwell off the catering kitchen or a service elevator requiring a staff keycard. The transfer takes 8 minutes. The crew needs to control the room.
06.2
Beats 1 & 2
Approach & Access
Beat 1
Approach — Getting into the Verdana Tower and onto the event floor.
Option A — Guest Credentials
Forged invitations from Kasim get through the outer guest check if documentation holds. Dynasty staff checking IDs is junior and distracted — not incompetent. Works once. First moment the crew discovers whether their cover is as good as they think it is.
Option B — Service Corridor
Food delivery access through the building’s loading dock. Requires a staff uniform and confidence. Avoids documentation entirely but puts the crew in the catering operation, which has its own supervision.
Option C — Social Engineering
A registered guest cultivated in the lobby bar before the event floor opens. Requires a real conversation. Works once.
Beat 2
Access — Getting from the event floor to the sub-level server room.
The maintenance stairwell runs from the catering kitchen — accessible but requires passing through kitchen staff who are not suspicious and not cooperative. The service elevator requires a staff keycard; three Dynasty staff members have one, and two of them can be approached.
The Log Problem
The passive monitoring system logs entry and exit biometrics. The crew either needs to ghost the log (requires Sarcade’s datasleeve or equivalent) or accept that the entry will show up in the morning and plan accordingly. Both are valid choices with different downstream costs.
06.3
Beat 3 — The Transfer
8-Minute Window
Beat 3
Extraction — The Data. The 8-minute transfer window. Cannot be interrupted without corrupting the pull. The crew needs someone in the room and someone managing the floor above.
The data node requires a physical connection — a datasleeve interface, purpose-built hardware, or improvised equivalent. During these 8 minutes, anything that happens in the building happens around the crew, not at their discretion.
This Is When the Secondary Clock Becomes Visible
The crew is holding position in a locking building with a fixed timeline. Whatever complication is coming — it arrives during the transfer, not before or after it. That’s the design. The mission architecture forces the crew to absorb pressure without being able to move.
If Transfer Completes
Full Dynasty biometric data and Syndicate routing chain. Chen gets what she needs. The log entry shows up in the morning. Countdown to complications begins.
If Transfer Interrupted
70% data recovery. Enough for Chen’s primary objective. Routing chain is incomplete. The crew’s decision here affects what Chen can do with the information downstream.
06.4
Beat 4 — Complication
D6 Roll or Choose
1
Mads Baratunde recognizes one crew member from a Syndicate operation three months ago. She hasn’t decided what to do yet. The window is closing.
2
A Dynasty junior staffer discovers the crew in the server room. She’s not going to call security — she’s going to bargain. She wants out of her contract and she knows something the crew doesn’t.
3
Pledge period ends 20 minutes early due to a guest medical incident. Door locks are engaging. Transfer has 4 minutes left.
4
The passive monitoring system logs an anomaly — not the crew. Someone else was in this room earlier tonight. The log has been partially altered. The crew is standing inside someone else’s operation.
5
Thane’s field agent enters the event floor and begins photographing guest interactions. Not targeting the crew — documenting Maya’s community contacts among the attendees. The crew sees this and must decide whether to act.
6
The transfer completes, but what it pulled is not Dynasty charity accounts. It’s a personnel file — a list of names with Syndicate classification codes that Chen has never seen. At least one person the crew trusts is on it.
06.5
Beat 5 — Extraction
The Walk Out
Beat 5
Extraction — The Crew. Getting out of the building with the data and without a trail.
Exit Options
Guest Departure
Exit through the main lobby while the event is running. Plausible if the crew maintained clean cover. Requires passing through Mads Baratunde’s security line.
Fire Exit
East face, tower exterior. Triggers alarm delay: 4 minutes before monitoring flags the exit. Not an instant alert. Useful if cover is blown.
Service Corridor
Re-entering the catering operation. Clean if the uniform held. Complicated if kitchen staff have questions.
The Breadcrumb — What’s Already in Motion
Whatever route the crew takes, they arrive back at Maya’s kitchen. She has dinner ready. What the crew doesn’t know: two people who left the event 15 minutes before them were on foot to the same district. Thane now has a neighborhood. He’ll have an address within 48 hours.
How to End This Session
End at Maya’s kitchen. She asks how it went. Someone says it went fine. She smiles and puts food on the table. Let that moment breathe. Then the session ends. The loss doesn’t arrive tonight. It arrives in 48 hours, when Thane’s people are at the door.
06.6
Opposing Forces
The Kitchen Job
Dynasty Security Detail
Event Security // 6 Personnel // Professional, Undertasked
Motivation: Secure the event, protect guests, clock out clean. Doctrine: Exit watching, guest management, no escalation unless forced. Not configured for a server room intrusion. Lever: Any credible authority figure gets cooperation rather than resistance. Breaking Point: Physical confrontation, a confirmed intrusion alert, or Mads Baratunde deciding she recognizes someone she shouldn’t.
Mads Baratunde
Dynasty Security Lead // Former Syndicate Contract // Wild Card
Motivation: Professional execution. Personal survival. The Syndicate operation that went wrong three months ago left her exposed in ways she hasn’t fully mapped yet. Doctrine: Pattern recognition. She watches how people move in rooms, not what credentials say. Lever: Not loyal to Dynasty. Loyal to whoever keeps the wrong attention off her. Breaking Point: If she confirms a crew member’s identity from that operation, she goes quiet and deliberate. Won’t call security. Will wait and follow.
Thane’s Field Agent
Syndicate Contractor // Social Documentation // Not Here for the Data
Motivation: Build a social graph of Maya’s network contacts. Tonight’s guest list includes three people who eat at Maya’s kitchen. Doctrine: Passive documentation. No confrontation. Professional invisibility. Lever: Has no idea the crew is running an operation. Not a threat — unless the crew makes them one. Breaking Point: If confronted, exits immediately and reports the crew’s presence to Thane. This accelerates the timeline by 24–48 hours.
06.7
Climax Variables
D6
1
Data pull completes cleanly. Crew exits as guests. Mads watches them leave and does nothing. The log entry shows up in the morning review and creates a problem for Chen — but not tonight’s problem.
2
Pledge period ends early. Transfer has 4 minutes left when door locks engage. Wait for full completion (trapped in a locking building) or pull with 70% of the data (enough for Chen, not enough for the routing chain).
3
Mads identifies a crew member and follows them to the service corridor. She’s not calling it in. She wants a conversation. She knows something about the Syndicate operation that affects the crew directly — if they’re willing to tell her something first.
4
The Dynasty junior staffer bargains. She has the routing chain data on a personal drive she’s been building for three months. She wants an introduction to someone who can get her out of her Dynasty contract. The crew can give her Elena Markov’s name. This will matter later.
5
The data transfer reveals a second access event from two hours earlier tonight. Someone else was in this server room. The data they pulled is not on record. The crew is the second intrusion. Something is already in motion that Chen doesn’t know about.
6
Thane’s agent is photographing guests near the crew’s exit route. Intervene and risk cover, alerting the agent. Walk past and protect the mission while Maya’s social network gets documented tonight. No right answer. The clock is still running.
Regardless of Which Variable Fires
One detail survives into the next session: Thane’s field agent was at the event. The crew’s competence tonight is the mechanism of Maya’s capture. The win is real. The cost is already paid. They just don’t know it yet.
A
Running The Echo
Appendix
The City as Pressure, Not Setting
Gorodskie Ekho works best when it’s doing something to operators rather than existing around them. The districts aren’t backdrops — they’re systems with breaking points. When operators act in one district, it ripples into adjacent ones. The escalation tracks are background physics: advance them based on time passed in-world, not on whether the crew addressed them. The city doesn’t wait.
Thane as Antagonist vs. Tragic Figure
Thane’s effectiveness depends on the crew encountering him as wrong before they encounter him as dangerous. The dinner scene in Arc 1 — where Maya sits across from something that looks exactly like a person but moves one beat off — is the most important scene in the campaign. He’s not threatening. He’s lonely. He’s trying very hard to feel something that used to come naturally. That’s what makes him frightening.
Dropping In
Any individual district works as a standalone location for an existing OT campaign. Signal Reach is a black market that fits any city. The Lockworks is a neutral faction space that generates its own encounters. Each district entry is self-contained enough to drop without the surrounding campaign architecture.
The Flood as Character
The flooding is not backdrop. It changes the map. Sections of The Undermap passable in session one may be impassable by session four. Track water-level changes between sessions and describe them at the top of each session before anything else. The city is visibly drowning. The crew sees it happening and has to decide whether that’s their problem.
The Null Collective
Left deliberately blank. If the campaign extends beyond four arcs, the Null Collective is the next layer — a faction whose ideology parallels Thane’s work in ways he doesn’t understand, and who has been patient enough to wait for him to prove their thesis before they act.
Operator Tactics // Terra Conflictus · 2066 // Hub Supplement
The Echo
Protocol
Gorodskie Ekho. Six districts. Four factions. Two clocks running simultaneously. A rogue synthetic lieutenant building immortality from stolen consciousness files. A city that is beautiful and drowning. There is no version where everything is saved. There is always a cost.