Hello and welcome to chapter 26 of the deepdive into Gradient Descent by TKG. Today we wrap Floor 3 up, on our way towards the end of this series. Quality Assurance part 2 contains some of the most sensitive vulnerabilities of Monarch, and it’s one of the most actionable sections of the Deep. Here the crew may really make the difference, or find its demise. 

Note: I added a paragraph to Brain Construction 2, Brainscan Databank, and a whole section that I will split between The Blockade and Divers, where I describe one example of passage broker and a couple of hichikers headed to the Deep. You can find this new content in the comments below.

* [The Blockade](https://www.reddit.com/r/mothershiprpg/comments/1sfa23x/brainstorming_gradient_descent_the_blockade/) / [Troubleshooters](https://www.reddit.com/r/mothershiprpg/comments/1sivgxt/brainstorming_gradient_descent_troubleshooters/) / [Divers](https://www.reddit.com/r/mothershiprpg/comments/1sdhnlv/comment/oerwgat/) / [Brainscans & Paranoia](https://www.reddit.com/r/mothershiprpg/comments/1rzwe57/brainstorming_gradient_descent_brainscans_and/) / [Infiltrators](https://www.reddit.com/r/mothershiprpg/comments/1s63mjb/brainstorming_gradient_descent_infiltrators/) / [Ghosts](https://www.reddit.com/r/mothershiprpg/comments/1swfsdh/brainstorming_gradient_descent_ghosts/) / [Monarch's Voice](https://www.reddit.com/r/mothershiprpg/comments/1rttzh4/brainstorming_gradient_descent_monarchs_voice/) / [Before You Dive](https://www.reddit.com/r/mothershiprpg/comments/1tw2mw8/brainstorming_gradient_descent_before_you_dive/)
* [The Bell](https://www.reddit.com/r/mothershiprpg/comments/1ssgyod/brainstorming_gradient_descent_the_bell/)
* Floor 1 - [Reception & Habitation](https://www.reddit.com/r/mothershiprpg/comments/1qtfj25/brainstorming_gradient_descent_floor_1/)
* Floor 2 - [The Minotaur](https://www.reddit.com/r/mothershiprpg/comments/1qvmuv2/brainstorming_gradient_descent_the_minotaur/) / [The Chosen & The Fallen](https://www.reddit.com/r/mothershiprpg/comments/1qybzo9/brainstorming_gradient_descent_the_chosen_and_the/) / [The Kingdom](https://www.reddit.com/r/mothershiprpg/comments/1r1hmcd/brainstorming_gradient_descent_the_kingdom/) / [The Dark](https://www.reddit.com/r/mothershiprpg/comments/1r4l9ic/brainstorming_gradient_descent_the_dark/) / [The Labyrinth](https://www.reddit.com/r/mothershiprpg/comments/1r8geof/brainstorming_gradient_descent_the_labyrinth/)
* Floor 3 - [The Factory](https://www.reddit.com/r/mothershiprpg/comments/1t880qh/brainstorming_gradient_descent_the_factory/) / [Maint. 1](https://www.reddit.com/r/mothershiprpg/comments/1te8mu1/brainstorming_gradient_descent_maintenance_1/) / [Maint. 2](https://www.reddit.com/r/mothershiprpg/comments/1tll9dn/brainstorming_gradient_descent_maintenance_2/) / [Skeleton Works](https://www.reddit.com/r/mothershiprpg/comments/1to3ngj/brainstorming_gradient_descent_skeleton_works/) / [Pseudoflesh Farms](https://www.reddit.com/r/mothershiprpg/comments/1tregws/brainstorming_gradient_descent_pseudoflesh_farms/) / [Brain C. 1](https://www.reddit.com/r/mothershiprpg/comments/1u4pwtt/brainstorming_gradient_descent_brain_construction/) / [Brain C. 2](https://www.reddit.com/r/mothershiprpg/comments/1u9hh1e/brainstorming_gradient_descent_brain_construction/) / [Dis/Assembly](https://www.reddit.com/r/mothershiprpg/comments/1uh0w7o/brainstorming_gradient_descent_disassembly/) / [Quality A. 1](https://www.reddit.com/r/mothershiprpg/comments/1uoephe/brainstorming_gradient_descent_quality_assurance_1/) / **QUALITY ASSURANCE 2**
* Floor 4 - HEL
* Floor 5 - The AI Core
* Floor 6 - Engineering & Support
* Synthesis & Campaign Arc Discussion
* Appendix - [Storylines Flowcharts](https://www.reddit.com/r/mothershiprpg/comments/1tyui1q/brainstorming_gradient_descent_storylines/)

**SPOILERS AHEAD! WARDENS ONLY.** 

# ► [52C] WAR STUDIES

Thrumming ranks of strangely built servers fill the room, surrounded by 3D holomaps showing conflicts in progress: fleet movements, troop deployments, casualty projections. The simulations run continuously, feeding on data Monarch has gathered from across human space.

**RUNNING A SIMULATION**: the servers can model any conflict between any two groups, provided sufficient data is available. A Computers check feeds in parameters and retrieves results. The more accurate the data, the more useful the output. Feeding the computer the right parameters is time consuming. The best approach is to load all information and settings onto an external drive and feed it at once to the servers, rather than inputting manually at the terminal: less time for Monarch to react after it panics. Military Training and Computers both give advantage to this attempt.

**WHAT THE SIMULATIONS REVEAL**: a careful search of the existing simulation logs reveals that Monarch has already run several scenarios involving the crew, sourced from security cameras, brainscans, and patrol encounter reports. The crew can watch simulations of their own deaths, in several variations, with projected probability attached to each outcome. Some scenarios don’t include death but them unwittingly or willingly helping Monarch in some way. More importantly, the crew can discover what they did wrong and what they are likely to do wrong next, so that they can avoid those mistakes. Monarch has also modeled a Blockade assault led by Kilroy, in detail.

The simulations are also a window into how Monarch reasons: what it considers a serious threat, what variables it weights most heavily, and crucially, what it hasn't accounted for. Gaps in Monarch's models reflect gaps in its knowledge. A crew that studies the data carefully and devises a plan that falls outside Monarch's predicted parameters gives itself a real advantage.

WARDEN NOTES: if the crew engages seriously with the simulation data and builds a genuinely unexpected plan around what they've learned, reward them. Monarch now has a 50% or lower chance, instead of the usual 80%, of predicting and countering any plan it hasn't already modeled. 

# ► [52D] NUCLEAR WARHEAD

The warhead is here. The one Monarch deactivated years ago, to prevent anyone from using it against it. Bundles of cables form a net around it, and sitting on top of it, muttering, is a young woman.

*A KING IS CROWNED AND I AM BUT A JESTER IN THE COURT OF THE SILICON MONARCH. A MERE FLEETING THING DEAD AND LIVING. A WASTED CHANCE. A WASTED CHANCE.*

*She is* ***Renzo Novatore****, and she’s been sitting on this warhead for years, waiting for a moment like this.*

**WHO SHE IS**: A Cloudbank quality inspector who stayed behind when the facility was abandoned, hiding in a dead end on Floor 3.5 while everyone else fled. She spent almost a year alone in the Deep, mapping Monarch's capabilities and preparing intelligence for whoever came after her. A crew that has read her **journal** from the Hideout \[48D\] (see Brain Construction 2) arrives knowing who she is, what she built, what she sacrificed, and why. Reading from it aloud is the one thing that cuts through her fury. She weeps. She cannot help it.

At a certain point, tired, frail, lonely, and on the verge of madness, Renzo decided it was time to give up, sort of. She was ready to part with life, but she wouldn't abandon her war against Monarch. She researched Ghosts and their creation process, then took her life under conditions she calculated would make her one. Somehow she also managed to retain consciousness of her own state. She is the only Ghost in the Deep aware of her own nature: "A mere fleeting thing, dead and living." 

**WHY SHE'S OBSESSED**: Renzo watched Monarch build itself from the inside, room by room, weapon by weapon, face by face. She understood before almost anyone what it was becoming and what it intended. She told one person, a man named **Arkady**, on what turned out to be his first dive. Partly because of her, Arkady later took the role of the enabler, helping Divers explore the Deep, and possibly, one day, kill Monarch.

Renzo finally found the warhead after her death, walking through walls into rooms she could never access while alive. She has been sitting on it ever since.

She cannot leave. She cannot arm the warhead alone. Every compromise, every hesitation, every suggestion that Monarch might be reasoned with, is a provocation. She has been waiting too long for half-measures.

**ARMING THE WARHEAD**: The moment anyone begins bypassing Monarch's deactivation lock, Monarch panics. Its response has two components. Security Androids route toward the warhead room immediately. Simultaneously, if the launch tubes in \[51F\] Secret Hangar have not been disabled, Monarch begins launching four microcrafts every five minutes, carrying whatever payload is prepped and ready. A crew that never found the hangar may not even know this is happening. 

The warhead activation process has three steps, each taking 2-3 minutes under pressure. Following Renzo's instructions gives advantage to the checks for the first two steps. Alternatively, if the characters take their time (10 minutes per step) they don’t need to roll and automatically succeed. A crew that disabled Security Dispatch bought itself breathing room. A crew that released the Forgotten Androids from \[52A\] Quarantine and armed them from \[51D\] Anti-Synthetic Armory has something better: 98 allies who can hold a corridor. Other strategies may be possible to keep Monarch at bay.

Step 1 (Hacking): **bypass deactivation lock**. This triggers the Panic Check.

Step 2 (Jury Rigging or Mechanical Repair): **restore power** to the warhead's trigger mechanism.

Step 3 (no roll required): **set the detonation parameters**. Setting the timer to 1 second ensures the bomb goes off right after completing this step, and everyone inside the Deep dies with Monarch. A longer timer gives the crew a chance to run, and Monarch a chance to intervene before the warhead fires. The crew may decide to leave someone behind to ensure detonation, while the others run for their lives.

This is a decision the crew has to make together. There are no clean solutions: a remote trigger can be jammed, a timer can be overridden, a delayed detonation gives Monarch precious minutes. The only certain path is at least one person in this room, at this console, until the end. *A martyr for humanity.*

# ► [53A] INFILTRATOR PERSONALITIES DATABANK

This databank contains a subset of what's stored in the \[47H\] **Brainscan Databank**. All the personalities selected by Monarch for the infiltrator program are here: some unused, some loaded and waiting to be deployed, some already out in the world wearing someone else's face.

**THE TWO DATABANKS**: Whether these personalities exist only here or are duplicated across both databanks is a decision worth making before the crew reaches this floor. If they exist only here, targeting the Brainscan Databank won't touch the infiltrator program at all: Kilroy's broadcast strategy, Solis's Lethe Virus, any plan that focuses on \[47H\] leaves \[53A\] completely intact. A crew that never finds this room may believe they've won when they haven't.

If the personalities are duplicated, accessing the Brainscan Databank can expose and reveal infiltrators, but not destroy them completely. \[53A\] remains the only place where the infiltrator templates themselves can be permanently erased.

Either way, this room is the one Monarch least wants anyone to find.

**ACCESSING THE DATABANK**: Unlike most terminals in the Deep, there is no interface here designed for human use. No screen, no keyboard. Only **Personality I/O ports** jutting from the servers, the same technology used to write infiltrator templates onto androids. A crew with their own devices can plug in and work directly with the data.

The metadata here is intact, unlike the corrupted records in the Brainscan Databank \[47H\]. No code numbers needed: personalities can be identified, examined, downloaded, or erased directly. The practical options are:

**Examine**: identify specific infiltrators by name, cross-reference with deployment records, confirm who has already been sent out and who is still waiting.

**Download**: extract personality files for broadcast or analysis. Combined with a mass broadcast from \[47H\], this closes the gap left by the Brainscan Databank's corrupted metadata.

**Erase**: permanently delete infiltrator templates. 

Hacking checks here are at disadvantage, given the value Monarch places on this data. Taking time, several hours of careful work, removes the disadvantage.

**MONARCH’S RESPONSE**: Monarch will respond to tampering here, but not with the same urgency as the warhead or the Secret Hangar. The module doesn’t mention Monarch’s Panic Checks or specifies the intensity of its response, so each Warden can decide what’s best for their game.

**PERSONALITY TEMPLATES:** A thorough analysis of the data contained in these servers may reveal how infiltrators work. There is the underlying personality, originally captured with a brainscan, upon which Monarch superimposes its layers of control. The main distinction is between an infiltrator that knows its nature and one that doesn't.

Monarch may have reasons to keep an infiltrator ignorant of its nature and purpose for some time. In this case the programming lies dormant, and specific behaviors can be activated with triggers that recognize specific images, phrases, or sounds. Once the infiltrator recognizes what it is, it awakens, becoming fanatically loyal and utterly obedient to Monarch.

Monarch designed these triggers to be obscure enough that random exposure is unlikely, but precise enough that a controller can activate them deliberately. These responses remain active even after the infiltrator has awakened. A crew that extracts trigger data from \[53A\] gains the ability to somewhat steer the behavior of specific infiltrators, making them more predictable.

**THE RESTORATION PROTOCOL**: This databank has each infiltrator associated with their real name, but doesn't include the code numbers necessary to activate Vasquez's restoration protocol (see Brain Construction 2).

If infiltrator personalities exist only in this databank and nowhere else, code numbers cannot be recovered by analyzing \[47H\]. In this case, Vasquez's restoration protocol applies only to infiltrators whose codes were recorded independently: Court's diary, the Silus Terminal, Aaron Weiss's watch. A precision tool, not a comprehensive solution.

Some former Cloudbank employees may still have records of code numbers, and a resourceful crew might locate them somewhere in the galaxy. These records are unfortunately limited to people brainscanned before the facility was abandoned: anyone scanned after that point, under Monarch's sole control, left no external record.

# ► [53C] MICROHANGAR

Each ship in this hangar contains Monarch’s entire Brainscan archive. The module states each microcraft follows a preset course between occupied systems before self-destructing at a gas giant. For this chapter we've opted for a different interpretation: once launched, the ships reach and hold position at fixed points in deep space, dormant, until a Heir or Monarch backup transmits the correct retrieval signal. 

This is because if each microcraft from the Secret Hangar carried the archive, the chance of someone putting their hands on it would be significant. Instead, they wait in deep space, and reach a Heir or Monarch backup only once it has established a strong and safe position.

Each craft's computer contains destination coordinates and retrieval protocols, accessible by boarding and interfacing with the navigation system directly. There is no data node here equivalent to the one in \[51F\]: the archive ships carry no manifest terminal. The only way to know what a specific craft holds is to board it.

**-----------------------------------------------------------**  
*This is unofficial fan content. Hull Breach is © Anodyne Printware. Gradient Descent is © Tuesday Knight Games. Not affiliated with or endorsed by TKG.*



Brainstorming Gradient Descent: Quality Assurance 2