afaro-drop-submitlisted

# Afaro data removal: California DROP request Files one deletion request with California's state platform, which registered data brokers are required to process, instead of one form per broker. **Status: scaffold. Nothing in this skill runs yet.** The steps below describe what Phase 1 will do. If a person asks for it today, explain what it is, say it is not built, and offer the per-broker guided run instead. --- ## When to use - The person's profile has `state_of_residence` set to `CA` and they ask about the state deletion request. - The person asks why they would still file per-broker opt-outs if California has one request. ## When NOT to use - The person does not live in California. The platform is a California residents' right, and a request from elsewhere is not one Afaro will file. - The person wants the per-broker opt-outs. Use `afaro-orchestrator`. - The person wants to know who lists them. Use `afaro-exposure-scan`. --- ## Required inputs 1. **The profile path**, with `state_of_residence` equal to `CA`. 2. **A capture of the current platform page**, read on the day it is used, under the same provenance rule every manifest follows. 3. **The person, present.** The request is theirs, made in their name, and the state platform verifies them directly. Stop if `state_of_residence` is anything other than `CA`. --- ## The framework **One request, many brokers.** The state platform takes a single verified deletion request and makes it available to registered data