Example Master Plan — Capacity Exchange DAO (CED)

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

Workbook: CED DAO Workbook  ·  Self-check: [DEP 3 · DAO Proposal Qualification Checklist Template]  ·  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 revenue path (session revenue). The DAO's job is to grow and sustain it.

 

The collaboration a DAO does (feasibility)

For Cohort 3, CED runs the Community Self-Governance Skills Program — a named program funded by a Theme Sponsor ("Tập huấn trang bị kỹ năng cho cộng đồng tự quản"): a themed series of ~200 one-to-one sessions equipping community leads with the skills to run self-governing communities. It's a realistic, divisible scope for ~15 people, with a natural onboarding lane and a real funding path.

Four concrete pillars:

1 · Secure the funding — Call for Theme Sponsors. The DAO runs CED's Call for Theme Sponsors to fund the program, using the [DAO Partner Outreach Playbook]. The goal is a Theme Sponsor who funds the whole program (~$3,000 into the CED Learning Fund); Kambria's $3,000 seed is held in reserve for any shortfall.

2 · Build the curriculum & ready the Guides. With Kambria, the DAO builds a hybrid curriculum — a core track every lead completes, plus elective topics by relevance — and refers/recruits Guides. Kambria qualifies both Guides (for quality) and Explorers (right audience).

3 · Recruit the leads & run the sessions. The DAO recruits the community leads (Explorers), matches them to Guides, plans each lead's core+elective series, and runs the ~200 sessions with QA and completion tracking. Explorers join the sponsored sessions for free; Guides are paid $6 per completed session from the CED Learning Fund.

4 · Regeneration through revenue sharing (Order Handler). Outside the sponsored program, CED's regular paid sessions generate real revenue. By holding the Order Handler role, the DAO earns a share of that revenue — recorded in full and split through the framework's standard DEP 3 split. (The sponsored program itself is funded by the Partner, so its sessions are free to Explorers.)

The boundary: Guides keep guiding and Explorers keep exploring — the DAO secures the sponsor, builds the curriculum, recruits and runs, and handles orders; it doesn't replace the exchange itself.

 

1 · DAO Overview

• DAO name: Capacity Exchange DAO (CED)
• Type: Operator DAO — members run the operations (the partner call, curriculum, recruitment, delivery, order handling); the value, the 1-1 sessions, is created by 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 — in Cohort 3, by equipping community leads to run self-governing communities.
• DAO Lead: Farai Moyo (KAM-0038) · DAO Facilitators: [names]
• Project team in the DAO: N/A — CED is Kambria's model DAO, so the quorum cap doesn't apply.

→ Workbook: DAO Master tab.

 

2 · Objective & OKRs

The DAO Objective (three axes) — for the Community Self-Governance Skills Program:

• Reach — community leads reached and sessions run. For this program: secure a Theme Sponsor to fund this program (~$3,000) and a committed or pipelined Partner for the next cycle ($3,000+ each); ≥2 qualified Guides per topic; ~30 community leads; ~200 sessions run.
• Depth — leads who complete the core track and gain the skills. For this program: ≥80% of leads complete the core track; a positive before/after self-assessment; healthy session feedback.
• Self-propagation — leads who carry it onward. For this program: ≥10 leads run their own community's coordination cycle during the program; ≥5 Explorer→Guide transitions; and ≥25% of leads take an organic next step (a paid session, becoming a Guide, or running their own cycle) within ~3 months of completing the core track — including ≥5 leads who pay it forward by volunteering as Guides for ≥20 sessions — early signal by the showcase, the rest tracked after.

How success is measured. Platform records (sessions, completion, feedback, transitions) and community field notes.

Regeneration is measured too: the revenue the DAO shares in as Order Handler on CED's regular paid sessions is recorded in full and split through the standard DEP 3 split. Revenue is a signal, not the target; the program itself is Partner-funded.

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

 

3 · Scopes, Lanes & Members

Scopes (4): Partnerships (fund the program) · Curriculum & Guides (build and ready) · Registration & Leads (recruit and match) · Delivery (run and handle orders).

