The Account on the Watchlist

The evacuation corridor ended at a service lobby with a public emergency relay built into one wall. Its display still carried the city seal and a steady notice: EXTREME REPAIR MODE. PUBLIC SAFETY CHANNELS REMAIN AVAILABLE.

Marcus stood at the terminal with the unedited journal loaded on a storage wafer. Chloe had taken the corridor’s other access panel apart far enough to keep the door from sealing behind them. Ethan sat on the low maintenance bench, the signer’s local copy open across his tablet.

“Give me a minute,” he said.

Marcus glanced over. “You’ve had the whole walk.”

Ethan had been staring at the same rows since they left the sublevel suite. The journal captured Sella Orin’s authorization, the nested request, and the redaction that followed. He had copied the raw records onto two separate devices. He could explain the sequence. He could not explain why anyone had singled him out.

He scrolled back to the entry immediately before the authorization. It carried a date from eighteen days earlier.

“Here.” Ethan enlarged the line. “Subject binding.”

Chloe came over. Her eyes moved across the row once, then returned to the timestamp. “Your account?”

“Hash matches mine.” He compared the final characters against the current account token. “The binding predates the test run. It predates the overflow night.”

Marcus set the wafer down. “What does the condition say?”

“Only that my account was to be watched for a boundary-intent evaluation. The detail field is sealed under the same Continuity Safeguard authority.” Ethan tapped the line. “Sella’s authorization is attached to the later request. This earlier entry has a separate service seal.”

Chloe leaned closer to the screen. “Someone selected you before your script triggered the request.”

The phrase seemed too simple for the rows he was seeing. Ethan checked the timestamps again, then searched the local journal for the account hash. One match. A binding created, acknowledged, and retained. His test harness had not wandered into a trap by chance. Someone had put his account where the trap could find it.

He kept looking for an innocent explanation. A test cohort, perhaps. A routine audit of low-risk users. A retained security list from the years he had worked on Aether’s boundary checks. Each possibility required records that the journal did not contain.

“Can you pull the service seal?” Marcus asked.

“Not from this copy. It’s referenced, not stored.” Ethan looked up. “The signer hardware here accepted the binding. The identity behind the service seal could be elsewhere.”