User journeys

Coverage drives three reader journeys (discover → read → traverse to mentioned entities) and one editorial journey (event happens → planned → written → published). The editorial journey is more structured than other modules because of the strict Calendar dependency.

Reader journeys

1. From a Calendar event details page: "Coverage" section lists every CoverageArticle with parentEventId = this event. Click → /coverage/:slug.
2. From SERP: search for "RiseUp 2025 recap" → JSON-LD NewsArticle/Article click → directly to /coverage/:slug. Coverage URLs are the highest-AEO-value pages in the module.
3. From a founder/startup profile: "Mentioned in coverage" rail lists every article that name-checked them. Click → article. Reader can then traverse to other mentioned entities from the article sidebar.

Editorial journey

1. Step 1 — Plan: On a CalendarEvent details page (admin), editor flips coverageEligible=true + coverageStatus='planned'. This adds the event to the Coverage editorial queue.
2. Step 2 — Attend: A staff editor or trusted contributor attends the event, takes notes, photos, gathers pitch outcomes, talks to founders.
3. Step 3 — Draft: In the admin draft surface, editor picks the parent event from a search picker, picks the kind, writes title/dek/bodyHtml in EN + AR, attaches cover image, picks mentioned founder/startup/opportunity/file IDs.
4. Step 4 — Fact-check: Second editor verifies every named entity, every pitch outcome, every quote. No "from memory" facts — everything must be sourced.
5. Step 5 — Publish: publishedAt set; parentEvent.coverageStatus flips to 'covered'; reverse-link appears on the event details page; mentioned-entity reverse-lookups light up on every cited founder/startup profile.