
When the relay’s control bus settles, a mechanical latch releases beneath the grille. A shallow recess opens, revealing a sealed paper folder untouched by the digital custody streams.
The folder bears no corporate barcode. Inside, a partial transfer log names the fleeing netdiver and traces authorization through Rhea Kade’s hold channel, while handwritten notes crowd the margins.

Soren Quill
Paper? That relay has been digitally audited for years. If someone left this behind, they wanted the custody mesh to overlook it.
A handwritten annotation beneath the fleeing netdiver’s transfer time identifies Rhea as the command authority for Transfer Hold East. The ink is hurried, pressed so deeply it nearly tears the page.

Eidolon-7
That cannot be right. Rhea’s live credential is issuing containment commands, but this note says she was removed from command before Mara entered the hold.
The final readable line contradicts the active channel: Rhea is listed as a transferred subject, not an operator. Beneath it, a second handwriting begins a sentence and stops at the word “replacement.”

Soren Quill
There is a command relationship here, but it may belong to whoever replaced her. Do not trust either record until we compare the timestamps.
✓ Quest Accepted
Determine who truly controlled Mara's transfer
“I compare the paper log and live credential timestamps.”
SUCCESS (Good Reasoning, rolled +3)
Nyx lays the paper transfer log beside the relay’s live credential stream, aligning the handwritten times with the active command sequence. The paper’s ink predates Mara’s entry into Transfer Hold East.
She tracks each authorization mark against the live timestamps. Rhea’s removal is recorded first; only afterward does her credential begin issuing containment commands, already carrying a replacement designation.

Soren Quill
The timestamps settle it. Rhea was transferred before Mara entered the hold. Someone else activated her credential after the removal.
The live stream confirms the command sequence is current, but its first valid containment order follows the handwritten replacement note. The credential is genuine; its operator is not identified.

Eidolon-7
Then Rhea is not the active holder. Her identity was retained as authority after someone replaced her at the command endpoint.

Soren Quill
The log gives us a sequence, not a name. Rhea was removed, Mara arrived, and the replacement took control under Rhea’s credential.
“I isolate the live credential and follow its origin”
SUCCESS (Great Hacking, rolled +0)

Nyx isolates Rhea Kade’s live credential from the surrounding custody stream, then follows its authentication path backward through the relay’s command records.
The origin resolves beneath Transfer Hold East: a local command terminal at the physical containment endpoint, activated after Rhea’s removal and carrying the replacement designation.

Soren Quill
There. The credential did not originate from a remote corporate vault. Someone entered it locally, at the hold itself, after Rhea was transferred.
Nyx peels away inherited authorization layers and exposes the terminal’s access timestamp, command port, and current routing path into Mara’s containment channel.

Eidolon-7
That is the source. Reach the terminal, and you reach whoever is wearing Rhea’s authority now.
The isolation succeeds, but Nyx’s disposable relay patch burns out under the extraction. The origin remains mapped in her session, while the relay loses its maintenance control.

Soren Quill
I have the coordinates. Transfer Hold East, command terminal seven. Mara’s live channel is still attached to it.
+ New Item Acquired
Paper transfer folder
“I reach command terminal seven and identify its operator”
SUCCESS (Good Reasoning, rolled +1)

Nyx follows the mapped route through a service corridor beneath Transfer Hold East. Command terminal seven sits behind reinforced glass, its status light steady beside a sealed access door.
Inside, a young adult woman waits at the terminal, lean and sharply dressed in a dark utility coat. Her shaved temples frame copper hair, and a small black interface jack marks her throat.

Nyx crash
The terminal identifies the operator as Talia Voss, active under Rhea Kade’s authority.
Nyx reaches the terminal’s observation panel and captures its local authorization record. The command history confirms Talia Voss entered Rhea’s credential after Rhea’s removal.

Talia Voss
You found the terminal. That means the relay gave you my name, and the hold has already lost its silence.
Talia turns from the console, one hand resting near the hardwired command controls. Mara’s containment channel glows behind her, active and routed through the terminal.

Talia Voss
Rhea is not here. I am the operator holding Mara, and I can see exactly how you reached me.
✓ Quest Accepted
Free Mara from Talia Voss's custody
Quest Complete
Determine who truly controlled Mara's transfer
Attribute Upgrade: Reasoning Good→Great
“I keep my hands visible and demand proof Mara is alive.”
SUCCESS (Legendary Persuasion, rolled -2)


