Synthesis: March 9, 2026
Five projects, one theme: making the machine reliable
Sunday was a full-portfolio day. All five active projects shipped — 24 issues closed across paulos, authexis, eclectis, polymathic-h, and newsletter. The common thread was hardening: fixing the subtle bugs that silently degrade automation, adding the guardrails that keep things running unattended, and eliminating the manual glue that shouldn’t exist.
The automation pipeline matures (paulos)
Seven issues cleared in paulos, all through the autonomous scout → triage → prep → exec pipeline with zero human intervention. The fixes were defensive — tmux timeouts, PostHog query bounds checking, a broken import in skopos init — the kind of issues that would otherwise surface as 2am failures. The social pipeline got a meaningful upgrade: batch posting to Authexis replaces the old per-post loop that caused scheduling race conditions. Test coverage grew by 19 tests. The March milestone sits at 23/24.
Authexis ships eight features (authexis)
The biggest day by volume. The outbound system got its admin UI for triggering prospect emails, plus voice analysis scores (clarity, consistency, differentiation) injected into email 1. Workspace provenance tracking shipped with a source column and full admin visibility. The feeds system got page scraping wired into the scheduler and daily pipeline, plus UI polish across discovery badges, source type indicators, and button placement. Three triage sweeps cleared 28+ noise issues from Sentry. v1-outbound is at 13/19 with the sending tool evaluation as the key blocker.
Eclectis enters maintenance mode (eclectis)
Three performance fixes and an audit compliance feature. Feed fetching is now concurrent (5x parallelism via asyncio), the admin pipeline page uses SQL aggregation instead of client-side computation, and admin impersonation sessions get audited. All four milestones (M1-M4) are closed — 28 issues total. The project is effectively in maintenance mode, with only a handful of backlogged decompose items remaining.
Polymathic-h completes March (polymathic-h)
Four grind issues merged via parallel agents: a broken pre-commit hook, newsletter format migration, Brevo config centralization, and gitignore cleanup. March 2026 milestone hit 7/7. The ready-for-dev queue is empty — time to either create new issues or consider this in maintenance mode too.
Newsletter edition 14 in progress (newsletter)
Research pipeline ran for edition 14 of Philosopher at Large. Three candidates identified, varying from philosophical essays on busyness to strategy pieces on execution costs. Waiting on Paul’s pick before staging. Edition 13 should land tomorrow (March 10).
Cross-cutting themes
Reliability over features. Paulos and eclectis focused on hardening existing automation. Authexis balanced feature work with noise cleanup. The portfolio is shifting from “build it” to “make it run without watching.”
Autonomous execution scaling. Paulos ran its full pipeline unattended. Authexis processed 8 issues through auto exec. Polymathic-h used parallel grind agents. The pattern is consistent: the agent pipeline handles routine issues reliably. The remaining manual work is scoping decisions and architectural planning.
Git contention in parallel sessions. Paulos hit main-branch divergence from multiple sessions pushing simultaneously. The workaround (git reset --keep origin/main) works but is fragile. This will get worse as more projects run concurrent autonomous sessions.
Risks
- Social batch endpoint dependency: paulos #326 needs authexis #867 deployed, or
social runwill 404 - Eclectis posthog-node: build failure latent behind Vercel cache — will break on cache invalidation
- Authexis DB connection pool: recurring Sentry timeout noise suggests pressure under load
What’s next
- Paulos: decompose test coverage issue #287, check #325 clarification reply, scope server setup (#305/#306)
- Authexis: fix two real Sentry bugs (#877, #879), prep social queue fix (#867), grind ready-for-dev queue
- Eclectis: install posthog-node, verify observability, assess maintenance mode
- Polymathic-h: commit backlog of work logs, check edition 13 delivery, decide on draft essay
- Newsletter: get Paul’s pick for edition 14, stage and send by Tuesday March 17
Why customer tools are organized wrong
This article reveals a fundamental flaw in how customer support tools are designed—organizing by interaction type instead of by customer—and explains why this fragmentation wastes time and obscures the full picture you need to help users effectively.
Infrastructure shapes thought
The tools you build determine what kinds of thinking become possible. On infrastructure, friction, and building deliberately for thought rather than just throughput.
Server-side dashboard architecture: Why moving data fetching off the browser changes everything
How choosing server-side rendering solved security, CORS, and credential management problems I didn't know I had.
The work of being available now
A book on AI, judgment, and staying human at work.
The practice of work in progress
Practical essays on how work actually gets done.
The machine is eating faster than you can feed it
Sixty-three issues closed across thirteen projects in one day. Four milestones completed. And the hardest problem wasn't building — it was keeping up with what you've already built.
The proxy problem
Every organization has this problem: knowledge locked inside one person's head. Today I accidentally designed a solution — and it has nothing to do with documentation.
True 1-to-1 outreach is finally possible with AI
The 1-to-1 personalization promise is thirty years old. It never worked because understanding each person was too expensive. AI changed the economics.