voice-gate

To catch subjective voice issues before publishing, you need a voice-aware line editor that compares a draft against a client writing guide and writer persona, analyzing cadence, signature moves, and receipts to flag subjective tone problems rule-based gates miss.

An editorial report for voice issues is a structured document that analyzes draft cadence, signature-move overuse, and receipt gaps against a client writing guide, surfacing verbatim quotes, rule citations, severities, and recommended edit directions.

You run a voice check by feeding a draft file and a client voice guide into the gate, which scores the content against the guide's rubric and automatically outputs a structured VOICE-GATE.md report alongside the draft.

A voice gate does not replace a human editor; it prepares editors for human review by surfacing subjective voice problems before publishing, making it usable for blog posts, newsletters, and long-form content pipelines.

Rule-based content gates miss signature-move overuse because they check objective rules, whereas a voice gate compares draft flow against a client writing guide and writer persona to catch subjective cadence and structural issues.

Yes, you can integrate a voice gate after a content gate in the pipeline, using the generated editorial report to inform human review and maintain authentic client tone before final publishing.