The site you're reading is the launch
The quest hub went public - this page, the receipts, the real token costs, all of it. Two days after the mail server was born, the story of building it became the launch surface itself.
Public build
Email stresses me out. It's critically important, but it's noisy and annoying, and I always feel like I'm missing something or someone important. Yes, I've tried automated tagging, Superhuman, Cora, and a half dozen other tactics to tame the monster - all to no avail.
This thriving quest is to master my email inbox + outbox by building a net new, agent-native email infra stack. I want to own my email end to end: a self-hosted server, an agent village to manage all the pieces, and real token cost accounting along the journey.
Current problem
Email is a useful and necessary tool - connection, collaboration, coordination, and more - but the stream of emails can be overwhelming and counterproductive.
Thesis
Agents can cost effectively and accurately manage every aspect of a secure, private email architecture from the ground up.
Current progress
It's working! Self-hosted mail server receiving emails, an EA agent triaging the live inbox, and solid documentation along the way.
Follow along
Read the intro essay or subscribe to the RSS means updates come to you - no account, no algorithm. Paste this into any feed reader:.
I find better outcomes when I spend more time than you'd expect on drafting and editing the plans. I like to organize my documentation from a first principles approach with explicit decision and change logs - that way I always know where I started and how I got to where I am today.
Most importantly, it helps me organize my thoughts for how to support others who also seek this thriving quest.
The server is alive. My thrivinghenry.com mailbox receives on a self-hosted OpenBSD box - MX cutover complete, first real mail delivered in under a second. Outbound sends through a self-managed relay: the host refused to open direct port 25, so I routed around it with the break-glass path I'd designed in from day one. The EA agent triages the live inbox daily. The village of agents and daily brief are the next big pushes.
Finish the newsletter relaunch, make the daily brief genuinely useful, then grow the agent village seat by seat.
Design spec approved before any building: mail server, newsletter relaunch, this hub, and a five-seat agent team - success criteria declared first.
Mailbox receiving on owned OpenBSD hardware. MX cutover complete; first real delivery in under a second.
Changelog entry →The EA triages the live inbox at 100% on its golden-set eval - and flagged a prompt-injection attempt instead of obeying it.
The full server was rebuilt from backup during a live drill - target was four hours.
10/10 on mail-tester through a self-managed relay (the host blocked direct port 25, so I routed around it) - SPF, DKIM, and DMARC all green.
Thriving with AI relaunches with replies landing in the new mailbox - the agent team's first real traffic.
This page ships with the site relaunch. If you're reading it, this one's done.
Sys Admin, EA, Editor, Publicist, Chief of Staff - with a nightly self-improvement loop.
The win condition: nothing important lands at the old address anymore.
The quest hub went public - this page, the receipts, the real token costs, all of it. Two days after the mail server was born, the story of building it became the launch surface itself.
The hosting provider refused to open direct outbound - so the relay path designed on day one took over. Messages queued for 23 hours flushed in seconds, and the whole stack scored 10/10 on mail-tester. The foundation workstream is complete.
See the PR →The launch surface went from route inventory to four reviewed page redesigns in one day - drafted as design cards, edited in a shared design pane, shipped as pull requests. 30 routes went dark; 13 pages remain, crawl-audited clean.
See the PR →My thrivinghenry.com mailbox now receives on hardware I control: MX cutover done, first real message delivered in under a second, and an EA agent triaging at 100% on its golden-set eval.
Design spec approved before any building: a self-hosted OpenBSD mail server, a newsletter relaunch on owned rails, this quest hub, and a five-seat virtual agent team - with success criteria declared up front.
Real token spend, per workflow, from the agent run logs. I have yet to see anyone publish this level of detail, so I have no benchmarks or comparables. I don't have a feel for what I believe is the right cost for a daily run, and tracking closely is the fastest way to get there.
Note: I am not counting my $100 Anthropic and $100 OpenAI subscriptions. They are amortized across consulting gigs.
Updated 2026-07-09.
| Date | Workflow | Model(s) used | Full cost | Actual cost |
|---|---|---|---|---|
| 2026-07-09 | golden-set evals + first live triage | Fable, Sonnet | $3.72 | $0.00 |
| Total | $3.72 | $0.00 | ||