Skip to main content
Paul Welty, PhD AI, WORK, AND STAYING HUMAN

Synthesis: March 10, 2026

The day in one sentence

A four-project sprint where the outreach pipeline went live (and sent real emails to a prospect), Authexis gained a self-improving feedback loop, Eclectis shipped passkey auth and feed discovery, and Polymathic cleared its entire issue queue.

Cross-cutting themes

Capability pruning is as important as capability building. The Fastmail incident in Paulos is the sharpest example — a “just in case” send path fired when nobody expected it. But the same instinct drove removing review and schedule from outreach, collapsing three manual steps into one. Across all four projects, the day’s best work involved removing things: dead newsletter templates (Polymathic), junk URLs before fetch (Authexis pre-score gate), unnecessary commands (Paulos).

Pipelines are converging on the same pattern. Paulos outreach, Authexis content, and Eclectis feeds all follow the same shape: ingest → process → gate → human decision → output. The Authexis self-improving loop adds a feedback arc that closes the loop. Paulos outreach doesn’t have that yet, but the architecture is ready for it.

Decomposition unblocked a lot of frozen work. Paulos decomposed 4 parent issues into 15 children and shipped 2 immediately. Eclectis decomposed passkey auth into 3 children and shipped 2. The pattern: large issues sit until they’re split; children move within hours.

Per-project highlights

Paulos

  • Incident: Fastmail JMAP client sent real emails to KC via EmailSubmission/set. Entire send capability deleted. Client can only create drafts now.
  • Pipeline simplified: enroll → pipeline → approve (creates Fastmail drafts). Three commands became one.
  • Orchestrate gained decompose action, git-based prospect sync, multi-step pipeline advancement.
  • 8 tests shipped (cos_cmd, qa_cmd).
  • Blocker: 9 issues across two chains gated on SSH access to speedy-gonzales (#343).

Authexis

  • Self-improving feedback loop complete: workspace.learn synthesizes engagement data → scoring and briefing prompts personalize per workspace.
  • Pre-score gate saves ScrapingBee credits by filtering junk URLs before fetch.
  • 5 scout issues filed (#955-#959).
  • Risk: Railway deploy failure (#971) — latest engine code may not be live.

Eclectis

  • Feed discovery: RSS auto-detect from HTML pages, podcast discovery via iTunes API. 20 tests.
  • Integration settings: Raindrop + Readwise token management with masking.
  • Passkey auth backend + login UI shipped. Registration UI (#130) is the last piece.
  • Risk: webauthn_challenges table has no automatic cleanup.

Polymathic

  • Full scout-and-grind cycle: 5 issues found and 5 shipped in one session.
  • Newsletter listing bug fixed — 8 editions were invisible since the migration.
  • Email signatures got LinkedIn/Substack links with UTM codes.
  • Edition 14 staged and sent.
  • March milestone complete (7/7). Issue queue is empty.

Blockers and risks

ProjectIssueImpact
Paulos#343 — SSH to speedy-gonzales9 issues blocked across 2 chains
Authexis#971 — Railway deploy failureNew features not live in production
Eclectiswebauthn_challenges cleanupTable grows unbounded

Numbers

  • Issues completed: 21 across all projects (Paulos 6, Authexis 8, Eclectis 8, Polymathic 5) — counting decomposed parents
  • Tests shipped: ~28 new tests (Paulos 8, Eclectis 20+)
  • March milestones: Paulos 23/24, Polymathic 7/7 complete

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.