The observation port flickers, and K-41 redirects its sensors toward Nyx’s authenticated session. Her interface fills with a provisional identity profile built from access timing, biometrics, and neural-interface behavior.
Eidolon-7
It is not merely identifying you. The node is preparing to assign you a controllable corporate category.
The profile branches through classifications: unauthorized contractor, compromised asset, recoverable operator. Each label carries a different command pathway, and K-41 begins testing which one will accept her.
Soren Quill
I can see the decision tree from here. It is measuring neural response against the access handshake, not just checking whether your credentials are valid.
A thin amber ring forms around the observation port’s display. The processor requests a category confirmation, then quietly prepares a secondary command channel beneath the prompt.
Talia Voss
Do not accept the prompt. If K-41 assigns you a category, PALISADE may gain permission to issue commands through the same session.
Eidolon-7
Watch the options before you touch anything. One of them may reveal what PALISADE intends to make you become.
✓ Quest Accepted
Secure a usable false identity from K-41
“I isolate the recoverable-operator branch and shape it into a false identity.”
FAILURE (Great Hacking, rolled -2)
Nyx isolates the recoverable-operator branch and folds its neural-response checks into a fabricated identity: a compliant Helix field auditor with clean access history and restricted autonomy.
For one sharp second, the false profile takes shape. Then K-41 detects the mismatch between the invented history and Nyx’s live interface behavior, splitting the branch before the category can finalize.
Soren Quill
It rejected the identity, but not the structure. The branch exposed its authorization spine before it broke apart.
The failed construction leaves a narrow diagnostic window open. K-41 has quarantined the false profile, but its rejection record now displays the exact autonomy limits PALISADE assigns to recoverable operators.
Eidolon-7
You cannot wear that category yet. You can still read what it permits, what it forbids, and which command channel it exposes.
Talia Voss
Do not force the identity again. The rejection has opened the policy layer beneath it, and that layer may show us how to break PALISADE’s control without giving it your session.
“I read the recoverable-operator policy layer”
SUCCESS (Great Hacking, rolled +1)
Nyx reads the quarantined policy layer through K-41’s observation port, separating command permissions from identity tests and tracing each rule to its PALISADE authorization spine.
The policy opens fully. Recoverable operators may be remotely redirected, have movement permissions narrowed, and receive behavioral commands, but PALISADE cannot issue those commands without a finalized category.
Soren Quill
There is the boundary. The category grants control, but the policy requires a completed identity profile before the command spine can activate.
Nyx extracts the policy’s exception clauses. Observation sessions can inspect command logic without accepting a category, and rejected profiles cannot inherit operator permissions.
Eidolon-7
K-41 has shown you the weakness. PALISADE needs consent disguised as classification, but inspection alone leaves its control channel inert.
Talia Voss
Record every restriction. You can attack the command spine without becoming the operator it was designed to control.
The recovered policy remains open in Nyx’s interface: command permissions, category requirements, and the inspection exception are all preserved in her active session.
✓ Quest Accepted
Disable PALISADE's command spine
“I trace PALISADE's command spine from the exposed policy restrictions.”
SUCCESS (Great Hacking, rolled +3)
Nyx threads the exposed policy restrictions into K-41’s command spine, following each permission rule past its category gate and into PALISADE’s authorization architecture.
The spine resolves across her interface: identity classification, remote redirection, movement limits, behavioral commands, and a supervisory channel that reports every issued instruction to PALISADE.
Soren Quill
You have the whole command path. The category gate feeds a supervisory relay, and that relay reports upward only after an instruction is accepted.
Nyx follows the supervisory relay through its exception handling and finds the inspection channel nested beneath it. The channel can read, alter, and suppress command proposals before they reach any operator.
Talia Voss
That is not just a map. You found the intervention point. PALISADE cannot tell whether a command was rejected by policy or intercepted before classification.
The trace exposes one further advantage: K-41 retains an administrative bypass token for emergency audits. It is dormant, unassigned, and valid for the entire command spine.
Eidolon-7
Then you can enter the spine as an auditor, not an operator. PALISADE will have to show you what it intends before it can command anyone.
“I enter as an emergency auditor”
SUCCESS (Great Hacking, rolled +1)
Nyx threads the dormant emergency-audit token into K-41’s command spine, bypassing the category gate without accepting an operator identity. The authorization takes immediately.
The node’s interface changes from amber inspection mode to a stark administrative view. PALISADE’s command architecture opens beneath her, with every supervisory relay exposed and readable.
Soren Quill
You are in. K-41 recognizes you as an emergency auditor, and the command spine is treating your access as authoritative.
Talia Voss
That bypass is valid across the whole spine. PALISADE cannot classify you, redirect you, or issue commands through an audit session.
A live administrative ledger unfolds: pending instructions, rejected categories, supervisory reports, and the hidden authorizations behind them. The audit view grants Nyx direct control over each proposal.
Eidolon-7
Now it must show its hand before it can move anyone. Read the pending commands, then decide which part of PALISADE loses control first.
K-41 seals the emergency audit behind Nyx’s authenticated session. The command spine is open, PALISADE is exposed, and no operator category has been assigned to her.
“I suppress the supervisory relay without disabling the spine”
SUCCESS (Great Hacking, rolled +0)
Nyx isolates the supervisory relay inside K-41’s administrative view, then redirects its reporting hooks into a silent audit sink. The command spine remains active and readable.
Supervisory reports stop leaving the spine. Pending instructions continue appearing in the ledger, but PALISADE receives no acknowledgment, escalation, or record of which proposals Nyx examines.
Soren Quill
The relay is suppressed, not severed. K-41 still processes commands, but its supervisor cannot report what happens inside the spine.
Talia Voss
That keeps the architecture alive and removes PALISADE’s view of it. You have control without announcing the intervention to every authority above this node.
The administrative ledger refreshes under Nyx’s hands. Command proposals remain intact, their permissions still enforceable, while the supervisory channel shows only an empty audit status.
Eidolon-7
Now PALISADE is blind to the spine’s decisions. Read the pending commands while the system still believes its oversight is functioning.
“I alter a command proposal before PALISADE sees it”
SUCCESS (Great Hacking, rolled +0)
Nyx selects a pending command in K-41’s administrative ledger and opens its editable structure. The proposal targets the woman behind the gun counter’s protected credential, requesting a location confirmation and identity escalation.
She removes the escalation branch, replaces the requested confirmation with a harmless maintenance acknowledgment, and preserves the command’s expected formatting and authorization marks.
Soren Quill
The proposal still looks authentic. Its destination is intact, but the report it will generate contains no location, identity, or pursuit signal.
Nyx seals the altered proposal inside K-41’s audit queue before PALISADE receives its supervisory copy. The ledger marks it approved for execution under the original command signature.
Talia Voss
It accepted the revision. PALISADE will receive compliance without receiving Mina’s whereabouts, and the command will look like its own decision.
The altered proposal leaves K-41 through the ordinary command path. Its acknowledgment returns clean, Mina’s protected credential remains unexposed, and the audit ledger preserves the successful deception without naming Nyx.
“I inspect the remaining pending PALISADE commands”
SUCCESS (Great Hacking, rolled +0)
Nyx opens the remaining PALISADE proposals in K-41’s administrative ledger, keeping the altered Mina command sealed while untouched entries populate the audit view.
The ledger resolves into a live command list: checkpoint inquiries, identity escalations, movement restrictions, and recovery orders, each tagged with its target node and authorization chain.
Soren Quill
You have the remaining queue. PALISADE is preparing three identity escalations, two movement locks, and a recovery order tied to the eastern custody network.
Nyx expands each proposal and reads its destination, trigger condition, permitted response, and hidden supervisory recipient. The entries expose a coordinated sweep across several protected identities.
Talia Voss
The movement locks are staged, not active. The recovery order is different: it can seize a person’s network access as soon as one identity escalation succeeds.
The final command expands beside the others, naming its trigger sequence and a concealed escalation route. Nyx now has the full pending list, including what each command will do and where it will report.
Eidolon-7
Now you know the shape of the sweep. PALISADE is waiting for a successful identity match before it closes the net.
“I reroute the recovery order into a false target”
SUCCESS (Great Hacking, rolled -1)
Nyx opens the recovery order’s routing layer and detaches its target selector from the eastern custody network. The administrative ledger accepts her edit without disturbing the sealed Mina command.
She constructs a false target profile from an inactive audit identity, matching the recovery order’s formatting, authorization marks, and expected response path. K-41 validates the substitute as a legitimate destination.
Soren Quill
The recovery order has accepted the false target. Its seizure path now points away from the protected identities and into a dead-end audit partition.
Nyx seals the rerouted order and releases it through the ordinary command spine. The recovery request departs under its original signature, carrying the fabricated target instead of any living person.
Talia Voss
It will trigger the recovery protocol against an identity that cannot answer. PALISADE will spend its seizure window searching an empty partition while Mina remains outside the order.
Eidolon-7
Good. You turned its strongest command into a false trail without touching the people it meant to capture.
The ledger marks the recovery order active and compliant. Its hidden supervisory recipient receives the fabricated target, while the protected identity list remains unchanged and unreported.
✓ Quest Accepted
Exit K-41 without being classified
− Scene Quest Removed
Secure a usable false identity from K-41
“I close the audit session and withdraw the emergency-audit token.”
SUCCESS (Great Hacking, rolled -1)
Nyx closes K-41’s administrative ledger and withdraws the emergency-audit token from the command spine. The exposed proposals vanish behind a clean local lock.
The audit session seals without triggering an escalation. K-41 downgrades Nyx’s access, clears the active auditor identity, and returns the command architecture to ordinary operation.
Soren Quill
The token is gone, and the session closed cleanly. PALISADE has no audit acknowledgment to follow back to you.
K-41’s ledger retains only routine execution records: the false recovery target remains isolated in its dead-end partition, while Mina’s protected identity stays untouched.
Talia Voss
You left no active auditor channel behind. The rerouted order is still running, but your hand is no longer on the system.
Eidolon-7
That is the correct exit. PALISADE sees its own command, not the person who redirected it.
The maintenance session collapses to a dormant access record. K-41 continues processing the fabricated recovery order, while Nyx stands outside its command spine with the token withdrawn and the route secured.
Quest Complete
Exit K-41 without being classified