DEP – Cohort 3
Operating Rhythm — What Happens When
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 DAO gathers for the monthly Circles DAO Sync.
The cohort runs in three phases from the DAO's point of view: set up (Onboarding, February 2027), run the monthly cycle (Execution, from March 2027), and close out (Summary & Showcase).
The Circles DAO's timeline: Launch January 2027 · Onboarding February · Run & measure March–April · mid-season check end of April · Local event & Practice Circles Season 1 May–June · OKR review end of June · Summary & Showcase September 2027· DEP 3 continues to October 2027.
1 · Onboarding — 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 Circles DAO 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 — 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. Every XDAO voting — this one, each operating-cost release, and any GT changes — is logged in the Voting Tracking tab, so the DAO keeps one auditable list of its decisions.
Then the DAO settles into the weekly and monthly rhythm.
Every week
| Do this | In this tool |
|---|---|
| Hold the weekly 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.
When a member goes persistently quiet — or a serious issue arises — it's recorded and worked through in the Inactivity & Misconduct tab, following the termination process on the Consent page: a flag, a private check-in, a one-week window to re-engage, and only then a DAO vote.
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 (recorded in Voting Tracking).
- Log and reconcile. Payouts and costs are logged in the Cashbook, one line per movement, each with its evidence. Before the close, every month-end check in the Cashbook must read OK — including contributor payouts against verified Contributions, and custody against the actual treasury and wallet balances — and spending is read against the Budget Plan to see where a lane is under or over. If any check 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 Circles DAO Sync (monthly). Each pair speaks to its Key Results: what moved, what didn't, what's next. Progress is tracked against the DAO's goals and OKRs 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.
Mid-season check (end of April 2027): the DAO compares the houses it supports with self-run houses (verified tasks per week, % of contributors returning, cost per task) and chooses the selected project that will host a Local event — one with a local lead, enough people nearby, and costs paid by a local sponsor or the project. May–June 2027: the Local event and Practice Circles Season 1. End of June 2027: OKR review.
Adjusting the plan
The Master Plan and Workplan are a starting point, not a fixed contract — execution will differ from the plan, and that's expected. The rule for changes is simple:
If a change touches something the DAO voted on, it goes back to a vote. Otherwise, the lane just makes the change and keeps the Workbook current.
- No vote needed (a pair/lane just does it): reordering or re-timing tasks, refining a Definition of Done, swapping small tasks within a lane, adding a small unpaid task. Update the Workplan so it stays accurate.
- Needs a proposal + vote (these were approved by the DAO): changing the Pay-Per-Task Scheme (rates, or adding/removing a paid task), reallocating the Budget Plan, changing the Objective / OKRs, adding, removing, or merging a lane, or membership changes. Log the vote in Voting Tracking.
- Inform, don't vote (in between): if a lane materially changes its own Key Results or scope, tell the DAO Lead and DAO Facilitators; escalate to a vote only if it affects the DAO's Master Plan commitments.
The point: lanes have room to adapt day to day, while the few things the whole DAO committed to stay under the DAO's collective decision.
3 · Summary & Showcase — close out
The cohort's last month (September 2027) 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 Circles DAO 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 · Circles DAO 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 |
| DAO Facilitator | run the check-in | run the Circles DAO Sync; support settlement |