Figurative Language Review Checklist¶
Review checklist — instantiates Literal-vs-Figurative Boundary Preservation
An editorial pass that scans a near-final draft, comparison by comparison, for figures that are unmarked, missing a named feature, or likely to lose their boundary when summarized.
The Figurative Language Review Checklist is a standardized set of yes/no questions an editor runs over a near-final draft, one figure at a time: Is every comparison visibly marked? Is the transferable feature actually named, or left for the reader to invent? Will the marker and the named feature survive a summary, a pull-quote, a headline? Unlike a per-comparison design tool, the checklist is a document-wide quality gate applied late, by someone other than the author, whose output is a list of flagged spots to fix — not a rewrite and not a judgment about whether the comparison was a good idea in the first place. It checks form and durability, not aptness, and it does so at the scale of a whole text.
Example¶
A magazine editor reviews an economics feature that calls inflation "a hidden tax on savers." She runs the checklist. Marked? — "a tax" has no like or as; it reads as a bare equivalence. Flag: soften to "acts like a tax" or add a marker. Feature named? — yes, the piece explains it erodes purchasing power the way a levy would; pass. Survives downstream? — the headline desk will likely compress it to "Inflation: The Tax You Didn't Vote For," which reads as a literal fiscal claim; flag a standing note to the headline writers to keep the "like." She returns three flags — one to the author, two to the desk. The figure stays, because it is a good one; what the checklist guarantees is that it stays marked and does not mutate into the claim that inflation is a statutory tax as it moves toward the cover.[n1]
How it works¶
The checklist is a fixed question list applied per comparison across an entire document, at a late review gate, by a reviewer who is not the author. For each flagged figure it assigns a fix class — add marker, name feature, or add a downstream-preservation note — rather than editing the text itself. Because the questions are fixed and the pass is systematic, the review is auditable and repeatable across issues, releases, or authors; two editors running it should flag the same spots.
Tuning parameters¶
- Strictness threshold — flag every figure versus only those above a risk bar. Stricter catches more but generates noise and fatigue.
- Coverage — every comparison in the document versus a sample. Full coverage is safer; sampling scales to long texts at the cost of misses.
- Who fixes — author versus editor. Author-fixes preserve voice; editor-fixes are faster but can flatten it.
- Downstream scope — which reuse channels the "survives summary" question covers: headlines, social cards, translations, machine summaries.
When it helps, and when it misleads¶
Its strength is catching at scale what per-sentence authoring misses — especially the marker that a headline or summary will silently strip — and doing it as an independent second pass, which surfaces figures the author has gone blind to. Its failure mode is checklist fatigue and rubber-stamping: a list run without attention certifies nothing. It flags but does not fix, so a flag no one owns is worthless, and — because it inspects form — it cannot tell whether a well-marked comparison rests on a badly-chosen source. The classic misuse is treating a passed checklist as certifying the comparison is good, when it only certifies the comparison is properly built and reasonably durable. The guarding discipline is to keep the list short, attach every flag to an owner, and route aptness questions back to the mapping note.
How it implements the components¶
explicit_figurativeness_marker— the first question verifies every comparison carries a visible marker, catching bare equivalences the author let through.shared_feature_selection— a question checks that the transferable feature is actually stated, not left to the reader to guess.downstream_preservation_rule— the "survives summary/headline/quote" question is the mechanism's signature: it certifies the boundary will hold through predictable reuse.
It does not implement literalization_risk_check, transfer_scope_constraint, or audience_interpretive_context — those belong to the Contractual Figurative-Language Scrub, which removes figures that endanger a binding text; the checklist only flags figures for the author to keep and fix. Nor does it write a standalone non_mapping_disclaimer (the Non-Literality Disclaimer).
Related¶
- Instantiates: Literal-vs-Figurative Boundary Preservation — the checklist is the late, document-wide QC gate for bounded comparisons.
- Sibling mechanisms: Like/As Clause Template · Source–Target Mapping Note · Non-Literality Disclaimer · Simile Scaffold Prompt · Comprehension Backcheck · Contractual Figurative-Language Scrub · Translation Marker Preservation Instruction
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Figurative Language Review Checklist operates as a bounded evaluation of existing evidence or work that produces a finding or disposition because it an editorial pass that scans a near-final draft, comparison by comparison, for figures that are unmarked, missing a named feature, or likely to lose their boundary when summarized.
Independent corroboration: The frozen evidence defines Figurative Language Review Checklist as 'An editorial pass that scans a near-final draft, comparison by comparison, for figures that are unmarked, missing a named feature, or likely to lose their boundary when summarized', so its operative form is Assessment, Review & Assurance.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Rhetoric
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Systematic scrutiny of figures and their persuasive implications descends from rhetorical criticism and composition.
Related originating lineages:
- Linguistics & Semiotics — Semantics and pragmatics contribute tests for literal versus figurative meaning.
- Literature & Literary Theory — Literary criticism materially developed analysis of figurative devices and their interpretive boundaries.
Review resolution: Both reviewers agree that rhetoric is primary. I retain literature_literary_theory, linguistics_semiotics only as formative origin lineage(s), without treating every later application as an origin. cross_disciplinary_synthesis is appropriate because the exact artifact combines contributions from multiple professional lineages. Reach is multi_domain as a separate applicability judgment: it does not widen or narrow the recorded provenance. Encyclopedia synthesis is true because the exact generalized artifact is an encyclopedia-authored combination or refinement. The secondary differences are reconciled with no unresolved primary-provenance ambiguity.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
[n1] A dead metaphor is a figure so conventional its figurative origin is no longer felt (a table's "leg," a "hidden tax"). The checklist watches for the moment a live figure is on its way to dying — where the marker has fallen off and readers may take the words at face value — and flags it before publication rather than after. ↩