VVANISH
CASE FILE / 2026.10.13PROTECTION SIDE · ILLUSTRATIVE REPLAY

THE SAME ENGINE. A DIFFERENT OWNER.

“I want you to see if you can figure out where the leak https://boredsexy.com/p/<post-id> comes from”

Vanish replays the same eight investigative beats, in the same order, from the rights holder’s side. No real takedown is represented here.

1 QUERY~48 STEPS19 MIN
SCROLL THE TRACE ↓
INPUT → FETCH → PAYLOAD → FRAMES → SIBLINGS → CADENCE → REVERSE → MATCH → FINDING

SAME ENGINE / OWNER-LED REPLAY

Eight chapters.
One uninterrupted run.

A concept replay of the observed GoonBot trace. The same evidence illustrations are redacted or abstract; the final notice flow is invented.

01 / 08 · 17:30 MYTSAME ENGINE / OWNER-LED REPLAY

THE SIGNAL

One link. One question.

A verified rights holder submits one suspected copy for investigation. The same one-query trace begins; this protection-side replay is illustrative, not a claim of a real Vanish case.

  1. Fetched the post URL and searched for it on the open web
  2. Post resolved; its token does not surface anywhere on the open web; began platform tracing
  3. Identified the platform and pulled the post's server-side payload
↔ SAME ENGINE · SAME STEP 01
Abstract stand-in for the supplied post; no source pixels retained.
Abstract stand-in for the supplied post; no source pixels retained.

02 / 08 · 17:33 MYTSAME ENGINE / OWNER-LED REPLAY

THE PAYLOAD

Read what the page reveals.

The app bundle and server-rendered payload exposed the media host and post metadata. The source was not visible in the page headline.

  1. Identified the SSR framework; extracted the dehydrated payload
  2. Pulled the post page HTML
  3. Pulled the platform welcome page HTML
↔ SAME ENGINE · SAME STEP 02
Redacted range-probe reconstruction: anonymous 206 responses for available renditions.
Redacted range-probe reconstruction: anonymous 206 responses for available renditions.

03 / 08 · 17:34 MYTSAME ENGINE / OWNER-LED REPLAY

THE MEDIA

From file to frames.

The CDN responded to anonymous range requests. The engine inspected a 51.6-second rendition frame by frame, not a single thumbnail.

  1. Confirmed video specs; extracted frames across the full timeline
  2. Planned a contact-sheet pass across every post on the same CDN library
  3. Downloaded thumbnails and built the first contact sheet
↔ SAME ENGINE · SAME STEP 03
Reconstructed terminal capture for the frame and sibling scan.
Reconstructed terminal capture for the frame and sibling scan.

04 / 08 · 17:37 MYTSAME ENGINE / OWNER-LED REPLAY

THE SIBLINGS

The next clue was next door.

A contact-sheet sweep of neighboring uploads surfaced source watermarks absent from the target frames. Each thumbnail here is deliberately abstract.

  1. Ran a frame analysis pass
  2. Read the contact sheet: source watermarks found; planned target-frame scan and account sweep
  3. Ran a frame analysis pass on the target frames
↔ SAME ENGINE · SAME STEP 04
Abstract X-over-blur stand-ins for neighboring thumbnails, not original imagery.
Abstract X-over-blur stand-ins for neighboring thumbnails, not original imagery.

05 / 08 · 17:40 MYTSAME ENGINE / OWNER-LED REPLAY

THE CADENCE

Uploads had a rhythm.

Account A showed five-post batches across four observed dates. Repeated short gaps suggested an automated reposting workflow—not proof of who first published the media.

  1. Escalated the reverse search to the stealth-browser layer
  2. Started the stealth-browser session
  3. Reverse search submitted; color matches generic; switched to feature search
↔ SAME ENGINE · SAME STEP 05
Redacted timing reconstruction; source inventory in uploads.csv.
Redacted timing reconstruction; source inventory in uploads.csv.

06 / 08 · 17:41 MYTSAME ENGINE / OWNER-LED REPLAY

THE DETOUR

A blocked route became another route.

Direct reverse-image search was bot-walled. The engine escalated to a stealth browser; the first engine returned generic color matches and no feature hit.

  1. Feature index returned no hit; retried the engine in the standard browser and checked audio
  2. Audio near-silent; routed the engine through the stealth browser; checked the API catalog
  3. Match found; opened the source-sites tab
↔ SAME ENGINE · SAME STEP 06
Abstract X-over-blur search placeholder; no person or reverse-result pixels.
Abstract X-over-blur search placeholder; no person or reverse-result pixels.

07 / 08 · 17:43 MYTSAME ENGINE / OWNER-LED REPLAY

THE MATCH

The image found a gallery.

The second reverse-image route returned a gallery match. The engine checked its source-page chain and verified the matching package in the gallery.

  1. Opened the leak gallery through the stealth browser
  2. Confirmed gallery pagination; checked the stealth-browser screenshot capability
  3. Grabbed gallery page and raw image assets
↔ SAME ENGINE · SAME STEP 07
Redacted reverse-image trace: match recorded, first origin not proven.
Redacted reverse-image trace: match recorded, first origin not proven.

08 / 08 · 17:49 MYTSAME ENGINE / OWNER-LED REPLAY

THE FINDING

A provenance chain, not a verdict.

The evidence packet is ready for owner review. The earlier-copy finding is a lead, not an automatic allegation; the owner decides what belongs in a notice.

  1. Searched for the same-name public figure to rule out a relation
  2. Confirmed the gallery alias is unrelated to the public figure; provenance chain complete; cleaned up tabs
  3. Saved the workflow lessons to the GoonBot skill and memory
↔ SAME ENGINE · SAME STEP 08
Abstract X-over-blur gallery placeholder; no leak host, handle or source media.
Abstract X-over-blur gallery placeholder; no leak host, handle or source media.

AFTER THE SAME EIGHT BEATS / ILLUSTRATIVE

Find it. Prove it. Take it down.

The verified rights holder reviews the matching evidence. A DMCA-style notice is drafted; nothing is transmitted until the owner approves. This is a storyboard, not a claim that a notice was actually sent.

01 / DRAFTEDCopyright removal requestWork and matching-copy evidence attached · recipient: host.example
02 / SENTAfter owner approvalIllustrative dispatch state · no email sent from this page
03 / REMOVEDOnly after re-checkIllustrative confirmed-gone state · no live removal claimed

THE ACTUAL COMPANY

Identity management
in the AI era.

GoonBot and Vanish are two product faces of one identity-tech engine: face ≈ name ≈ handle search, evidence resolution and action. The same machinery that can find a person can help that person find and remove unwanted copies.

Beyond removal: consent-led due diligence, background checks and identity risk monitoring. Powerful search needs authorization, review and clear limits.