Caleb's notebook

Last redrawn Oct 29, 2026

Agency

Not languages or frameworks: this is how work moves from an idea to a release. I ask in Basecamp or the mate chat, firstmate turns the ask into a brief, a second mate looks after each project, and crewmates do the typing, each in its own worktree. Nothing ships until the review pipeline passes and I merge.

How work moves from an idea to a release, and how questions, decisions and review findings travel back: me, Basecamp, firstmate, the second mates, crewmates, the review pipeline, GitHub and releasemeideas, calls, the mergeon my phone over TailscaleBasecampHQ to-dos and chatbasecamp-mate keeps it syncedfirstmatethe lead agentpicks up asks, writes briefs,hands them to second matesfirstmate's ownbasecamp-matebasecamp-axicaleblenoir.comynabynab-mcp-servertatext adventure:server · engineterminalomarchycontributionsto OmarchysfcSacred FeminineCommunity appdraftDraft, thewriting toollocal-appsmate · pocket-kitcrewmatesClaude Code · Codexone worktree per tasktmux · herdra pane for every agentreview pipelinereview · tests · lintbefore anything is pushedGitHubpull requestI read it and mergereleasedeploys on mergeto-dosmate chatpicks uprunssecond matesreview findingsrun inhands offopens PRmerge

Recent changes, start to finish

Back where I left off · Draft

  1. I ask Draft to take me back to the writing session I left.
  2. Firstmate files it: new work waits until this week's blog post is live.
  3. My post goes live, and firstmate routes the ask to the Draft second mate.
  4. A crewmate builds it: a quiet "Resume writing" link on the home screen.
  5. It is reviewed, tested and documented.
  6. It opens github.com/calebl/draft-web/pull/106.
  7. It merges, and Draft redeploys.
  8. The Draft second mate reports it live.
  9. Firstmate passes it on.
  10. It posts in Basecamp chat.
  11. It reaches me.

Two sessions from one tap · Draft

  1. On my phone, I tell Draft: starting a new session just made two.
  2. The note reaches firstmate, which routes it to the Draft second mate.
  3. The Draft second mate finds the cause in the request log: the app was preloading the New Session link, which created a session.
  4. At the same time, it starts a crewmate on the fix: a session now starts only on a tap.
  5. The answer goes back up through firstmate.
  6. It reaches me: my writing is safe, and here is why it happened.
  7. The fix is reviewed and tested.
  8. It opens github.com/calebl/draft-web/pull/104.
  9. It merges, and Draft redeploys.
  10. Firstmate tells me the fix is live.