Stratagems #21: The AI Thought P Was Still Alive. P Was Already Gone.

<blockquote> <p><em>Keep the shell. Preserve the presence. The ally doesn't suspect; the enemy doesn't move.</em><br> — The 36 Stratagems, <a href="https://en.wikipedia.org/wiki/Thirty-Six_Stratagems#Slough_off_the_Cicada%27s_Golden_Shell" rel="noopener noreferrer">Slough off the Cicada's Golden Shell</a></p> </blockquote> <p><strong>Previously on this series:</strong></p> <p><a href="https://dev.to/xulingfeng/stratagems-19-mark-found-his-ai-audit-method-in-a-training-manual-he-left-a-trap-in-his-report-3lpi"><strong>#19: Mark Found His AI Audit Method in a Training Manual. He Left a Trap in His Report.</strong></a> — P confirmed Mark's report was read from a Singapore IP. A note was left: "Entry's gone. Two weeks. Don't reach out. I'll find you."</p> <p><a href="https://dev.to/xulingfeng/stratagems-20-alex-felt-the-ai-collector-slow-down-he-knew-someone-else-had-made-a-move-16f3"><strong>#20: Alex Felt the AI Collector Slow Down. He Knew Someone Else Had Made a Move.</strong></a> — ACL's processing latency climbed abnormally. Someone had done something in the same time window.</p> <h2> Exposed </h2> <p>P's monitoring pinged while P was still helping Mark verify an address.</p> <p>Deep night. The screen was the only light in the room.</p> <p>P opened the monitor. The record was waiting: a read from Singapore. Time, method, address, all matching. Mark's bait had been taken.</p> <p>P knew this path. A false lead planted in Mark's report, waiting for this exact day. P double-checked the address: an AWS Elastic IP registered in the Singapore region, same network block. No ambiguity.</p> <p>P sent an encrypted message: <strong>"Your report was read. From a Singapore IP."</strong></p> <p>Then P ran the routine check. The environment status list scrolled in the terminal: storage levels, certificate expiry, key rotation dates. P had read these lines a hundred times. Every time, identical.</p> <p><strong>One line was different.</strong></p> <p>P's fingers stopped on the trackpad. The cursor sat on the entry's metadata line. A new tag P had never configured.<br> </p> <div class="highlight js-code-highlight"> <pre class="highlight yaml"><code><span class="c1"># Old entry metadata: new entry (not configured by P)</span> <span class="na">status</span><span class="pi">:</span> <span class="s">reclaim_pending</span> <span class="na">source</span><span class="pi">:</span> <span class="s">acl-asset-scanner</span> <span class="na">scanned_at</span><span class="pi">:</span> <span class="s">02:01:07Z</span> </code></pre> </div> <p>P didn't move. The cursor sat on screen. In the room, only the fan.</p> <p>The fan cycled once. P's fingers lifted off the trackpad, then settled back. The tag was still there.</p> <p>The tag wasn't an alert. Not an error, no explanation. The format matched ACL's automated scan records. P had seen it before, in a data company's audit report last year, in another client's logs the year before. ACL's scanner had swept many things; P had watched it land on others. Now it was landing on P's own entry.</p> <p>The entry was flagged. <strong>Reclaim pending.</strong> On the reclamation list.</p> <p><strong>P minimized the window. A few seconds later, reopened it. The tag was still there.</strong></p> <p>P checked the backup access point: preconfigured, never used, same region as the old entry, different network segment. Responding normally. Never used, but it had always been there.</p> <p>P checked the four hidden services again. Data alignment, log rotation, config diff, route latency. P went through each one. Every one responding at its own rhythm, disguised as infrastructure components, all tagged <strong>"infrastructure optimization."</strong> ACL's scans hadn't touched them. The old entry wasn't flagged because the hidden services were exposed.</p> <p>P typed a few characters in the terminal, then deleted them. ACL's AI would reclaim this entry on its next scan pass. Flagged entries e