post-merge-voice-gate

To detect generator voice artifacts in a merged draft document, analyze `output/DRAFT.md` and `outline/transitions.md` to identify specific high-signal stems and slash-list patterns. This process flags automated writing like planner-talk for correction.

Planner-talk is a generator voice artifact that introduces automated phrasing into academic writing. Remove it by routing identified voice issues back to the earliest responsible source artifact for correction, ensuring a consistent human-like tone.

Fix transition notes that slipped into a draft paper by running a post-merge voice gate to flag phrases like "To keep the chapter...". This directs corrections back to the original transition notes instead of applying ad-hoc edits.

You can use a voice gate to check draft polishing consistency without manual review by automatically analyzing `output/DRAFT.md` for axis-label lists and planner-talk. It routes fixes to the source artifact, maintaining consistent tone.

The limitation of automated merge review for draft documents is that it requires specific input files (`output/DRAFT.md` and `outline/transitions.md`) to function. Without these source artifacts, it cannot route fixes or identify high-signal stems.

Post-merge-voice-gate works with existing content automation workflows by analyzing draft and transition files to detect generator voice. It routes corrections back to source artifacts, integrating seamlessly into automated draft polishing pipelines.