Cultural & Creative DAO

For the CCD Proposals locally, will the meetings have to be offline or virtual?

If some DAO members can meet offline locally, we encourage that. At the same time, because of the decentralized nature, DAO-wide meetings or meetings among members from different locations will need to be online.

Exchange DAO

As the program transitions from planning to implementation, what are the most important actions that Working Group Leads and members should prioritize, and are there any examples or resources from previous DEP cohorts that can help newer participants understand how to contribute effectively?

• As we transition into implementation, our key priorities are to regularly align on the Master Plan and Working Group Plans, follow the Exchange DAO timeline and assigned deliverables, communicate blockers early, and maintain active participation within your teams.
• From previous DEP cohorts, one of the biggest success factors was not having the most ambitious plan, but maintaining strong communication, accountability, and consistent contributions throughout implementation.
  >> We also encourage everyone to review the XDAO Quick Start Guide and the DEP Implementation Timeline & Next Steps resources. These materials provide practical guidance on proposal workflows, governance processes, upcoming milestones, and key actions expected from all participants.

KAT Tokenomics DAO

As a technical contributor in the KAT Tokenomics DAO, what tools and tech stack will we primarily be using - both for the MVP dashboard and for the testnet smart contracts?

The KAT Tokenomics DAO will likely use a mix of lightweight collaboration tools, no-code workflows, and experimental blockchain tooling depending on each Working Group’s needs.
For collaboration and coordination, we currently expect to use tools such as:
- Discord,
- Google Workspace,
- Figma,
- Spreadsheets,
- and GitHub for technical contributors where relevant.

For the MVP dashboard and workflow prototype, the approach will initially prioritize:
- simplicity,
- accessibility,
- and rapid experimentation, rather than building a production-ready system immediately.

For the testnet smart contracts, the technical stack may evolve during the cohort depending on contributor expertise and implementation scope. Since DEP 2 is experimental and learning-oriented, contributors will also have opportunities to help shape the technical direction collaboratively.

The main focus is not advanced infrastructure complexity, but rather:
- contribution tracking,
- symbolic recognition logic,
- governance experimentation,
- and workflow usability.

There are any preparatory materials or frameworks (especially related to tokenomics design, governance models, or evaluation criteria) that we should review before the kickoff session to maximize our contribution.

Yes. Participants are encouraged to review the core DEP 2 materials before the kickoff event to build shared context around:
DAO Introduction: https://kambria.io/docs/dep2/dao-projects-overview/kat-tokenomics-dao/

Member Roles and Contributions
- DAO Leaders and Working Group Leaders will coordinate and collaborate closely with other members to complete the templates below.
- The DAO Facilitator will also provide clear guidance and timely reminders throughout each stage of the process.
* Master Plan: Template | Example | Qualification Checklist
* Working Group Plan: Template | Example | Qualification Checklist
* Report: Template
* KAT for Contribution Recognition: Link

That said, DEP 2 is intentionally designed to be multidisciplinary and beginner-friendly. Participants are not expected to already be experts in tokenomics or blockchain systems. A major goal of the cohort is collaborative learning through experimentation and real participation.

Additional templates, onboarding guides, and DAO-specific frameworks will also be shared progressively during the program.

Which skills should participants focus on developing during DEP 2 to create the most impact?

DEP 2 is designed as an experimental learning ecosystem, so participants will likely develop both practical and collaborative skills throughout the program.

Some of the most valuable skills participants may strengthen include:
- decentralized coordination,
- systems thinking,
- governance participation,
- facilitation,
- community collaboration,
- regenerative thinking,
- documentation,
- storytelling,
- project execution,
- and cross-cultural communication.

For technical contributors, DEP 2 also provides opportunities to explore:
- workflow prototyping,
- DAO tooling,
- contribution tracking systems,
- and lightweight blockchain experimentation.

More importantly, DEP 2 encourages participants to learn how decentralized communities can:
- coordinate,
- create impact,
- experiment responsibly,
- and move toward sustainability together.

The goal is not only to complete deliverables, but also to build long-term collaborative capacity and shared learning across the cohort ecosystem.

How successful frameworks and deliverables from DEP 2 may continue to be supported or adopted after the program concludes.

• Frameworks and deliverables that prove their value during DEP 2 in general and the KAT Tokenomics DAO's outputs in particular are designed to feed into Kambria's longer-term DAO framework infrastructure.
• DAOs and contributors whose work proves effective gain priority for future co-funding, continued participation in DEP 3, and opportunities to take on ecosystem-wide leadership roles.
• Kambria's long-term vision is a self-organized network of DAOs, and strong DEP 2 outputs become the building blocks for that.

Expectations for cross-DAO collaboration during execution

We don't mandate a single rigid process — DAOs are expected to take initiative and reach out directly when their Master Plan identifies a dependency on another DAO. That said, we'll help facilitate introductions where needed, especially early in execution if a DAO is struggling to make contact. A good practice is to designate one point of contact per dependency and agree on even a lightweight monthly check-in — it doesn't need to be heavy process, just enough that both sides know what's expected and by when.

If a cross-DAO dependency doesn't come through — the other DAO doesn't respond, deprioritizes it, or its scope shifts — flag it early, ideally in your weekly report or directly to your facilitator, rather than waiting until it blocks a milestone. We evaluate DAOs based on how they handle that kind of risk, not just whether every dependency resolves perfectly. Documented, timely escalation is what we're looking for — it won't count against you the way silent failure would.

Additional guidance regarding: Best practices for measuring DAO impact and regeneration outcomes.

