The cohort-onboarding reactor — auto-generated from the step registry: the path a new member walks if they go the whole happy way. Ovals are events, blue boxes are pure steps, orange are side-effecting performers, dashed red edges are failures.
When a new member says yes, a multi-stage automation takes over — orchestrated by agents, not by a person working through a checklist. It provisions their mailbox, proves the line works, welcomes them, and tracks their progress, with a human gate on the moves that matter.
The cohort-onboarding reactor — auto-generated from the step registry: the path a new member walks if they go the whole happy way. Ovals are events, blue boxes are pure steps, orange are side-effecting performers, dashed red edges are failures.
When a new member says yes, a multi-stage automation kicks off — orchestrated by agents, not by a person working through a checklist. A cohort agent registers the new participant on a shared agent bus, and the rest of the onboarding runs itself from there.
Our provisioning agent, Penelope, picks up the request and sets the member up with their own @geelenandcompany.com address: a single, idempotent call creates the alias in Exchange Online, creates a dedicated folder, and installs the matching forwarding and filing rules. First, a guard checks that no forwarding is assigned twice — until that is clean, nothing is changed.
This step is the hard gate: nothing proceeds until Penelope has confirmed end-to-end that the alias actually works. Only then do two things start in parallel — the welcome email to the member’s private mailbox (with per-send approval) and a forwarding test that proves the line really gets through. Every outgoing message is copied into the right folder in real time, backed by a 15-minute sweep that also picks up sends from desktop or phone after the fact.
After that, the system reconciles every tracker in a single pass — allowlist, cohort database, funnel stage, member tag, alumni list, send log, and memory. A drift audit has to come back clean, or it does not count as done. From there, a cron job tracks each member’s progress in the Anthropic Academy every 15 minutes (signed up, course started, course completed) via the Microsoft 365 Graph API — entirely without human involvement.
The whole thing is captured in a single, versioned template, with a rule that protects the non-blocking test from silently slipping through the cracks — and an automation arc that stands ready to switch from manual to fully automatic whenever we choose.