Operating Rhythm — What Happens When

Estimated reading: 6 minutes 7 views

The other pages in this section explain what each tool is — the Kambria DAOs Framework and the DAO Workbook, tab by tab. This page explains when you use them: the order things happen in, across the cohort. Read it as the map that turns the tools into a routine.

Two rhythms run the whole thing:

A weekly rhythm — the short check-in that keeps every lane visible.
A monthly rhythm — the close-of-month, where money and recognition settle and the cohort gathers for the All-DAOs Sync.

The cohort runs in three phases from a DAO's point of view: set up (Onboarding), run the monthly cycle (Execution), and close out (Summary & Showcase).

1 · Onboarding (Jan 2027) — set the instruments up

Before any work is tracked, the DAO gets its Workbook and its on-chain framework ready. Most of this happens once.

Do this	In this tool	Result
Confirm members from the Hub	Workbook — Roster	every member has a person_id
Define scopes, lanes and pairs; assign the DAO Lead	Workbook — Owned Lanes & Roles	the DAO's ownership map
Write the master plan (scopes, lanes, objective)	Master Plan doc → linked in DAO Master	the first act of ownership
Set the DAO Objective (three axes) and each lane's Key Results	Workbook — OKR	what success means, before work starts
Draft lane proposals and the task list with Definitions of Done	Workbook — Workplan	tasks anyone can pick up
Set the tasks and their rates	Workbook — Pay-Per-Task Scheme	the approved menu of paid tasks
Plan the budget — contributor payouts + operating costs vs the $3,000 seed	Workbook — Budget Plan	the seed allocated, within budget
Configure recognition — parameters, credit rules, tiers	Workbook — KAT Config / Credit Rules / Karma & Tiers	KAT ready to run (configure, don't redesign)
Set up the framework — vault, splitter, executor, split config, roles	Kambria DAOs Framework (with Kambria)	the DAO can receive and split money
Fill the event catalogue for the cohort	Workbook — Config	the Attendance Grid knows the calendar

The phase ends at the Kickoff — the first All-DAOs Sync — with proposals ready to go to a vote.

Kambria runs this first live cohort hands-on. The framework setup, and the first runs of settlement, happen with close support and manual checks alongside the automation.

2 · Execution (Feb – May 2027) — run the monthly cycle

This is the heart of the cohort, and it repeats every month. It starts once, with the vote:

Once, at the start of Execution: proposals are submitted through XDAO and voted on; the qualified ones move into execution.

Then the DAO settles into the weekly and monthly rhythm.

Every week

Do this	In this tool
Hold the per-DAO check-in; tick who showed up	Workbook — Attendance Grid
Each lane submits its weekly update (summary, blockers, needs)	Workbook — Lane Weekly (Google Form)
Log deliverables as they land, with their review checks	Workbook — Contributions
Create Payment Requests as revenue comes in; mark orders completed	Kambria DAOs Framework (Order Handler)

The weekly check-in is where a stalling lane gets caught early — a rising gap in someone's activity plus a named blocker in Lane Weekly is exactly the signal it exists to surface.

Every month (the close)

At the end of each month, the DAO closes the cycle in this order:

Qualify and confirm the month's work. Completed deliverables are reviewed in Contributions — lane owner, then DAO Lead, then Facilitator. When all three confirm, the deliverable is Verified, a short confirmation is sent to the whole DAO (naming the deliverable, contributor(s), and amount), and the confirmation date is logged. Only verified deliverables are paid — and a verified, confirmed deliverable is owed even if the contributor has since left the DAO.
Settle contributor payments. The Operator builds the allocation from the qualified tasks, at the rates in the Pay-Per-Task Scheme; the framework computes and pays out (per task, settled this cycle). Operating costs go the other path — a DAO vote releasing funds to the DAO Lead or treasurer.
Log and reconcile. Payouts and costs are logged in the Cashbook, its reconciliation is checked against accepted Contributions, and both are tracked against the Budget Plan to see where a lane is under or over. If reconciliation reads CHECK, fix it before anything else.
Settle recognition (KAT). Verify the month's Credits Log, set levels in the Karma Register, run KAT Settlement, and pass the KAT Audit. Credits → Karma → KAT, once a month.
Release the next seed tranche. The month's operating funds are released.
Gather — the All-DAOs Sync. Each pair speaks to its Key Results: what moved, what didn't, what's next. Progress is tracked against the three axes in OKR; field notes capture what the numbers don't.

The framework grows across this phase: revenue-flow automation is in place from the start, with more of the settlement automated as it proves itself. Until then, Kambria runs the monthly settlement hands-on.

3 · Summary & Showcase (Jun 2027) — close out

The cohort's last month adds a closing layer on top of the normal monthly close.

Do this	In this tool	Result
Run the final monthly settlement (contributors + KAT)	Cashbook · KAT Settlement	the books and recognition are closed
Score the DAO's report	Workbook — Proposal QA	performance tier + decision
Write the DAO summary — what it did, impact vs the three axes, learnings	Master Plan / summary doc	the DAO's story of the cohort
Present at the Showcase (the final All-DAOs Sync)	—	Cohort 3 complete

Cadence at a glance

When	What settles / happens
Once, at Onboarding	Roster, lanes & roles, master plan, OKRs, workplan, pay-per-task scheme, budget plan, KAT config, framework setup
Once, start of Execution	Proposals submitted and voted (XDAO)
Every week	Check-in + Attendance · Lane Weekly · Contributions · Payment Requests
Every month	Qualify work · contributor settlement · Cashbook + reconcile · KAT settlement · seed tranche · All-DAOs Sync
Last month	Final settlement · Proposal QA · DAO summary · Showcase

Who drives each rhythm

Role	Weekly	Monthly
Lane owners (pairs)	deliver, log contributions, submit Lane Weekly	speak to their Key Results at the Sync
Order Handler	create Payment Requests, mark orders completed	—
Operator	—	run the distribution & Microjob settlement
Organizer	—	keep config current; adjust caps/rules if needed
DAO Lead	connect the lanes, flag a quiet one	hold the whole picture at the Sync
Bookkeeper / treasurer	—	log the Cashbook, reconcile
DAO Organizer (KAT)	verify credits as they land	run the monthly KAT settlement + audit
Kambria Facilitator	run the check-in	run the All-DAOs Sync; support settlement