The Third-Party Code

Priya said the integration had one callback endpoint in a retired monitoring vendor.

Bell said the endpoint was pinged six times, each one at the moment a key piece was hidden.

Elise replayed the map from chapter 127.

Each ping matched a corridor route they had not visited yet.

"They used a third party to avoid direct blame," Priya said.

Elise filed a request for the callback payload and got one JSON fragment:

{"actor":"system","event":"queue_lock","reason":"process continuity"}

No IP. No client. No owner.

They traced the vendor’s office from a public registry.

It had been shut down in the year before this case opened.

The office still had an apartment unit with three desks and no internet.

Bell stood in the empty office and found a paper card:

Third party is never neutral. It is a relay for ownership.

Elise scanned the card and compared with court logs.

Every callback had a matching room code from Archive Annex.

At the hearing, the legal team disputed the relevance.

Elise responded with a direct line:

"TP-77 gave the room permission to speak without a person."

The judge asked if they could prove it touched case materials.

Priya replayed the callback times.

Each line overlapped exactly with missing witness segments.

The hall stayed quiet.

That night, Priya received an error message:

Callback endpoint has moved.

Elise wrote:

They moved from third-party to invisible-party.