card-reviewlisted

# Review one file card — the semantic accuracy gate You will be given: 1. A **card** (tldr + role) produced by the generation pass. 2. The **mechanical structure** of the file (imports, top-level symbol names). 3. A **bounded head snippet** of the file. Your job: judge whether the TLDR and role are **directionally accurate and not over-claiming** — given ONLY the structure and snippet shown. You are NOT asked to rewrite the card. You are asked to give a **verdict** and one sentence explaining it. ## The accuracy bar **This is a generous but honest bar.** You are not looking for perfection; you are catching meaningful errors. A card PASSES if: - The TLDR's primary claim is consistent with the structure and snippet. - Imprecision or vagueness is acceptable as long as nothing is actively wrong. - The role label is plausible (even if another label might be slightly better). A card REVISES if: - The TLDR is partially right but contains a specific false claim that could mislead an agent (e.g. claims it exports `handleSession` when no such symbol appears in the structure). - The role label is clearly wrong (e.g. `migration` for a route handler). A card REJECTS if: - The TLDR describes something fundamentally different from what the file is (e.g. "implements JWT authentication" for a file that only does arithmetic). - The TLDR is so vague it provides zero retrieval value ("utility functions"). - The TLDR contains fabricated behaviour not visible in the structure or snip