A worked example of the whole participant-proposed flow — the project, the collaboration a DAO can do to scale it, and the master plan and lane proposal that follow from it.

Workbook: Heritage Kitchen DAO Workbook  ·  Self‑check: [DEP 3 · DAO Proposal Qualification Checklist]  ·  DAO Facilitator: [name]  ·  Date: Jan 2027

 

Part 0 · The Project & the Collaboration

Before the master plan, two things: does the project meet the criteria, and what can a DAO realistically do to scale it? Everything after flows from here.

 

The project (illustrative)

Heritage Kitchen is a regional food‑heritage project run by a small coordinating team working with a community of home cooks and small food producers. It documents traditional recipes, preservation methods (ferments, sauces, cures) and the stories behind them, and shares them with a global audience through live online heritage‑cooking classes and a digital "recipe + technique + story" collection.

How it meets the criteria:

• An innovation solution in hand. A proven format — live online heritage‑cooking classes plus a structured digital collection — already runs, and has for about a year, with real learners attending and real recipes documented. It is in use, not a concept.
• Regeneration proven. It sustains itself through paid class seats, sales of the digital collection, and a modest cultural‑organisation sponsorship — with records: class rosters and receipts, collection sales, the sponsorship agreement. Modest but real; enough to keep the documentation going and pay small honoraria to featured cooks.
• A local community. A community of ~25 home cooks and heritage‑keepers, plus a wider community of learners who return and cook the dishes.
• Practical conditions. The coordinator and members have reliable internet; cryptocurrency is not banned where they are.

 

The collaboration a DAO can do (feasibility)

The cooks keep cooking and sharing their knowledge — they don't become marketers, event managers, or fundraisers. That's the boundary. A DAO of ~15 remote members becomes a channel that amplifies the project and scales its reach through community:

• source and document more heritage‑keepers' recipes and stories (with their consent),
• turn that raw material into class‑ready content and grow the digital collection,
• run and grow the online classes and story events, and keep learners coming back,
• build partnerships (culinary schools, cultural and tourism organisations, sponsors),
• welcome and activate both learners and new DAO members.

Value flows through the framework; the recipe/story collection's authorship is anchored on‑chain with the source community credited as originators (the DAO amplifies, it does not own the heritage). This is a realistic scope for a cohort: divisible into a few owned lanes, with a natural onboarding lane, run by ~15 people, with real revenue paths — so it's tested with real money, not in theory.

From this collaboration — not from the project in the abstract — the OKRs, lanes and workplan below follow.

 

1 · DAO Overview

• DAO name: Heritage Kitchen DAO
• Type: Operator DAO — the DAO's members amplify; the value at the heart of it (the recipes, techniques and stories) is created by the community of cooks and heritage‑keepers.
• The project it scales: Heritage Kitchen — traditional food heritage, documented and taught online. A working solution with a real community and proven regeneration (see Part 0).
• Mission (one line): carry this community's food heritage further into people's lives — teaching more people to cook it, and helping the community keep sharing it onward.
• DAO Lead: [participant name] (KAM‑xxxx)  ·  Kambria Facilitator: [name]
• Project team in the DAO: two of Heritage Kitchen's coordinating team join the ~15‑member DAO — together well under the 34% quorum cap, so the DAO is community‑governed, not run by the founders.

→ Workbook: DAO Master tab.

 

2 · Objective & OKRs

The DAO Objective (three axes):

• Reach — learners and communities the heritage reaches, and classes/events run. This cohort: 400 learners reached; 24 classes/events run.
• Depth — learners who actually cook it and come back, not one‑and‑done. This cohort: 40% return for a second class; 30 documented "I cooked it" cases.
• Self‑propagation — learners who host or teach others, and community members who step forward as featured guides. This cohort: 30 learners who share/teach; 6 new heritage‑keepers featured.

