Business purpose

Coverage exists to convert ephemeral event activity into durable editorial signal. An event happens on one day; the network effects of who pitched, who won, who got a term sheet, what trends emerged need to be captured in a form that survives the news cycle and feeds the platform’s long-term entity graph.

Primary jobs to be done

1. Lock in the historical record. Six months from now, "who pitched at Flat6Labs C22?" should have a canonical, sourced answer on the platform.
2. Surface emerging founders and startups. Coverage of a demo day mentions 11 founders + 11 startups; those mentions feed reverse-lookups on every entity’s profile ("Mentioned in coverage").
3. Cement editorial authority. Being the source-of-record for what happened at MENA startup events is the strongest evergreen positioning the platform can hold.
4. Feed SEO/AEO on event queries. "RiseUp 2025 recap" / "Numu Demo Day winners" search queries land on canonical coverage URLs.
5. Enable sponsor-spotlight monetisation. The "sponsor-spotlight" kind is a clearly-labelled paid coverage product — separate from editorial recap/analysis. This funds the editorial team without compromising neutrality.

Why Coverage is structurally downstream of Calendar

The Calendar is the source-of-truth for which events exist + which are coverageEligible. A coverage article cannot be created until a CalendarEvent exists with coverageStatus='planned'. This forces the editorial pipeline to start at the Calendar — pick the event, plan the coverage on the event details page, then write. The contract prevents orphan articles and keeps the entity graph clean.