Delivery Desk: transcript

This is Delivery Desk: a team of AI sessions that ships software, while the founder makes the calls.

Work comes in as requests. Sessions build them, test them, merge them and release them, and it all shows on one dashboard.

When something needs a person, like a database change, it waits for one tap: approve or veto.

Under the dashboard sits a desk with eight roles, an owner for every epic, and a tick every fifteen minutes.

Every pull request moves through one append-only ledger, from requested to live and notified: over five thousand events in six days.

Before anything merges, eighteen chained checks run, and a merge is refused unless a passed trial covers that exact commit.

Migrations, production writes and secrets need the operator's own yes, bound to the exact change. A yes relayed by another session doesn't count.

Every change gets a risk class, and unknown is never treated as low. A sheriff may approve low-risk migrations, and its yes counts after thirty minutes unless the operator vetoes it.

At night the desk keeps shipping everything that needs no yes, and saves its questions for one morning ask.

And it improves itself. The reporter prices every day's delivery and sends the builder its costliest patterns. A monitor reads each new Claude Code release for ideas.

The planner logs every idea into a backlog, and the builder, the only role allowed to change the desk's own tooling, plans each one and ships it as a tested pull request.

Then the reporter compares the cost per merged pull request before and after, and marks whether each change improved it, shifted it, or did nothing. And the loop starts again.

Delivery Desk. Ship all day, decide only what matters.