The Big Picture
This is a largely autonomous system. It discovers events, monitors its own health, and fixes many of its own bugs — every day, with minimal human intervention. The Observatory exists to give transparency into this process so people can see how an autonomous AI system actually works. This isn't a black box.
How It Works
The whole system, end to end — it runs largely on its own, with a human reviewing only the riskiest changes.
Discovery Pipeline
— runs nightlyOpus reviews recent results and decides what to scrape and search today
Scans roughly a dozen curated sources and the web for London AI events
Catches the same event listed on different platforms
AI confirms: real event? In London? AI-related?
Tags audience, skill level, and free/paid
Approved events appear on the calendar
Self-Monitoring
— evaluates every runCollects data on scraper health, error rates, source performance, and calendar coverage
The most powerful Claude model reviews everything, assigns a health grade, and identifies issues
Creates search queries, manages sources, and escalates code issues for the repair agent
Self-Healing
— runs daily, 2 hours after discoveryPicks up the highest-priority action item from the monitor
Diagnoses the root cause — fetching the live web page through a supervised relay, since the agent deliberately has no direct internet access
Reads the codebase, understands the bug, and writes a fix
Runs the full test suite, then tests the fix on a draft branch against the real live page — a fix that fails the rehearsal never touches production
Ships proven low-risk fixes to production automatically; flags riskier changes for a human to review first
The Independent Watchdog
A separate watchdog — its own program, running outside this system on its own schedule — independently counts how many LondonAI events exist and compares that to how many the calendar has captured. Because it lives outside the agent, the system can't grade its own homework: if coverage quietly slips, the watchdog is the thing that catches it.
Multi-Model Architecture
Three Claude AI models split the work based on what each task needs — like having a junior analyst, a senior reviewer, and a strategic director on the same team.
Handles 80% of decisions — validation, classification, dedup
Evaluates new sources and extracts event details
The system brain — plans each run and monitors system health
Community Input
Anyone can submit an event the system missed using the “Missing an event?” button on the calendar. The agent scrapes the submitted URL, validates it, and adds it to the calendar — all in the same daily run. It also learns from each submission, adding new sources and search strategies to find similar events in the future.
Where It Goes
Each morning, Claude summarizes the overnight run — what it found, what broke, and what it cost — and emails it to the operator. It's how a human keeps an eye on the system without having to run it.
Every Sunday evening, anyone who's subscribed gets the week ahead in London AI events delivered straight to their inbox.
Agent Performance
What the agent is doing autonomously
Events Added (Last 30 Days)
Recent Activity
Under the Hood
How the agent thinks, decides, and sometimes fails
Health Report
Automated self-evaluation of system effectiveness
| Grade | Scraper Health | Sources | Error Rate | Activity |
|---|---|---|---|---|
| A | 80%+ | 4+ contributing | <5% | Events added in last 7d |
| B | 60-79% | 3+ contributing | <10% | Active discovery |
| C | 40-59% | 2-3 contributing | >10% | Some source issues |
| D | <40% | <2 contributing | High | Multiple broken scrapers |
| F | — | — | — | System not running |
Updated 2026-03-29: Grades now measure infrastructure health (what the agent controls), not event count or empty days (which reflect community activity). The agent still actively maximizes calendar coverage as a separate mission.
Human Stewardship
How humans guide the agent's growth
Human Stewardship
How humans guide the agent's growth using Claude Code
When an organizer renamed an event, the calendar kept the old title for up to a week. The nightly scrape already saw the new title, but it only copied the date, time and venue onto the stored event; the title waited for the Sunday re-check. The Larger Half added Perplexity as a partner and renamed its October 21 workshop on Luma, and the listing here kept the old name with Sunday four days away. Correcting it by hand was ruled out. The mechanism had to do it.
The nightly scrape now takes the organizer's new title, with two guards. The new title has to come from the same source as the stored event. On Luma, where each event keeps a permanent ID, the same event can take any new title, which is what the Sunday re-check already trusted. Everywhere else the new title must keep at least 60% of the old title's words, because on other platforms a changed heading can mean a different talk in the same slot or a page redesign; those still wait for Sunday. It adds no page fetches and no AI calls.
The next run, on October 15, changed the listing to "The Larger Half x Perplexity: AI at Work, Hands-On Workshop" within minutes of reading the calendar. Another Luma rename that week, "Build Your Life OS" to "Build Your Business and Life Operating System", shares only 3 of 8 words with the old title. The 60% rule would have refused it, which is why Luma events take any new title.
This agent is developed iteratively with Claude Code. The collaboration is part of the project's identity.