Operating rhythm — the recurring-operations view of the process corpusThe operating rhythm
A year of running a startup, honestly. Incorporation happens once — then the company is a set of loops: code ships daily, payroll runs and the books close monthly, the board meets quarterly, the franchise tax comes due every year, and a hire or a cancellation can fire off a process any afternoon. Same corpus as all 106 processes, sliced by how often each one really recurs — with its agent ceiling and the software that runs it.
29 processes live on the calendar · 22 fire on a trigger · 55 are one-time setup
Daily×4
The loop that never stops — code ships, issues move, email goes out.
Weekly×4
The week-shaped rituals: releases, content, outbound, goal check-ins.
Monthly×7
The money drumbeat: payroll runs, books close, invoices go out, runway gets read.
Quarterly×4
Governance season: board meetings, minutes, OKRs, review cycles.
Annual×10
The filing calendar: franchise tax, returns, 1099s, insurance, 409A.
When it happens×22
No calendar — a hire, a cancellation, a new vendor, a round sets these off.
Once×55
Setup and formation — done once, then the company runs on everything above.
Cadences are curated by hand from each process's real-world recurrence — and every process clicks through to its step-by-step DAG and simulator. Browse the full corpus →