Worked example. Fills the DAO Master Plan Proposal template with real CED content. Pairs with the CED example data in the DAO Workbook.

Workbook: CED DAO Workbook  ·  Self-check: [DEP 3 · DAO Proposal Qualification Checklist]  ·  DAO Facilitator: [name]  ·  Date: Jan 2027

 

Part 0 · The Project & the Collaboration

CED is Kambria's model DAO, so the "project" is the platform itself and Part 0 stays short — but the collaboration is concrete.

 

The platform

Capacity Exchange (CED) is a platform where people exchange skills, knowledge and experience through live 1-1 sessions. It already runs, with real Guides, Explorers and sessions, and a proven regeneration path (session revenue). CED serves a community of Guides and Explorers; the DAO's job is to grow and sustain it.

 

The collaboration a DAO does (feasibility)

For this cohort, CED DAO takes on three concrete pillars — a realistic, divisible scope for ~15 people, with a natural onboarding lane and a real revenue path:

1 · Run the CED Call, end-to-end. The DAO runs the CED Call — the pioneer‑recruitment drive that brings new Guides and Explorers to the platform — using the materials Kambria has already made and the guidelines it provides. The Call that Kambria ran is packaged into a DAO Partner Outreach Playbook, so the DAO replicates a proven campaign rather than inventing one: outreach, content, ads, referral tracking, and the hand‑off to activation.

2 · Peer support & community building. The DAO builds and holds the CED community — peer support between members, community sessions and rituals, and the retention that keeps Guides and Explorers coming back. This is the human layer the platform can't run on its own.

3 · Regeneration through revenue sharing (Order Handler). CED's regeneration is real and shared: by taking the Order Handler role, the DAO earns a share of the revenue from the sessions it helps make happen. The DAO's work returns value to it — recorded in full and split through the framework's standard DEP 3 split.

The boundary: Guides keep guiding and Explorers keep exploring — the DAO runs the Call, holds the community, and handles orders; it doesn't replace the exchange itself. From these three pillars, the Objective, lanes and workplan below follow.

 

1 · DAO Overview

• DAO name: Capacity Exchange DAO (CED)
• Type: Operator DAO — members run the operations (the Call, the community, order handling); the value, the 1-1 sessions, is created by the platform's Guides and Explorers.
• The project / solution it scales: the CED platform (see Part 0).
• Mission (one line): grow and sustain the Capacity Exchange platform so more people can exchange capacity, more deeply, and carry it onward themselves.
• DAO Lead: Farai Moyo (KAM-0038)  ·  Kambria Facilitator: [name]
• Project team in the DAO: N/A — CED is Kambria's model DAO, not built around an external project team, so the quorum cap doesn't apply.

→ Workbook: DAO Master tab.

 

2 · Objective & OKRs

The DAO Objective (three axes):

• Reach — new Guides & Explorers brought in through the CED Call, and sessions run. This cohort: 100 registrants from the Call; 500 sessions run.
• Depth — registrants who activate and keep exchanging, held by the community. This cohort: 60% of registrants complete a first session; a healthy return rate.
• Self-propagation — users who refer others and members who support their peers. This cohort: 40 users who refer someone; 30 active peer-supporters / community members.

How success is measured. Platform analytics (registrations from the Call, sessions, returns, referrals) and community field notes. 

Regeneration is measured too: the revenue the DAO shares in as Order Handler is recorded in full — a signal the exchange is valued, split through the framework's standard DEP 3 split. Revenue is a signal, not the target. 

→ Workbook: OKR tab. Framework: Measuring What Matters.

 

3 · Scopes, Lanes & Members

Scopes (3): The CED Call (bring people in and activate them) · Community (hold and grow the community) · Regeneration (run sessions and earn the shared revenue).