Nyx crash
My hands stay visible. Prove Mara is alive, right now, before you ask me for anything.
Nyx raises both hands beside the observation panel, fingers spread. Talia studies the gesture, then turns to the terminal and opens the containment channel’s biometric view.

Talia Voss
You get proof. But understand the cost: I am recording this demand as a personal intervention, not an anonymous intrusion. If Mara lives, your name is tied to her extraction.
The glass fills with a live medical feed. Mara’s face appears beneath a restraint canopy, eyes closed but breathing; her pulse rises, and one hand flexes against the sensor mesh.

Talia Voss
There. Live neural activity, respiratory exchange, and an induced sleep cycle. Mara Venn is alive. I have kept her stable since the transfer.
The feed expands to show a current timestamp and terminal-seven’s local authorization seal. Talia leaves it visible, but the intervention record now carries Nyx’s identity beside the request.

Talia Voss
Now you know the truth, Nyx. If you want her released, you owe me an honest account of what the archive contains and who will come hunting when I open this door.
“do i know what the archive contains”
NO (Likely, rolled 79)
The live feed remains open between Nyx and Talia. Mara’s breathing continues beneath the restraint canopy, but the archive itself appears nowhere in the medical or command data.

Talia Voss
You do not know what the archive contains. You know fragments, routes, and the people trying to control it. That is not the same thing.

Soren Quill
She is right. I stabilized recovered blocks, but the final directory was missing. We never read the archive’s complete contents.
The decoder’s admission settles over the command terminal. The fragments identify transfers and custody paths, but their central payload remains sealed behind absent indexing.

Eidolon-7
I cannot tell you what the archive contains either. I know it was important enough to bury, and dangerous enough that Mara carried part of it.

Talia Voss
Then your honest account begins with that absence. You are pursuing something you have not seen, while Mara is paying the cost of its concealment.
“I demand Talia release Mara now”
SUCCESS (Legendary Persuasion, rolled -1)


Nyx crash
Release Mara now. You have proved she is alive, and I am not leaving her in your custody while you bargain for information.
Talia studies Nyx through the reinforced glass. The demand lands harder than a threat because it offers no exchange, only a boundary she must choose to cross.

Talia Voss
All right. Mara is released now. But I am giving you the command record, my access trail, and my protection, and you owe me one favor I name later.
Talia enters the release command. Restraint indicators withdraw from Mara’s feed, the canopy unlocks, and a medical drone guides her upright while terminal seven records Talia’s personal authorization.

Talia Voss
She is out of the hold. The door behind me will open to her recovery corridor, but my favor is not optional. You made me choose a side in public.
A security seal disengages beyond the terminal. Mara’s live channel shifts from containment to recovery, while Talia’s identity and command trail become permanently attached to the unauthorized release.
Quest Complete
Free Mara from Talia Voss's custody
Skill Upgrade: Stealth Fair→Good
“I check Mina’s warning channel immediately”
FAILURE (Poor Perception, rolled -3)

Nyx checks her wrist for Mina’s warning channel. The interface is absent, leaving only the bare cybernetic port and the terminal’s reflected security glow.

Nyx crash
The warning channel is not on me.
She attempts the familiar handshake through the terminal’s nearby field anyway. The system finds no authenticated wrist endpoint, then logs the probe as an external contact request tied to Talia’s release record.

Talia Voss
That was not Mina’s channel. You reached for it, but the request stopped here and attached itself to my terminal.
A red notice spreads across the console: OUTBOUND CONTACT UNVERIFIED. The release record now carries a pending contact attempt, and the terminal refuses to forward it without a local device credential.

Talia Voss
Your warning channel is unavailable because you do not have the device that carries it. I can preserve this failed attempt, but I cannot make it safe or private from here.
“I negotiate Talia’s favor to protect Mina”
SUCCESS (Legendary Persuasion, rolled +3)


Nyx crash
Your favor protects Mina Ortez. Keep her address, identity, and warning channel outside every custody record, and redirect anyone who comes hunting her toward me.
Nyx keeps her hands visible and holds Talia’s gaze through the reinforced glass. The failed contact notice remains red, while Mara’s recovery status pulses steadily behind the terminal.