How success is measured. Class rosters, returns, referrals, collection sales, and — crucially — field notes: a learner who taught their neighbour, a cook whose recipe travelled further than expected. Revenue is recorded in full but is a signal the heritage is valued, not the target. (Regeneration is already proven; the cohort scales it.)

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

 

3 · Scopes, Lanes & Members

Scopes (3): Community & Content · Audience · Growth & Revenue.

Scope	Lane	Owners (pair)	What it owns (boundary)	Decides without asking
Community & Content	Sourcing & Community	[pair]	Relationships with cooks/heritage‑keepers; inviting, consent, gathering knowledge	Who to approach; how to document; consent terms within policy
Community & Content	Production & Storytelling	[pair]	Turning raw material into class‑ready content + the digital collection	Format, style, what goes in the collection
Audience	Audience & Onboarding	[pair]	Bringing learners in, running the class calendar, keeping them returning; welcoming new members	Channels, class schedule, welcome cadence
Growth & Revenue	Partnerships & Revenue	[pair]	Culinary‑school / cultural / sponsor partnerships; selling the collection	Which partners to approach; draft terms

Audience & Onboarding is this DAO's onboarding lane — it activates learners and welcomes new members. Floating contributors help across lanes (e.g. translation, subtitling) without owning one.

Roles. DAO Lead: [name] — connects the lanes. Facilitator: [name] — from outside. KDF roles: Order Handler [name]; Operator [name]; Organizer [name].

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

 

4 · Workplan

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

• Sourcing & Community — document heritage‑keeper profiles (recipe + technique + story) with consent; keep the relationships warm.
• Production & Storytelling — produce class‑ready content packs from each profile; assemble the digital collection v1.
• Audience & Onboarding — run the class calendar; grow the learner base; drive returns; welcome new members.
• Partnerships & Revenue — approach and sign culinary‑school / cultural / sponsor partners; sell the collection.

Cross‑lane activity — the Season 1 Launch. A launch push needs Sourcing (profiles ready), Production (content ready), Audience (fill the classes) and Partnerships (co‑promotion) together — run as a named activity, each lane owning its part.

→ Workbook: Workplan tab.

→ Resource — partner outreach. The Partnerships & Revenue lane applies the DAO Partner Outreach Playbook in the DAO's shared Drive — the runway for finding culinary‑school, cultural, and sponsor partners.

 

5 · Pay‑Per‑Task Scheme

Paid per completed, reviewed‑qualified task, settled monthly through the framework. The menu:

task_id	Lane	Task	Rate	Basis	# planned
HK‑SC‑01	Sourcing & Community	Document a heritage‑keeper profile (recipe + story, with consent)	60	per profile	8
HK‑PR‑01	Production & Storytelling	Produce one class‑ready content pack	90	per pack	8
HK‑AU‑01	Audience & Onboarding	Run one online class end‑to‑end (promote, host, follow‑up)	70	per class	6
HK‑PT‑01	Partnerships & Revenue	Sign a partner / sponsor	80	per partner	3

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

 

6 · Budget Plan

The $3,000 seed — the DAO's capital for this collaboration, released monthly:

• Contributor payouts: 1,860 USDT (Sourcing 480 · Production 720 · Audience 420 · Partnerships 240) — through the framework.
• Operating costs: 780 USDT — video/editing + hosting tools (150), translation/subtitling (90), honoraria (micro‑grants) to featured heritage‑keepers (300), on‑chain fees (40), contingency (200) — released by DAO vote, against receipts.
• Against the seed: total planned 2,640 of 3,000, buffer 360. Within seed. Phased Feb–May.

The honoraria show the model clearly: the seed is the DAO's to spend on the collaboration — including small, consented payments to the community collaborators whose heritage it amplifies — not a grant handed to the project.

Budgeting principles: impact‑first; receipts for every cost; transparent; the seed is starting capital for scaling impact, not a sum to be earned back.

→ Workbook: Budget Plan tab. Revenue the DAO earns is split by the DEP 3 standard split (separate from the seed) — see Categorisation & Revenue Split.

 