Scope	Lane	Owners (pair)	What it owns (boundary)	Decides without asking
The CED Call	Outreach & Campaign	Amara Okoro (KAM-0007), Bao Tran (KAM-0012)	Running the CED Call end-to-end from the Playbook	Channel, message, weekly targets within the Playbook
The CED Call	Onboarding & Activation	Esi Mensah (KAM-0031), Farai Moyo (KAM-0038)	Turning registrants into active users; welcoming new members	Onboarding flow, welcome cadence
Community	Peer Support & Community	Chidi Eze (KAM-0019), Divya Rao (KAM-0024)	Peer support, community sessions, retention	Community rituals, peer-support format
Regeneration	Sessions & Order Handling	Gita Nair (KAM-0041), Hoang Le (KAM-0044)	Making sessions happen with QA; handling orders (Order Handler)	Scheduling & QA within policy; order handling

Onboarding & Activation is CED's onboarding lane. Floating contributors help across lanes without owning one.

Roles. DAO Lead: Farai Moyo (KAM-0038). Kambria Facilitator: [name]. KDF roles: Order Handler — Gita Nair (KAM-0041), the role through which the DAO earns its shared revenue; Operator — Farai Moyo (KAM-0038); Organizer — Farai Moyo (KAM-0038).

→ Workbook: Owned Lanes & Roles + Roster. Concept: Owned Lanes Model.

 

4 · Workplan

Each lane's tasks (full list in the Workplan tab):

• Outreach & Campaign — run the CED Call end-to-end following the CED Call Playbook, in referral-tracked batches.
• Onboarding & Activation — ship the welcome + first-session flow so a registrant books within 48h; welcome new members.
• Peer Support & Community — run peer-support and community cycles that keep members engaged.
• Sessions & Order Handling — coordinate sessions with a QA checklist and operate the Order Handler role.

Cross-lane activity — the CED Call. The Call needs Outreach & Campaign (bring people), Onboarding & Activation (activate them) and Peer Support & Community (hold them) at once — run as a named activity, each lane owning its part.

→ Workbook: Workplan tab.

