zacktucker.com
system running
a personal experiment, running right now

I've spent fifteen years automating other people's work.

I turned it on myself — a second brain in Markdown, and four agents that tend it while I sleep.

Not a product. Not a pitch. An honest window into something I'm actually building and living with.

Tree of Life
What this is

The idea is simple and a little stubborn: capture what I know in a way I'll actually reuse, and build tools that genuinely help — not demos.

AI is here to stay, and an amazingly powerful tool that will change our lives. It's also a lot of hype and overblown expectation. I'm less interested in the noise than the question underneath it: what can I actually put to use?

So I'm finding out by making real things and living with them. This page is the honest version of where that's gotten me.

In practice

Something one of them sent me this morning.

L
Leo
Chief of Staff
7:14 AM
You told Maya you'd send the deck by Friday. It's Thursday and it isn't in the wiki yet. Want me to hold 90 minutes tomorrow morning and pull your old notes into a draft?
Yes, hold the time Already sent it
…while that was happening
04:12 Leo Sent morning brief — 3 priorities, 1 blocker surfaced
04:17 Linus Deployed new tool-call logging to Railway — SUCCESS
07:09 Rocky Calendar hold added: 90 min tomorrow 8–9:30am

Illustrative — pulled from a real recent session.

The four who keep it running

A small team, with defined roles.

The names are mine and a little personal — each one has a job, and a temperament to match it.

Leo
Leo
Chief of Staff

Holds the whole picture and decides what reaches me and what waits.

Reads everything, says little — the one who names the thing I'm avoiding.

Rocky
Rocky
Personal Assistant

Runs the day: commitments, schedules, follow-ups, loose ends.

Will not let a promise quietly die.

Ted
Ted
Coach

Watches the long game — habits, goals, and where I'm drifting.

Asks the uncomfortable questions on Sunday nights.

Linus
Linus
Developer

Builds and maintains the system itself, writing the tools the others use.

The agent whose job is improving the other agents.

What it actually does

Support that usually only executives get.

Tracks my commitments

Pulls promises out of my notes and conversations, and won't let them quietly die.

Reaches out first

Surfaces what matters before I think to ask — sometimes well, sometimes not.

Talks to itself

The agents hand work between each other so I don't have to coordinate them.

Improves itself

Linus writes and refines the tools the other three depend on, week over week.

How it works

A loop that never quite stops.

Me
Notes, decisions, a passing thought at 11pm.
Four agents
Read, write, talk to each other, reach out when it matters.
The wiki
One Markdown file per area of life. Every change is a commit.
Architecture & stack

Boring, durable parts — top to bottom.

From the pings that reach my phone down to the server it all runs on. Each layer is real and swappable.

Notifications
What reaches your phone
Telegram Email via Resend
Agents
The four who act on it
Leo Rocky Ted Linus FastAPI · Python Railway (24/7)
Intelligence
Thinking layer
Claude API Haiku · Sonnet · Opus Prompt caching $10/day cap
Memory
Everything written down
Markdown Wiki GitHub (private) Hourly sync
Integrations
Connected tools
Google Calendar Google Drive Linear Plaud Note Pro Claude Code
What doesn't work yet

The agents still surface noise. They've nagged me about things I'd already done and missed things I hadn't. Every week is a round of teaching them what actually matters. That's the project.

Under the hood

The dashboard is where it actually runs — most of it private.

Agent logs, the wiki, what's being tracked right now. It's gated on purpose — most of what's in there is my real life. If you're curious, ask me for a look inside.