slopbeth

Slopbeth

Remove machine-writing tells without sanding away the author's meaning or voice. The target is not "detector-proof" prose; it is dense, specific writing where every sentence carries load and detector results stay dated and tool-specific.

Workflow

1. Classify the task: rewrite; critique; benchmark; detector-facing validation; or skill maintenance.
2. Separate the brief from the artifact. Long inputs often mix the material with instructions about it: "the note should keep that texture"; "do not turn this into a lesson"; "the rewrite must not promise that the problem cannot recur". Those sentences address you, not the reader. Do what they ask and leave them out of the output. Reprinting them is the same class of error as inventing content, and preservation and density checks will not catch it, because instruction text is specific, sourced, and dense.
3. Preserve facts first. Lock named entities; numbers; dates; URLs; citations; quotations; technical claims; explicit uncertainty; and the user's requested stance.
4. Set the evidence boundary. When the user supplies only vague copy, switch to evidence-bound mode: do not invent or assert product features; dates; people; metrics; workflows; examples; customer facts; or outcome claims. Unsupported claims such as "faster decisions," "better alignment," "reduced friction," "confidence," or "momentum" must become proof gaps, questions, or explicitly attributed claims.
5. Diagnose clusters, not isolated words. Look for filler; vague significance language; formulaic contrast; promotional inflation; padded lists; generic uplift; actorless claims; summary endings; and ornamental formatting.
6. Rewrite in this order: preserve claims and constraints; cut scaffolding and inflated abstract nouns; apply Orwell's six rules as generation defaults (short word over long, cut deletable words, active over passive, no printed-cliche metaphor or jargon, but break any rule sooner than write something unclear or graceless); make each sentence carry a claim, example, constraint, image, number, consequence, or argumentative move; match the user's register; remove concrete details that are not sourced or clearly labeled; check for meaning loss, bland-clean prose, formula replacement, and over-editing.
7. Validate when files or before/after text are available. Use the scripts in scripts/ for repeatable checks, then apply judgment for meaning, voice, and sentence-load failures.
8. Output the revised text first for normal rewrite requests. Add a compact note only when it helps explain material changes, preservation risks, or remaining issues.