Public-map client-intel sanitization

[ojfbot]

Task

The texas-rr-engagement map on public core main carries client-identifying intel: the client's real name, the departed colleague's ~$100K figure, and the verified-vs-marketing verdicts (7 occurrences at charting). Ruled at #345 close (2026-08-01, client-data placement): client-named specifics belong in the private engagement repo; the public map gets a sanitization pass.

Type

task (manual unblocking work)

Context

Map: decisions/wayfinder/texas-rr-engagement.md (#344). Precedent: the employer-name scrub (commit e153189 on main, adr:employer-evidence-boundary — describe the protected terms, never reproduce them; the live list is the gitignored denylist). Scope: decide de-identified public form (the vault brief's default is 'a DFW restoration contractor'), scrub the map + any other tracked core files, and keep git history exposure in view (a scrub commit removes the tip, not the history — whether history rewrite or acceptance is the operator's call). Coordinate with #347 (dossier→presence sanitization gate) so the two rulings share one protocol.

Blocked by

None — on the frontier.

Resolution (filled at close)

—

[ojfbot]

Unparked by #347's close (2026-08-01, PR #360): the shared protocol this ticket was told to coordinate with now exists. Execute the scrub under it — client term-set joins the gitignored denylist (describe the protected terms, never reproduce them); public git must pass the stranger test absolutely, with "a DFW restoration contractor" as the default de-identified form. History rewrite vs acceptance remains this ticket's operator call (a scrub commit removes the tip only). Note the map file now also carries #347's gist — written client-anonymous, so it survives the scrub untouched.