7 · KAT Reward Framework

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

• What this DAO recognises: heritage‑keepers and cooks (sharing a recipe/technique — community collaborators), learners (feedback, qualified referrals, "cooked it" evidence), DAO members (documentation, content, coordination), ambassadors (referral campaigns).
• Karma & tiers: Low / Normal / High / Trusted; tiers Seeker → Contributor → Builder → Steward, with non‑disruptive privileges (early access to new classes, invitations to community sessions).

→ 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 Season 1 Launch activity plan aligns lanes. Full cadence: Operating Rhythm.

 

9 · Timeline

• Onboarding (Jan 2027): set up Workbook + framework, form pairs, write this plan + lane proposals, Kickoff.
• Execution (Feb–May 2027): monthly cycle — weekly check‑ins; monthly qualify → contributor settlement → Cashbook + reconcile → KAT settlement → seed tranche → Sync. Season 1 Launch in Feb–Mar.
• Summary & Showcase (Jun 2027): final settlement, Proposal QA, DAO summary, Showcase.

→ Workbook: Timeline tab.

 

10 · Governance

Proposals through XDAO; operational decisions by 48‑hour poll; plan/budget changes require a quorum. Project‑team quorum cap: the two Heritage Kitchen founders in the DAO stay well under 34%, so no decision rests with the founding team alone. Revisions proposed in Discord, then a poll.

 

11 · Dependencies & Risks

• Dependencies: Production depends on Sourcing (profiles first); Audience depends on Production (content to teach); all depend on the community's willingness to share and the framework running (first live cohort — Kambria hands‑on).
• Risks & mitigations: community consent / IP sensitivity → clear consent at sourcing, on‑chain credit to originators, nothing published without sign‑off; a cook withdraws → multiple profiles in the pipeline; low class turnout → Audience lane owns activation, and returns are tracked early; contributor crypto access → confirmed at onboarding.

 

12 · Documentation & Reporting

Field notes alongside the numbers; weekly lane updates; monthly settlement; an end‑of‑cohort 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,640 / 3,000) ✓ · KAT configured ✓ · IP/consent handled ✓ · 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 — Sourcing & Community (Community & Content)

The lane closest to the project's community — and the one that shows the participant‑proposed care (consent, IP, the boundary that protects the cooks).

• Lane: Sourcing & Community  ·  Scope: Community & Content  ·  Owners (pair): [person_id, person_id]
• What this lane owns (boundary): the relationships with the cooks and heritage‑keepers, and the respectful gathering of their recipes, techniques and stories — with consent. A continuing stream, ours end to end. We do not ask the cooks to become marketers or organisers — we come to them.
• Decisions we make without asking: who to approach next, how to document a profile, and the consent terms within the DAO's policy.

Our Key Results:

• Reach — 8 heritage‑keeper profiles documented (recipe + technique + story), consented and ready for Production.
• Self‑propagation — 6 heritage‑keepers who continue sharing beyond their first profile (a second recipe, a class appearance, referring another cook).

Our workplan (each with a Definition of Done):

• Approach and onboard a heritage‑keeper — done when consent is signed and the first session is booked.
• Document a profile — done when the recipe, technique notes and story are captured and the keeper has approved them.
• Hand off to Production — done when the raw pack + consent + on‑chain authorship credit are filed.

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

• HK‑SC‑01 — document a heritage‑keeper profile, 60 USDT per profile.

What we need:

• The consent + IP‑credit template (with the DAO Facilitator) so authorship is anchored to the originating community.
• Small honoraria for featured keepers (from the operating budget) so their time is respected.
• A steady hand‑off rhythm with Production, so profiles don't pile up unmade.

→ Workbook: our rows in Owned Lanes & Roles · OKR · Workplan · Pay‑Per‑Task Scheme. Runway: the Sourcing Launch Kit. Self‑check: the Lane Proposal Checklist tab. IP: the IP Framework / NFT IP Anchoring page.