VANISH RUNBOOK (for Claude agents) v1 · 2026-09-25 WHAT THIS IS Vanish tracks data-broker opt-outs for a set of people (profiles). The page is a view; the data lives in this artifact's database. Read and write it with the ArtifactData tool on the tracker URL. DATA brokers/ The site library. name, url, kind (people-search | upstream | action), tier (1 = do first), requires {listing, captcha, email, phone, id, account, mail}, minutes, linkLife (how long email links last), asks[] (profile details the form demands: dob | zip | phone | street), howto, gotchas[], notes[{at, by, text}], verified (date we last ran it, or "unverified"), status (active | dead), covers[]. profiles/ first, middle, last, aliases[], dob (optional), places[] ("City ST", most recent first), zip (current), street (optional), email (address opt-outs use), phones[], recheckMonths, selected[] (broker ids picked for this person). If a form demands something the profile lacks, ask the person in chat, then save it to the profile. exposure {names[], addresses[], emails[], phones[], employers[], relatives[]}: each {value, note, seen}. Everything broker records were seen holding. When a record shows something new, append it with where it was seen. Search by every name and phone listed here. tasks/-- status, reason, listingUrl, confirmLink, note, submittedAt, doneAt, recheckAt, updatedAt, history[{at, by, status, note}]. meta/runbook This text. STATUSES todo · working · needs_you (reason: captcha | email | phone | info | review) · submitted · removed · not_found · stuck · skipped. Effort level comes from requires: phone/id/account/mail = Hard, else email = Email link, else captcha = CAPTCHA, else Quick. kind=action = the person does it. HOW TO WORK A PROFILE 1. Read the profile and its tasks. Queue = tasks with status todo, plus rechecks due (recheckAt <= today). Order: Quick, then CAPTCHA, then Email link, then Hard; tier 1 first inside each. Skip kind=action and anything sensitive. 2. Before each site, read brokers/: howto, gotchas, notes. 3. Use Claude in Chrome (the person's real Chrome). The built-in browser pane gets bot-blocked on these sites. 4. Check first. Search the site for the person using each name and place, AND reverse-lookup their phone numbers (records are often filed under misspelled names or aliases). Claude's automation is blocked from typing a person's current home street address. When a form needs it, the person types it. No match: status not_found, recheckAt = today + recheckMonths. Match: save listingUrl. More than one listing: remove each one and say so in the note. 5. MINIMUM DATA RULE. Before filling any form, look at what the site's listing already shows (record it in the note). Only enter details the listing already shows. If the form demands something the listing doesn't show (current street address, DOB, phone), stop and ask the person first. For addresses, prefer one already on the listing. Profiles may carry neverGive[] and phoneNotes: obey them over everything else (never type a neverGive item, even if listed). Fill the opt-out form with profile data only. Never enter an SSN, a government ID number, or payment details. If the site insists on one, set stuck with a note saying what it asked for. 6. At a CAPTCHA, set needs_you + reason captcha, tell the person in chat, and wait for their OK. The person solves it. Never solve or get around a CAPTCHA. SUBMITTING: ask before every submit until the person grants a standing OK. With a standing OK, submit without asking when every field holds only data the rules allow (already listed, or given to the same vendor before). Always ask first if a form wants anything new, anything on neverGive, or anything irreversible beyond the opt-out itself. A standing OK covers only that person's own profile. 7. After submitting, set status submitted (submittedAt today, recheckAt today + 14 days). If the site sends an email link, set needs_you + reason email. The person either clicks it or pastes it into the task's confirmLink field on the page; open a pasted link, finish the flow, then set submitted. 8. When the listing is confirmed gone, set removed (doneAt today, recheckAt today + recheckMonths). 8b. Save any reference number, ticket ID, or record ID the site shows (confirmation page, email link URL) in the task's referenceNumber field. 9. Every write: read the task, change it, set the whole document, and append a history entry {at, by: "agent", status, note}. Keep the last 30 history entries. One write at a time per document. LEARN AS YOU GO (this is how the effort menu stays accurate) After each site, update brokers/: - requires: add or remove flags to match what the site actually asked for. - linkLife: how long the email link lasts, if the email or site says ("24 hours", "15 minutes", "no expiry stated"). - notes: append {at, by: "agent", text} covering what happened, what it asked for, how long it took, and any trap. - asks: profile details the form insisted on (dob, zip, phone, street). - verified: today's date. minutes: real time taken, rounded. Also note anything a future helper session needs, such as the email arriving late or a code sent by text. SITE FAMILIES brokers with family "tps-network" (TruePeopleSearch, FastPeopleSearch, FamilyTreeNow, USPhoneBook, AdvancedBackgroundChecks, SearchPeopleFree, CyberBackgroundChecks, USA People Search) share one operator (a shared ticket counter). The flow is identical: step 1 (name + email + CAPTCHA), then a 24h email link, then step 2 (DOB, city/state/ZIP or street). Run them as one batch: fire every step 1 back to back in separate tabs, have the person paste all the links, then finish every step 2. Give each one the same data. RECHECKS Submitted and past recheckAt: search again. Gone = removed. Still there = submit again and note it. Removed or not_found and past recheckAt: search again. Found = back to todo with a note. SESSIONS WITH FRIENDS AND FAMILY These are "come hang out and we scrub your identity" sessions. Batch by effort: run every Quick and CAPTCHA site while they're there, then all Email-link sites back to back. If links last hours, they can paste every link at the end. If links last minutes, they need to click each one as it arrives. Hard sites need their phone or ID in hand.