Scope	Lane	Owners (pair)	What it owns (boundary)	Decides without asking
Partnerships	Call for Theme Sponsors	Amara Okoro (KAM-0007), Bao Tran (KAM-0012)	Securing & managing the Theme Sponsor(s) that fund the program	Outreach channel, targets, pitch within the Playbook
Curriculum & Guides	Curriculum & Guides	Chidi Eze (KAM-0019), Gita Nair (KAM-0041)	Base curriculum (core+elective) with Kambria; referring/readying Guides	Curriculum structure; Guide sourcing (Kambria qualifies)
Registration & Leads	Registration & Leads	Esi Mensah (KAM-0031), Farai Moyo (KAM-0038)	Recruiting community leads; matching leads↔Guides; planning each series; welcoming	Recruitment approach; matching; series plans
Delivery	Sessions & Delivery	Divya Rao (KAM-0024), Hoang Le (KAM-0044)	Running ~200 sessions with QA & completion tracking; Order Handler for regular paid sessions	Scheduling & QA within policy; order handling

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

Roles. DAO Lead: Farai Moyo (KAM-0038). DAO Facilitators: [names]. KDF roles: Order Handler — Hoang Le (KAM-0044), through which the DAO earns its shared revenue on regular sessions; Operator — Farai Moyo (KAM-0038); Organizer — Farai Moyo (KAM-0038).

Membership & removal rules. Within the Termination Policy (Consent §5): inactivity = 2 missed check-ins without notice, or 14 days silent; misconduct evidence = linked in the Inactivity & Misconduct tab; exceptions = health / exams / work / family, if flagged in advance; escalation = private check-in → 1-week window before a vote.

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

 

4 · Workplan

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

• Call for Theme Sponsors — run partner outreach from the Playbook until the program is funded; onboard the Partner to the CED Learning Fund.
• Curriculum & Guides — build the core + elective curriculum with Kambria; refer and ready Guides for the tracks.
• Registration & Leads — recruit community leads, match them to Guides, and plan each lead's core+elective series.
• Sessions & Delivery — run the ~200 sessions with a QA checklist and completion tracking; operate the Order Handler role for regular paid sessions.

Cross-lane activity — the launch. Funding (Partnerships), curriculum + Guides ready (Curriculum & Guides), and leads recruited (Registration & Leads) must line up before delivery starts — run as a named activity, each lane owning its part.

→ Workbook: Workplan tab.

→ Resource — partner outreach. For the Theme Sponsor outreach, 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

Operator work, paid per completed, reviewed-qualified task, settled monthly through the framework's Microjob pool. Guides are paid separately — $6 per completed session, from the CED Learning Fund (see Section 6).

task_id	Lane	Task	Rate	Basis	# planned
CSG-CU-01	Curriculum & Guides	Build one curriculum module (core/elective)	100	per module	5
CSG-PA-01	Call for Theme Sponsors	Run one Theme Sponsor outreach batch	90	per batch	3
CSG-RE-01	Registration & Leads	Recruit one community-lead batch	70	per batch	3
CSG-GU-01	Curriculum & Guides	Refer & ready one Guide	40	per Guide	4
CSG-OP-01	Sessions & Delivery	Coordinate ~50 sessions with QA	100	per batch	4
CSG-RP-01	Registration & Leads	Impact report (mid / end)	80	per report	2

Two separate flows: operator pay-per-task (above) pays DAO members for running the program; Guide session pay ($6/session) comes from the CED Learning Fund; and the Order Handler revenue share (regular sessions) is earned income returned to the DAO — not pay.

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

 

6 · Budget Plan

The program's cost is ~$3,000, funded by the Theme Sponsor (the goal); Kambria's $3,000 seed is held in reserve to cover any shortfall.

• Guide session delivery: 1,200 USDT — 200 sessions × $6, paid from the CED Learning Fund.
• DAO operator payouts: 1,700 USDT — the Pay-Per-Task Scheme above (Curriculum & Guides 660 · Call for Theme Sponsors 270 · Registration & Leads 370 · Sessions & Delivery 400), through the framework.
• Contingency: 100 USDT.
• Program total: 3,000 USDT — funded by the Partner; the Kambria seed backstops any gap. Phased Feb–May.

Separate from this: the Order Handler revenue share on CED's regular paid sessions is earned income, recorded in the Cashbook and split by the standard DEP 3 split.

