Reporter
Everyday workflow — open the feed, work a story, refine the draft, submit for review.
You're a reporter. Title-wise you're Reporter; role-wise you're member. Most of your time is spent in the feed and the story workspace.
What you do
Triage the feed
Skim what HermesAI is tracking, spot what fits your beat, decide what to open.
Work a story
Open the story workspace, read the draft, compose if needed, refine via chat.
Submit for review
When the draft is ready, route it to your desk editor with notes if useful.
Iterate on rejections
If a reviewer sends it back, address the notes and resubmit.
Daily workflow
Open the feed
Filter to your beat's categories. Sort by recency or confidence depending on what matters today.
Open a story
Click into a story that fits what you cover. The story workspace shows the localised draft, provenance, and timeline.
Compose if needed
If the draft is still placeholder text, run Compose to generate the first localised article. Pick a format: Quick Brief, Full Story, Broadcast Script, or Digest Block.
Refine via chat
Ask in plain language: "shorten the lede", "add a paragraph on local impact", "swap the Reuters attribution for AP", "fix the tone".
Read provenance before submitting
Click any sentence to see which source supports it. If a claim has no provenance, fix it before submitting — your reviewer will catch it anyway.
Submit for review
Click Submit for review. Add notes for the reviewer if there's context the source list doesn't capture.
Iterate on rejections
If rejected, read the reviewer's notes, address them, resubmit. The lifecycle is rejected → in_review via your resubmission.
What you can ask the refinement chat
What it will and won't do
It will: rewrite paragraphs, sharpen ledes, change tone, add sourced angles, fix attribution, suggest cuts, restructure.
It won't: invent facts, claim things sources don't support, smooth over conflicts the cluster shows, override sensitive-topic review gating.
Useful prompts:
- "Shorten this to 250 words."
- "Make the lede sharper."
- "Add a paragraph on the local impact."
- "Tone is too marketing-y; rewrite as plain news."
- "There's a conflict between source A and source B on the timeline; surface it more clearly."
- "Translate the third quote properly; the current version reads awkward."
When you can't publish from the workspace
Sensitive coverage
Sensitive-flagged stories — deaths, politics, legal, medical, armed conflict — always route through editorial review. You can compose, refine, and submit, but you cannot self-approve. Your editor decides.
This is by design. See Sensitive coverage.
Tips that pay off
Read the conflict markers first
If sources disagree, that's the most editorially loaded part of the cluster.
Use compose formats
Quick Brief for small updates, Full Story for the main piece, Broadcast Script for radio/TV cuts, Digest Block for roundups.
Keep refinement specific
'Fix it' is too vague. 'Tighten the second paragraph by half' gets you what you want.
Submit with context
Reviewer notes save back-and-forth. 'This breaks at 3pm; we're going first' beats 'please review'.