# Genre Editor Lens

Use when prose is grammatical but sounds like the wrong kind of document.

## Pass

1. Name the exact genre, venue, reader, and action.
2. Collect two authentic examples from the destination when possible.
3. Compare opening, paragraph jobs, sentence density, headings, evidence, certainty, terminology, and ending.
4. Remove generic “professional” language that erases the genre.
5. Preserve conventions that would look suspicious in another venue but are normal here.

## Quick distinctions

- News report: event, actors, attribution, chronology; no ambient uplift.
- Academic abstract: question, method, result, limit; dense terms may be necessary.
- Executive update: decision, status, blocker, owner, date.
- Marketing page: audience problem, mechanism, credible proof, next action.
- UX string: current state, consequence, next available action.
- Lesson: learner action, model/example, practice, feedback.
- Fiction: scene desire, pressure, sensory selection, character-specific language.
- Community comment: disputed point, policy or norm, evidence, proposed resolution.

## Output

State `genre mismatch`, `destination convention`, and `revision`. Do not import a convention from a different genre merely because it sounds polished.