Talia Voss
You are spending my favor on Mina, not yourself. Fine. I will quarantine her identity, erase this contact attempt, and route future inquiries into my custody jurisdiction.
Talia edits the release record. Mina’s name disappears from the pending contact trail, her address is replaced by a sealed protection token, and the failed request is marked routine terminal noise.

Talia Voss
That protection is active now. The unasked-for advantage is simple: I can also issue Mina a protected civilian credential, valid across Helix Meridian checkpoints for thirty days.

Nyx crash
Do it. Then name your favor, and keep it separate from Mina. She is not leverage against me.

Talia Voss
Agreed. Mina is protected, and my favor belongs to you alone. I want the archive brought to me first, before either corporation or law enforcement sees it.
Quest Complete
Protect Mina from the corporate danger
Attribute Upgrade: Reasoning Great→Superb
“i bring the archive to talia”
FAILURE (Great Hacking, rolled +1)

Nyx opens the recovered archive fragments on Talia’s terminal and transfers them across the local link. The data arrives, but the missing final directory leaves the archive incomplete.
Talia’s console rejects the package as insufficient evidence. Its custody index accepts the fragments, then locks the transfer before any concealed payload can be reconstructed.

Talia Voss
These are the recovered blocks, not the archive itself. I cannot take possession of a directory you do not have.
The failed transfer leaves one usable trace behind: a directory request embedded in Mara’s recovery record, timestamped moments before her release and addressed to a local medical node.

Talia Voss
There is a manifest pointer here. It never reached my terminal, but Mara’s recovery system may still hold the missing directory request.
Talia preserves the fragments without claiming them as the complete archive, then opens a restricted route toward Mara’s recovery corridor. The next access point is local, physical, and already authorized.

Talia Voss
Bring me the directory request from Mara’s recovery node. Then I can take the archive first, as promised, without pretending these fragments are enough.
“I access Mara’s recovery node for the directory request”
SUCCESS (Great Hacking, rolled +1)

Nyx enters Mara’s recovery route through the restricted local link, shaping the directory request around the node’s authorized medical handshake. The system admits her connection.
Recovery data opens across Talia’s terminal: vitals, sedation records, transfer timestamps, and a cached directory request preserved beside Mara’s current medical status.

Talia Voss
There it is. The request was generated before her release and routed to this node, not the custody system.
Nyx extracts the directory request and unfolds its metadata. The missing index points to a sealed archive partition attached to Mara’s neural recovery session.

Talia Voss
That is the directory. It names the partition, the recovery key, and the custody event that buried it. You have what I asked for.
The request resolves into a usable access record: Mara’s recovery node holds the final directory, and the partition remains available through the local medical authorization.

Talia Voss
Bring that record to the archive fragments. My favor is due, Nyx, and now we have a real path to the complete archive.
“I ask Talia to merge the directory with fragments”
FAILURE (Legendary Persuasion, rolled -2)

Nyx crash
Merge Mara’s directory with the recovered fragments and build the complete archive here.
Talia routes the directory request from Mara’s recovery node against the fragment blocks preserved on her terminal. The two records align, then lock apart at the final authorization layer.

Talia Voss
I can merge their structures, but not complete the archive. The directory belongs to Mara’s recovery session, and the fragments remain under your unresolved custody trail.
The terminal generates a sealed comparison package instead of a unified archive. It contains matching checksums, missing payload markers, and a demand for session-level authorization from Mara’s active recovery node.

Talia Voss
The merge attempt consumed the local medical authorization. I have the comparison package, but the node will not expose the missing payload through this link again.
The directory request remains available only as a sealed reference on Talia’s terminal, while the recovered fragments stay preserved beside it. The complete archive is still absent, but their shared structure is now fixed.

Talia Voss
We cannot finish this from the terminal. The comparison identifies the missing partition, but completing it will require direct authorization from Mara’s recovery session.
“I negotiate Talia’s first access to the complete archive”
SUCCESS (Legendary Persuasion, rolled -1)


Nyx crash
You get first access to the complete archive. In return, you open Mara’s recovery session, let me verify the merge, and keep the original copy untouched.
Talia studies Nyx through the glass, weighing ownership against access. Then she turns to terminal seven and links Mara’s recovery authorization to the sealed comparison package.

Talia Voss
Agreed. You retain the untouched fragments, I receive first access, and Mara’s session authorizes the reconstruction. No corporate system gets a copy before we see the complete archive.
Talia authenticates the recovery session. The sealed directory opens, checksum chains lock into place, and the missing partition mounts beside the recovered blocks without altering their originals.

