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

Skillexis — 2026-03-24

What shipped

No code changes shipped. The autonomous orchestrate loop ran continuously, polling the triage queue throughout the day. All 10 open issues remained in their routed states — the pipeline is fully triaged with a healthy backlog of grindable work, but no execution commands were dispatched by the orchestrator.

The only commit was the previous day’s rollover work log (pushed at 2:08am), capturing the productive March 23 session that fixed the open redirect vulnerability and surfaced 10 scout issues.

Completed

None.

Release progress

  • Simulation practice: 3/4 closed. #172 (pass lesson context through to simulation practice) remains in-progress.
  • Alpha launch (v2): 0/0 — not yet started.

Carry-over

  • #172 — Pass lesson context through to simulation practice (in-progress, sole remaining item for Simulation practice milestone)
  • 7 issues ready-for-dev: #199, #200, #201, #203, #204, #205, #206
  • 2 issues ready-for-prep: #202, #207

Risks

None identified.

Flags and watch-outs

  • The grind queue has 7 ready-for-dev issues that could be batch-executed. The orchestrator hasn’t dispatched exec or grind commands — this may be expected (waiting for a schedule window) or may indicate the orchestrate loop needs a nudge to move past triage-only polling.
  • #172 has been in-progress for multiple days without visible progress. It requires a Supabase migration and type regeneration — may need interactive attention.

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.

Designed to learn, built to ignore

The most dangerous organizational failures don't throw errors. They look fine, return results, and quietly stay frozen at the moment of their creation.

The variable that was never wired in

The gap between having a solution and using a solution is one of the most persistent failure modes in organizations. You see the escaped variable. You see the risk register. You assume the work is done.

Your empty queue isn't a problem

Dropping a column from a production database is the organizational equivalent of admitting you were wrong. Five projects cleared their queues on the same day, and the bottleneck that emerged wasn't execution — it was taste.