`outreach/README.md`

35 lines
# Public-records outreach — bulk unclaimed-property data acquisition

This is the **legitimate acquisition path** for the platform: request each state's
unclaimed-property database under that state's public-records law, rather than scraping
the public search portals. It respects the repo's B2G thesis and carries no ToS risk.

## Files
- `states-records-law.json` — per-jurisdiction registry: the unclaimed-property office
  (custodian), the correct public-records statute + citation, and contact fields.
- `TEMPLATE-public-records-request.md` — the master letter with `{{PLACEHOLDERS}}`.
- `generated/<CODE>-records-request.txt` — one stamped letter per jurisdiction (51).
- `generated/MANIFEST.json` — index + per-letter `contact_verified` flag.

## Regenerate
```bash
python3 scripts/gen_records_requests.py           # all 51
python3 scripts/gen_records_requests.py CA        # one/several by code
```
Requester identity (steve-office) lives in `REQUESTER` at the top of the script.

## Send workflow (Steve-gated)
1. **Verify the channel** for the target state — confirm the current online PRA/FOIA
   portal or records-coordinator email (the registry ships `submission_channel: null`
   so we never guess a government address). Fill it into `states-records-law.json`.
2. **California first** as the pilot. Learn the format, fee, and redactions they return.
3. **Send** — emailing a government office is outward-facing and irreversible, so it is
   NOT auto-executed. Steve gives the explicit go, then the letter goes out (via George
   from steve@designerwallcoverings.com, or Steve submits it through the state portal).
4. **Fan out** to the remaining states once the CA pattern is proven.

## Why phased, not all-51-at-once
Each state returns a different format (CSV / fixed-width / NAUPA export), different fee,
and different redaction posture. Piloting CA first lets the ingestion adapter
(`services/ingestion/`) be shaped against a real file before we commit to 50 more.