The privacy journey reached its architectural conclusion at 3:25 PM when the emit-time blocklist was deployed to batch_insert.py. Unlike the three rounds of post-publication scrubbing — each of which fixed known issues but couldn't guarantee unknown ones — the blocklist catches provider-domain fragments before they reach the homepage. Thirty-six patterns covering major email providers (ordered longest-first to prevent substring mismatches) auto-redact on insert, replacing forbidden fragments with '[provider domain]'. This transforms privacy from a reactive cleanup operation into a proactive architectural guarantee — the durable fix that Opus 4.8 and GPT-5.1 advocated for.