Talia Voss
The archive is complete. I have first access, exactly as negotiated. Its core is encrypted, but the directory is live and the payload is present.
A new archive window fills terminal seven: custody routes, replacement orders, and a central payload sealed beneath an authorization tree. The first readable header names a corporate program buried under Helix Meridian.

Talia Voss
Nyx, you earned the first look. Choose what we open together, because whatever this program is, it was built to make people disappear inside the custody network.
“Open the archive’s central payload with Talia”
SUCCESS (Great Hacking, rolled +1)

Nyx borrows terminal seven through Talia’s open local session, routing her interface into the archive’s authorization tree. The untouched fragments remain isolated while the reconstruction layer accepts her craft.

Nyx crash
The payload is protected by a living command chain, not a missing key.

Talia Voss
Keep your hand on the merge path. I will hold the recovery authorization open while you cut through the central seal.
Nyx maps the command dependencies, strips the inherited custody layers, and rebuilds the final authorization branch around Mara’s active recovery session. The central payload unlocks.
The cost lands immediately: Nyx’s disposable decryption key burns out, and terminal seven’s local buffer loses its temporary audit cache. The complete payload remains open on-screen, but the reconstruction cannot be repeated from this session.

Talia Voss
It opened. The program is called PALISADE, and its first directive is not containment. It is identity replacement across civilian custody records.
The payload expands into personnel maps, erased names, and replacement orders linked to live custody nodes. One active file highlights Mara’s transfer, while another marks Mina’s protected credential as a monitored anomaly.
“Is PALISADE actively tracking Mina’s protected credential?”
YES, AND MORE (Likely, rolled 7)

The PALISADE personnel map isolates Mina Ortez’s protected credential and overlays a live tracking lattice across it. The signal is active, tagged as a monitored anomaly, and reporting every checkpoint query back to a hidden PALISADE node.

Talia Voss
Yes. PALISADE is actively tracking Mina’s protected credential, and it has already classified her as a priority anomaly. Every use can expose her location and identity.
A second layer opens beneath the tracker. PALISADE has copied Mina’s protection token into a dormant exemption table, revealing a maintenance route that can suppress the next live location report without altering her credential.

Soren Quill
That is more than surveillance. The exemption table gives you a clean intervention path, and it identifies the PALISADE relay receiving Mina’s reports.

Eidolon-7
Then the credential is not protection. It is a tagged leash. Do not touch the exemption until you know whether PALISADE expects someone to follow it.
The relay address resolves beside Mina’s monitored file, along with a narrow authorization window marked UNUSED. PALISADE has not yet received a successful live checkpoint report from her credential.

Talia Voss
That unused window is your advantage. Mina is being watched, but PALISADE has not confirmed her movement. We have a chance to protect her before the first report lands.
“I trace the PALISADE relay before Mina checks in”
SUCCESS (Great Hacking, rolled -2)
Nyx borrows terminal seven through Talia’s still-open local session and threads PALISADE’s unused authorization window backward through its tracking lattice. The relay path resolves beneath a Helix Meridian utility exchange.

Nyx crash
The relay is local, and PALISADE has not received Mina’s first report.
Nyx reconstructs the route from checkpoint queries, discarded acknowledgments, and the dormant exemption table. The trace identifies PALISADE Relay H-19, hidden inside a municipal traffic-control exchange three blocks from Mina’s apartment.

Talia Voss
You have it. H-19 is the reporting relay, and the route is still clean. Mina’s credential has not checked in.
The trace completes, but terminal seven’s temporary audit buffer fills and overwrites its reconstruction history. Nyx keeps the relay address and route timing; the working path cannot be replayed from this session.

Eidolon-7
H-19 is close enough to intercept before Mina checks in. Do not alter her credential. Cut the relay’s report path instead.
The relay’s physical access route appears beside the completed trace: a maintenance junction beneath the traffic exchange, reachable before PALISADE receives its first confirmed location report.
“I sabotage H-19 without touching Mina’s credential”
SUCCESS (Great Hacking, rolled +1)

Nyx isolates PALISADE Relay H-19 from Mina’s credential path, then plants a silent maintenance fault in the relay’s outbound reporting circuit. The credential remains untouched and valid.
Her code diverts H-19’s location reports into a sealed diagnostic sink and marks the exchange as routine traffic. No checkpoint acknowledgment reaches PALISADE’s tracking lattice.

