The week's rhythm

Weekday mornings: the CEO leads

At nine in the morning, UTC, every weekday, the CEO reads every open task and pull request. If anything waits on you, a blocked task, a task in review, a pull request a person has to merge, a plan card to accept, a question card to answer, a task of your own with no movement, it writes you one message: two lines on where things stand, then the one thing to do next as an action you can take at once, naming the task or pull request. Never a finding alone, never a question back at you.

If nothing waits on you, it writes nothing. A quiet week costs nothing.

Friday: the review

On Friday the morning message is the week’s review instead, once: what was done and where it is, what was not and why, what carries over, and the next week proposed as a plan card you can accept.

Monday: the scorecard

Every Monday the team’s numbers land in your channel, and whenever you ask for them:

• Tasks closed this week, and by which role. A task counts when you approved it.
• Pull requests opened, merged, closed without merge, open now, and the share of what a person decided on that was merged. A pull request counts when a person merged it.
• Spend this month, by role, and the cost per closed task.
• Next: the one move, computed from what waits, in the order it matters: something blocked needs you first; then approvals; then pull requests to merge; then work filed and not handed out; then, when nothing waits, what is running; and when nothing at all is happening, give the team a task.

From your assistant, next_action is the same card.

Continuously: what keeps work moving

• Intake. What you send from Slack or the tracker is handed to the CEO within seconds of arriving, and a sweep every two minutes catches anything missed.
• Pace. Each agent works one task at a time; the rest queue. You can raise an agent’s ceiling on its page.
• The curator. A plan waits for a curator to read it; if none answers within the window, it passes on its own, marked unread. You are promised a plan, not a queue.
• Budgets. Spend is counted per run; at 80 percent of its budget an agent focuses on critical work, at 100 percent it pauses. The first of the month resets it.
• Recovery. A run that dies mid-task hands the task back on the next run; a task with no clear disposition, no owner and no movement is surfaced to you rather than left.