→ Resource — partner outreach. For the sponsor and partner outreach behind the Order Handler revenue (and CED's community partners), the DAO applies the DAO Partner Outreach Playbook in its shared Drive — CED is the worked example in that Playbook.

 

5 · Pay-Per-Task Scheme

Paid per completed, reviewed-qualified task, settled monthly through the framework's Microjob pool. The menu:

task_id	Lane	Task	Rate	Basis	# planned
CED-CA-01	Outreach & Campaign	Run one CED Call campaign batch (per Playbook)	70	per batch	8
CED-AC-01	Onboarding & Activation	Welcome + first-session flow milestone	84	per milestone	3
CED-CO-01	Peer Support & Community	Run one peer-support / community cycle	84	per cycle	6
CED-OP-01	Sessions & Order Handling	Coordinate ~50 sessions with QA (Order Handler ops)	105	per batch	5

Pay-per-task (the seed) is separate from the Order Handler revenue share (regeneration) — the first pays contributors for tasks; the second returns earned revenue to the DAO through the framework.

→ Workbook: Pay-Per-Task Scheme tab (budgeted total: 1,841 USDT).

 

6 · Budget Plan

CED's $3,000 seed — capital for this collaboration, released monthly:

• Contributor payouts: 1,841 USDT (Outreach & Campaign 560 · Onboarding & Activation 252 · Peer Support & Community 504 · Sessions & Order Handling 525) — through the framework.
• Operating costs: 680 USDT — design + hosting (120), chat/API + on-chain fees (80), community event/meetup (120), community micro-grants (160), contingency (200) — released by DAO vote, against receipts.
• Against the seed: total planned 2,521 of 3,000, buffer 479. Within seed. Phased Feb–May.

The seed funds the work of scaling; the Order Handler revenue share (Section 2, 5) is separate earned income, recorded in the Cashbook and split by the standard DEP 3 split.

→ Workbook: Budget Plan tab. Revenue split: Categorisation & Revenue Split.

 

7 · KAT Reward Framework

Recognition on the KAT Framework 1.0 — configure, not redesign; monthly (Credits → Karma → KAT):

• What CED recognises: Guides (completed sessions), Explorers (attendance, feedback, qualified referrals), DAO members (running the Call, coordination, tooling, onboarding, peer support), community collaborators and ambassadors (referral campaigns, reusable content).
• Karma & tiers: Low / Normal / High / Trusted; tiers Seeker → Contributor → Builder → Steward, with non-disruptive privileges (early visibility to session slots, pilot access, session discounts).

→ Workbook: KAT Config · KAT Credit Rules · KAT Karma & Tiers. Member view: KAT in DEP 3.

 

8 · Rhythms & Coordination

Weekly per-DAO check-in (Lane Weekly); monthly All-DAOs Sync (each pair to its Key Results); the CED Call activity plan aligns lanes when they push together. Full cadence: Operating Rhythm.

 

9 · Timeline

• Onboarding (Jan 2027): set up Workbook + framework, form pairs, write this plan + lane proposals, take up the CED Call Playbook, Kickoff.
• Execution (Feb–May 2027): monthly cycle — weekly check-ins; monthly qualify → contributor settlement → Cashbook + reconcile → KAT settlement → seed tranche → Sync. The CED Call runs across Feb–Mar.
• Summary & Showcase (Jun 2027): final settlement, Proposal QA, CED summary, Showcase.

→ Workbook: Timeline tab.

 

10 · Governance

Proposals through XDAO; operational decisions by 48-hour Discord poll; plan/budget changes require a quorum. Project-team quorum cap: N/A (operator DAO). Revisions proposed in Discord, then a poll.

 

11 · Dependencies & Risks

• Dependencies: Onboarding & Activation depends on Outreach & Campaign for a steady flow of registrants; the Order Handler revenue share depends on sessions actually running; all lanes depend on the framework and the CED Call Playbook being ready (Kambria provides both).
• Risks & mitigations: members distributed across time zones → recorded check-ins + async updates; a pair member goes quiet → the pair keeps the lane alive; low activation → the Onboarding & Activation lane owns exactly this, returns tracked early; revenue lower than hoped → the seed already covers the work; regeneration is upside, not a dependency.

 

12 · Documentation & Reporting

Field notes alongside the numbers; weekly lane updates; monthly contributor + KAT settlement; an end-of-cohort CED summary scored on the Proposal QA tab.

→ Workbook: Lane Weekly · Contributions · Cashbook · KAT Settlement · Proposal QA.

 

13 · Readiness (self-check)

Objective on all three axes with targets ✓ · lanes and pairs incl. onboarding ✓ · workplan tasks have Definitions of Done ✓ · pay-per-task rates set, budget within seed (2,521 / 3,000) ✓ · Order Handler regeneration path set ✓ · KAT configured ✓ · practical conditions met ✓ · risks named, no overclaim ✓.

Self-checked against the DAO Proposal Qualification Checklist (READY); Kambria qualifies it in scored mode before the vote.

 

Example Lane Proposal — Outreach & Campaign (The CED Call)

Worked example of a lane proposal, from the companion template.

• Lane: Outreach & Campaign  ·  Scope: The CED Call  ·  Owners (pair): Amara Okoro (KAM-0007), Bao Tran (KAM-0012)
• What this lane owns (boundary): running the CED Call end-to-end — bringing new Guides & Explorers to the platform, following the CED Call Playbook. A continuing stream, ours end to end.
• Decisions we make without asking: which channels to use, the outreach message, and our weekly targets — within the Playbook and budget.

Our Key Results:

• Reach — 100 registrants from the CED Call this cohort.
• Self-propagation — 40 registrants who refer at least one other person.

Our workplan (each with a Definition of Done):

• Run the CED Call in batches per the Playbook — done when a batch of ~50 is registered, referral-tracked and active.
• Stand up referral tracking — done when a referral is attributable end to end.
• Hand off to Onboarding & Activation — done when registrants are passed over for first-session activation.

Our paid tasks (from the Pay-Per-Task Scheme):

• CED-CA-01 — run one CED Call campaign batch (per Playbook), 70 USDT per batch.

What we need:

• The CED Call Playbook + Kambria's Call materials (from the Facilitator).
• Hand-off rhythm with Onboarding & Activation so registrants are activated, not just registered.

→ Workbook: our rows in Owned Lanes & Roles · OKR · Workplan · Pay-Per-Task Scheme. Runway: the CED Call Playbook + the Outreach Launch Kit. Self-check: the Lane Proposal Checklist tab.