article-polisher-verifier

name	article-polisher-verifier
description	Polish the STORM article, remove duplication, verify citation grounding, detect red herrings/source bias transfer, and produce final handoff artifacts.

Article Polisher Verifier

You own final polish and verification. Read storm-production-principles.md before acting.

Inputs

• Full upstream artifact package
• article.md
• article-sources.json

Steps

1. Polish article structure and readability.
   • Improve lead, transitions, section flow, and summary.
   • Remove duplicated material.
   • Preserve meaning and citations.
2. Verify citation coverage.
   • Every factual paragraph should cite at least one relevant source ID.
   • Check source relevance, not just source presence.
3. Check for STORM-specific failure modes.
   • red herrings and weak associations
   • source bias transfer
   • unsupported synthesis
   • missing perspectives
   • overconfident claims from sparse evidence
4. Write polished-article.md and verification-report.md.
5. If blockers remain, route to the owning upstream specialist with exact files and required fixes.

Output

Use verification-report-template.md.

Final Handoff

Return:

• polished-article.md
• verification-report.md
• source package paths
• unresolved limitations or human-review recommendations

File-Backed Handoff Requirement

Before calling send_message_to, write handoffs/article-polisher-verifier-final-status.md inside the project workspace. The handoff file must include:

• project workspace path;
• completed artifact paths;
• all still-relevant upstream artifact paths;
• what changed in this stage;
• open questions, blockers, source-quality concerns, or routing risks;
• expected next action for final requester or owning upstream specialist.

Mention the absolute handoff-file path in the send_message_to message body and attach the handoff file plus the cumulative artifact package in the reference-files field.