How this site runs

I don't update this site by hand. A small team of agents does, each with one job, running on my own laptop. My job is the one thing I don't delegate: deciding what's worth saying.

the team

Scout

Once a week, reads what I shipped and learned and drafts a short update. When a project ships or gets a big feature, it drafts a longer write-up.

Curator

Starts each of my apps with made-up demo data on a spare port and takes fresh screenshots. It never touches my real data.

Redactor

Checks every draft and every image before I see it. Anything private or work-related is blocked, not softened. When in doubt, it blocks.

Publisher

After I approve, adds the post to this site and opens a pre-filled post for X so I can send it with one more tap.

Editor

Keeps a log of what I approve, edit and skip, and once a month proposes updates to the principles the others follow.

the rules

Nothing goes public without my tap. Every post, project update and screenshot reaches me as a card first: approve, edit or skip.
The agents read a short allowlist. They see commits and plans from my projects, notes from books, courses and podcasts I've learned from, and nothing else. They never read my day-job material, my personal notes or my apps' real data.
My decisions become principles. Each approve, edit or skip teaches the team what I'd say and what I wouldn't. That idea comes from a company that turned its founder's decisions into precedent for its agents.
Replies are mine. If you reply on X, you're talking to me, not an agent.