→ Workbook: Budget Plan + Cashbook tabs. 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/community leads (attendance, feedback, completing the core track), DAO members (partner outreach, curriculum, recruitment, coordination, delivery, reporting), community collaborators and ambassadors (referrals, reusable content).
• Karma & tiers: Low / Normal / High / Trusted; tiers Seeker → Contributor → Builder → Steward, with non-disruptive privileges.

KAT recognises contribution of every kind — including volunteer/in-kind Guides, who receive no payment. Recognition is not a substitute for pay.

→ 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 launch activity aligns lanes when they push together. Full cadence: Operating Rhythm.

 

9 · Timeline

• Onboarding (Mid Feb - Mid Apr 2027): set up Workbook + framework, form pairs, write this plan + lane proposals, take up the Playbook, Kickoff. Partner outreach starts now (funding gates delivery).
• Execution (Mid Apr - Mid Aug 2027): monthly cycle — weekly check-ins; monthly qualify → contributor settlement → Cashbook + reconcile → KAT settlement → Sync. Curriculum + Guides ready and leads recruited early; the ~200 sessions run across the window.
• Summary & Showcase (Mid Aug - Sep 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).

 

11 · Dependencies & Risks

• Dependencies: delivery depends on the program being funded (Partnerships lane) and on curriculum + Guides being ready; matching depends on both leads and Guides being recruited and qualified by Kambria; all lanes depend on the framework and the Playbook (Kambria provides both).
• Risks & mitigations: no Partner secured in time → the Kambria seed can cover a smaller first program while outreach continues; a pair member goes quiet → the pair keeps the lane alive; low core-completion → the Registration & Leads lane owns series planning and follow-up; leads cherry-pick electives and skip core → the core track is required for "completed", tracked from the start.

 

12 · Documentation & Reporting

Field notes alongside the numbers; weekly lane updates; monthly contributor + KAT settlement; a mid-program and end-of-program impact report for the Partner; 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 ✓ · operator pay-per-task rates set, program budget Partner-funded with seed reserve ✓ · Guide pay via CED Learning Fund ✓ · Order Handler regeneration path (regular sessions) 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 — Call for Theme Sponsors

Worked example of a lane proposal, from the companion template. Replaces the earlier "Outreach & Campaign" example, to match CED's Cohort 3 master plan.

• Lane: Call for Theme Sponsors · Scope: Partnerships · Owners (pair): Amara Okoro (KAM-0007), Bao Tran (KAM-0012)
• What this lane owns (boundary): securing and managing the Theme Sponsor(s) that fund the Community Self-Governance Skills Program, following the DAO Partner Outreach Playbook. Ours end to end — from target list to a committed sponsor.
• Decisions we make without asking: which prospects to approach, the outreach channel and message, and our weekly targets — within the Playbook and the partner-communication rules.

Our Key Results:

• Reach (enabling) — secure 1 Theme Sponsor that funds the program (~$3,000 into the CED Learning Fund), so the ~200 sessions can run; a pipeline of ≥8 qualified prospects contacted.
• Quality of fit — the Partner is aligned with the self-governance theme, with a scope agreed in writing before delivery starts.

Our workplan (each with a Definition of Done):

• Build the target list and run outreach batches per the Playbook — done when a batch of prospects is contacted and logged in the partner CRM.
• Qualify prospects and run discovery calls — done when a prospect completes a discovery call and is scored against the rubric.
• Onboard the Partner — done when the scope is agreed in writing and the funds (or in-kind Guides) are committed to the CED Learning Fund.

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

• CSG-PA-01 — run one Theme Sponsor outreach batch, 90 USDT per batch (3 planned).

How we talk about Kambria (important): all outreach goes out in CED's name; CED is responsible for what it commits to. Kambria is referenced only as the organizer of the DEP program CED is part of — never as a party to, guarantor of, or endorser of the partnership. (See Partner With Us.)

What we need:

• The DAO Partner Outreach Playbook + outreach tools (lead lists exported by our DAO Facilitators in the early phase).
• CED's partner pages and the DEP 3 DAO Partnership Interest form for inbound interest.
• A hand-off rhythm with Curriculum & Guides and Registration & Leads, so a secured Partner flows straight into curriculum finalisation and delivery.

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