For Working Groups to Prepare Proposals Before Weekly DAO Review & Voting

This template ensures proposals are complete, clear, and ready for DAO discussion and voting.

Working groups should fill in every section unless marked optional.

1. Proposal Title

A short, clear title summarizing the action.

Examples:

• “Creative Workshop Series: Vietnamese Folk Art #1”

• “Regeneration Proposal: Paid Storytelling Circles”

• “Partnership Proposal: Collaboration with XYZ University”

2. Proposal Overview (Short Summary)

Provide a 3–4 sentence summary of the proposal. Include:

• What you want to do

• Why it matters

• Expected outcome

• Funding requested (if applicable)

3. Purpose & Background (Why This Proposal?)

Explain:

• The problem or need

• Context from previous DAO discussions

• Why this matters now

• Alignment with Cohort 2 focus (impact, regeneration, learning, community)

• (If applicable) External partners, collaborators, or customers involved

4. Alignment With DAO Goals

A. Impact Goal

How does the proposal contribute to the DAO’s measurable outputs?

B. Regeneration Goal

If relevant, how does this proposal contribute to the DAO’s $3,000 regeneration target?

(If not applicable → write “N/A”)

C. DAO Learning Goal

What experiment, insight, or exploration will emerge?

D. Cross-DAO or Cohort Contribution (optional)

Does the proposal benefit other DAOs or the cohort?

5. Activities & Action Plan

A. Activities

List step-by-step activities.

B. Deliverables / Outputs

Examples:

• Number of sessions

• Creative outputs

• Partnerships formed

• Regeneration outcomes

• Documentation required

• Multi-stakeholder participation (if applicable)

C. Timeline

Start date → end date → weekly milestones.

6. Roles & Working Groups

List members and contributors with clear distinctions:

A. Lead(s)

Responsible for coordination, reporting, and proposal presentation.

(Usually the WG Lead, with support from the DAO Lead and DAO Facilitator.)

B. Contributors (DAO Members)

Who is responsible for which tasks?

C. External Contributors (If Applicable)

Note roles for:

• Community Collaborators

• Partners / institutions

• Ambassadors

• Volunteers

• External Local Delivery Partners

• Customers / users (e.g., CED participants)

Important:

External contributors:

• DO NOT attend weekly DAO meetings

• DO NOT vote

• May receive KAT under Community Contribution categories

D. Support Roles

• Tokenomics integration

• Documentation support

• Communications / promotion

• Partnership follow-up

• Technical support

7. Budget Request (If Applicable)

If no funding required → write: “No seed funding requested.”

If funding required, include:

A. Total Amount Requested

B. Detailed Breakdown

• Supplies / materials

• Venue / logistics

• Professional fees

• Participant transportation

• Printing / production

• Contingency

C. Reasonableness & Necessity

Why these costs are essential.

D. Remaining DAO Budget

WG must stay within its assigned budget envelope.

E. Documentation Plan

How transactions will be recorded and reported.

8. Regeneration Component (If Applicable)

If regeneration is not part of this proposal → write: “This proposal does not include a regeneration activity.”

If regeneration is included, outline:

A. Regeneration Strategy

Examples:

• Sponsorship

• Ticketed event

• Paid sessions

• Membership model

• Corporate collaboration

• Community-based contributions

B. Target Audience / Stakeholders

Who will sponsor, pay, or participate?

(May include partners, institutions, CED users, communities, etc.)

C. Estimated Regeneration Value

Approximate revenue or regenerated value.

D. Risks & Dependencies

Partner readiness, logistics, venues, participant turnout, etc.

Add mitigation steps.

9. KAT Token Considerations (If Relevant)

If no KAT components → write: “No KAT-related components.”

If relevant:

A. How This Proposal Uses or Affects KAT

• Contribution categories

• Reward suggestions

• Inclusion of external stakeholders

• Privilege prototypes (optional)

B. Alignment With KAT Tokenomics DAO Guidelines

Confirm symbolic, non-financial usage and alignment with the KAT Reward & Privilege Framework.

C. Required Support From the KAT Tokenomics DAO

If needed for:

• Reward logic

• Dashboard integration

• Testnet prototypes

10. Dependencies & Risks

List all relevant dependencies:

• Cross-WG dependencies

• Cross-DAO dependencies

• Dependencies involving the KAT Tokenomics DAO

• Partner/venue availability

• Ambassador / volunteer / collaborator availability

• Customer participation (if applicable)

• Technical dependencies

• Scheduling issues

• External stakeholder or ecosystem risks

Include mitigation steps for each.

11. Success Criteria

Define how the DAO will know this proposal succeeded:

• Output targets

• Quality indicators

• Regeneration results (if applicable)

• Multi-stakeholder engagement

• Documentation completeness

• Learning outcomes

12. Documentation & Reporting Plan

A. Evidence to Be Collected

• Photos

• Videos

• Logs

• Creative files

• Attendance lists

• Partner confirmations

• Screenshots (online activities)

• External collaborator documentation (if applicable)

B. Completion Report Checklist

• Summary of execution

• Outputs & evidence

• Budget usage

• Reflections & insights

• Recommendations

C. Weekly DAO Meeting Updates

DAO Members must report weekly progress.
External contributors do not attend meetings.

13. Voting Options

Recommended default:

• Approve

• Reject

• Request Changes

DAOs may expand via governance proposal.

14. Proposal Attachments (Optional)

• Designs / mockups

• Partner LOIs

• Creative samples

• Budgets

• Schedules

• Regeneration projections

• Stakeholder maps

15. Submission Information

• Prepared by: WG Lead + members

• Date Submitted: DD/MM/YYYY

• Version: v1, v2…

SUMMARY

This template supports DEP 2’s goals by ensuring:

• Clarity

• Accountability

• Multi-stakeholder alignment

• Regeneration thinking

• Symbolic KAT integration

• Quality execution

• Weekly communication

• Cross-DAO collaboration

It is recommended that every DAO copy this template into its workspace and use it consistently.