Run: 2026-05-06__010__dash-scrubber-deployment-debrief · Date: 2026-05-06 · Phase 1 author
The Charlie & Bear article meets the brief: three voices (5th grade, 10th grade, expert), a side-by-side summary table at the top, and a long form that reads top to bottom without redundancy. The article passed the deployed dash gate at zero edits on the second pass after a deliberate rewrite. That round trip (write, scrubber finds 36 issues, rewrite to be em-dash-free in prose, scrubber finds zero) is the strongest possible proof of concept: the article walks the talk by being structurally compatible with the rule it's documenting. Demonstrative dashes (the title's em--dashes, code examples, regex patterns) live inside <code> tags where the protect and restore pass shields them.
The 5th grade voice was the hardest to calibrate. Concrete is good ("vacuum eats sneezes"), cute is bad ("oh no, the mean dashes!"). I cannot test this on actual fifth graders. The 10th grade voice could read as "regex tutorial" if a reader skips the systems framing in the third subsection ("why one fix wasn't enough"). The expert voice assumes the reader has felt the "we keep getting bitten by X" pain; if they haven't, the section reads as bureaucratic checklist rather than load bearing architecture.
Like run 008 (Salesfinity weekly pipeline) where writer produced a multi-audience deliverable: one document, layered voices, side-by-side compare. Same shape, different topic. This is becoming the writer's default form for "explain a system to multiple audiences in one artifact." Worth proposing as a brand kit template (document_registry.json entry) so future intern-onboarding articles inherit the structure instead of being reinvented.
An article that documents a rule and then passes that rule on save is the highest possible form of self-evidence. Charlie & Bear get to read a piece of writing that proves the system works by existing.
Generated from 010__writer.md — do not edit this HTML directly.