Architecture
Trigger → Input → Context → Processing → AI → Output
STEP 1 OF 6
Trigger
Vercel Cron starts the run every Monday morning. Manual runs are protected.
STEP 2 OF 6
Input
Tavily live search plus public event pages and schema.org markup, within each site's rules.
STEP 3 OF 6
Context
Neon stores your focus areas, cities, timezone, event history and run records.
STEP 4 OF 6
Processing
Normalise, de-duplicate, apply the 30-day window and compute deadline urgency in code.
STEP 5 OF 6
AI / Gemini Flash
Scores relevance and writes short, source-grounded summaries. Nothing is invented.
STEP 6 OF 6
Output
A ranked Resend digest, stored records and a dashboard with run history.
Rules the system will not break
30-day window
Only upcoming events that have not ended and start inside the window.
Under 7 days = flagged
A known registration deadline fewer than 7 days away is clearly flagged. Unknown stays unknown.
Source traceability
Every event keeps its original links. Missing facts are shown as unavailable, never guessed.
Reliable delivery
Failures are logged and a retried Monday run can never send a second digest.