A few principles that apply across DAOs, not just specific to one Master Plan:

• Impact measurement:
  Define impact targets as specific, countable outputs (e.g., "3 governance experiments completed," "2-3 DAOs pilot the framework") rather than vague goals like "improve governance."
  Track progress weekly, not just at milestone deadlines — this catches drift early instead of discovering a miss at the final review.
  Tie each metric to evidence, not self-reported completion — a deliverable link, a usage log, a pilot DAO's confirmation, etc.
• Regeneration measurement:
  For DAOs producing non-financial assets (frameworks, templates, tools, documentation), regeneration value should be evidenced by adoption, not just creation. "We built a template" is weaker than "DAO X used our template in their proposal."
  Keep a simple running log: asset created → who adopted it → evidence link. This turns regeneration from an abstract claim into something auditable.
  If the regeneration target is monetary-equivalent (e.g., "$3,000 ecosystem value"), be explicit about how non-financial assets are being valued — otherwise the number is unverifiable and hard to defend at final review.
• General best practice:
  Report impact and regeneration together in weekly updates, not as a separate end-of-program exercise — this makes the Onboarding Sync and final review far less stressful since the data already exists.
  When in doubt, prefer metrics that are binary and verifiable (done/not done, adopted/not adopted) over subjective scoring — easier for facilitators to evaluate fairly across DAOs.

Would the timeline increase if there are inactive members since we will have to delegate the work among active members

Both the program timeline and your DAO's internal timeline have room to be adjusted to fit what best serves your goals — so member inactivity doesn't have to put your deliverables at risk.
The more important lever is how work is distributed: Working Group Leads and the DAO Lead can redistribute tasks among active members, and we encourage you to flag any capacity gaps to your DAO Facilitator early so we can support you.
We've also shared our approach to strengthening active contribution from DAO members in the Onboarding Overview presentation — please refer to that for how we're helping each DAO keep momentum during execution.

As Frontend Engineer in System Prototyping WG, when exactly do we start coding and what is the first technical task we should begin with?

The beginning for coding depends on our Masterplan and Working Group Plan, which should detail the timelines and assigned PICs for each task. Please coordinate with our DAO Lead, on Discord, to align on your specific schedule and confirm the initial technical tasks you should prioritize.

Participant-Proposed DAO

What are the expected outcomes or deliverables for participants during the program?

DEP 2 is structured around both individual contribution and collective DAO-level impact.

At the DAO level, each DAO has specific impact and regeneration goals. For example:
- the Cultural & Creative DAO aims to co-create 400 cultural expressions,
- the Exchange DAO aims to facilitate 500 meaningful 1–1 sessions,
- and the KAT Tokenomics DAO focuses on building the KAT Reward & Privilege Framework, MVP dashboard, and symbolic testnet systems.

At the participant level, expected outcomes may include:
- active participation in Working Groups,
- contribution to DAO deliverables,
- collaboration across teams,
- governance participation,
- documentation,
- experimentation,
- and community coordination.

Deliverables may vary depending on a participant’s role and Working Group, but generally include:
- execution outputs,
- reports,
- prototypes,
- workshops,
- coordination support,
- storytelling,
- or operational contributions.

DEP 2 emphasizes meaningful participation, collaboration, and learning over rigid task completion.

During the execution phase, what is the expected turnaround time for Kambria to respond to urgent requests (e.g., payment issues, technical support for XDAO voting)?

When encountering payment issues, technical support bottlenecks for XDAO voting, or other critical operational blocks, the DAO should utilize the following channels in order of priority:
Priority 1 — Self-Support: Review the DEP 2 Docs for immediate troubleshooting steps.
Priority 2 — Peer-Support: Use Discord to engage with other participants for quick, localized problem-solving.
Priority 3 — Direct Kambria Support: Submit formal, urgent issues via the official Kambria Contact Form.
Expected Turnaround Time: Once an issue is submitted through the formal contact form, the review and assistance window is typically 1 to 3 business days.

If a DAO exceeds its regeneration target (more than $3,000), can the surplus be carried over to Cohort 3 or reinvested into the project without penalty?

• There is no penalty for regenerating more than the $3,000 target.
• Per the DEP 2 Reinvestment Rules, regenerated funds (including any surplus) are intended to serve as seed capital for your DAO's next cycle in DEP 3.
• Their primary purpose is to fund future project cycles, to scale what works and enable self-sustainability — so successful DAOs keep building with less dependence on external seed funding

For DAOs working with children (like Pesa Play), does Kambria have additional child safety or data protection guidelines beyond what is already in the Master Plan?

Kindly check our DEP 2 Docs for more details:
. Child Safety & Safeguarding Guidelines
. Consent Form for DAO use
. Kambria Disclaimer (6. Activities involving Minors)

Will there be Portuguese-language support available during the Onboarding Sync Meeting on June 19, or written summaries afterward for Lusophone participants?

We will send all DAO members recordings and written recaps after the event.

For the PESA PLAY DAO master plan, is there any chance of it to be in a geographical other country to implement and the idea of it to be in a very open government assisted schools?

• At this stage, Hela Hive is in a structured pilot phase as defined in the Master Plan, which is focused on Nairobi-based schools.
• The reason for this is that the first priority is to validate the learning outcomes, usability, and school integration in a controlled environment where implementation can be properly supported and measured.
• Exploration of other geographies and school systems (including government-assisted schools or international expansion) is part of the longer-term scaling pathway, but it will only be considered after the pilot has generated sufficient evidence and validation data.