Calendar management

Calendar management is the admin surface for the platform’s time spine — every conference, demo day, accelerator cohort, hackathon, and deadline across 16 MENA countries. The admin pipeline starts with submissions (public submit-event form), triages them through the 3-gate editorial verification, and feeds the coverage planning queue.

Admin surfaces

• /founder-account/admin/calendar — list of all events. Filters: verification status, country, category, audience, stage, mode (physical/online/hybrid), coverageEligible, startDate range.
• /founder-account/admin/calendar/queue — submission triage. Pending submissions FIFO-sorted. Inline Verify / Request Info / Reject actions.
• /founder-account/admin/calendar/new — manual create (for editorial-discovered events without a submission).
• /founder-account/admin/calendar/:id/edit — full editor. 30+ fields organized into the 11 clusters from §9.6.
• /founder-account/admin/calendar/:id/coverage — coverage planning surface. Flip coverageEligible + set coverageStatus. Feeds into the Coverage admin queue.

The 3-gate verification

1. Gate 1 — Source authority. sourceUrl points to authoritative channel (organizer domain, verified social, confirmed press release). Aggregator pages do not pass.
2. Gate 2 — Detail accuracy. Date, city, venue, organizer name, deadlines confirmed against the source. Source disagreement = entry is wrong.
3. Gate 3 — Ecosystem relevance. Event is genuinely about MENA startups / founders / investors / ecosystem operators. Generic tech, corporate sales, or non-MENA fails.