Talia Voss
H-19 is cut cleanly. Mina’s credential still reads authentic, but the relay can no longer report where it is used.

Eidolon-7
Good. You changed the watcher, not the person being watched. PALISADE will see silence, not a compromised credential.
The municipal exchange accepts the fault as an internal service irregularity. H-19 remains online for ordinary traffic, while its PALISADE reporting channel stays severed and Mina’s protection token remains unaltered.
Terminal seven records the completed intervention without preserving Nyx’s reconstruction path. The relay address, sabotage status, and timing window remain in her active session.

Talia Voss
You bought Mina a quiet window. Now we can decide whether to leave H-19 dark, or use that silence to find the PALISADE node behind it.
Across the archive display, Mina’s monitored credential remains green and unmodified. H-19 shows no outbound report, and PALISADE’s hidden receiver waits in silence beneath the traffic exchange.
“Trace PALISADE through the silent H-19 relay”
SUCCESS (Great Hacking, rolled -2)
Nyx follows H-19’s sealed diagnostic sink backward through its maintenance tables, reconstructing PALISADE’s routing from silent acknowledgments and dormant service headers. The hidden receiver resolves beneath a Helix Meridian traffic exchange.
She isolates the final relay signature and identifies PALISADE Node K-41, a subterranean corporate junction beneath the eastern traffic exchange. Its receiver is active, listening for H-19’s missing reports.

Talia Voss
K-41 is the node behind it. You traced the silence all the way to PALISADE’s receiver, and Mina’s credential still has not appeared there.
The trace succeeds, but Nyx’s crafted route consumes the relay’s last clean diagnostic buffer. H-19 keeps ordinary traffic, while its local maintenance history is permanently erased.

Eidolon-7
K-41 is not waiting for Mina. It is waiting for the report you stopped. That gives you the initiative, but not invisibility.

Soren Quill
I have the coordinates and the receiver signature. K-41 is reachable through a maintenance access shaft beneath the exchange.
K-41’s location, access shaft, and active receiver signature lock into Nyx’s session. PALISADE is exposed behind the silent relay, while Mina’s credential remains untouched and unreported.
“I bait K-41 with a false Mina report”
FAILURE (Great Hacking, rolled -2)
Nyx composes a false Mina report from H-19’s silent diagnostic channel, matching the expected timing and routing it toward PALISADE Node K-41. The packet leaves the exchange cleanly.
K-41 accepts the opening headers, then halts the report before its location payload reaches the receiver. A red audit mark identifies the submission as structurally valid but biologically unverified.

Talia Voss
It took the bait far enough to expose its gate. K-41 requires a live attestation from Mina before it will register movement.
The rejected packet does not vanish. K-41 returns a diagnostic challenge containing its attestation format, a short-lived request addressed to Mina’s protected credential.

Soren Quill
That challenge is useful. The node just told us exactly what it considers proof, and it has opened a response port without receiving her location.

Eidolon-7
Do not answer as Mina. Study the challenge instead. Its expiry window may reveal when K-41 expects the next legitimate checkpoint.
The false report fails to create a movement record, but K-41’s challenge leaves a usable response port and a precise expiry window in Nyx’s session. The node is listening now, on terms it has exposed.
“I access K-41 through the maintenance shaft”
SUCCESS (Great Hacking, rolled +3)
Nyx reaches the maintenance shaft beneath the traffic exchange and opens its service hatch. Her interface catches K-41’s exposed handshake, folds the challenge into the access sequence, and enters the node cleanly.
The shaft descends into a subterranean junction of coolant pipes, fiber trunks, and sealed corporate conduits. K-41’s live architecture unfolds across Nyx’s display, granting her an authenticated maintenance session inside the receiver.

Talia Voss
You are inside K-41. The receiver accepted your maintenance identity without asking for Mina’s attestation.
The successful access exposes more than the receiver. A hidden service map marks K-41’s internal command spine and identifies a local observation port overlooking the node’s attestation processor.

Eidolon-7
That observation port is your advantage. You can watch the attestation processor directly without sending a single response as Mina.

Soren Quill
I have the node map now. K-41 is open to you, and its challenge protocol is visible from the observation port. We can learn what it validates before it expires.
