feat(examples): teritori's dao sdk

[n0izn0iz]

This implement a DAO SDK inspired by DA0-DA0

Continuation of #1925 in a branch that allows maintainers edits and has a sane base.

Last status on the previous PR was a message by @moul stating

Can you move all the packages under {r,p}/teritori/... and relocate the docs/... into r/teritori/dao_maker/README.md?

I believe we should merge your PR in its current state but under teritori.

We have iterated on this in our repo and it might lack a lot of features and bug fixes, we wonder if we should update or merge as-is.

It includes:

• Interfaces for the DAO gno.land/p/demo/dao_maker/dao_interfaces
• A reference implementation for the core of the DAO gno.land/p/demo/dao_maker/dao_core
• A membership-based voting module gno.land/p/demo/dao_maker/dao_voting_group
• A single-choice proposal module gno.land/p/demo/dao_maker/dao_proposal_single
• An example DAO gno.land/r/demo/dao_maker/dao_realm
• A registry to dynamically interact with any registered DAO using it's address gno.land/r/demo/dao_maker/dao_registry

For usage see the tutorial

---

There is an example membership-based DAO at gno.land/r/teritori/dao_realm that can administer itself and a grc20 token at gno.land/r/teritori/tori

Here is it's GnoWeb Render:

---

This powers the "Organizations" feature of Teritori dApp on Gno as shown below

The DAO creation UI uses a Gno template and instantiates a new realm.

Contributors' checklist...

• Added new tests, or not needed, or not feasible
• Provided an example (e.g. screenshot) to aid review or the PR is self-explanatory
• Updated the official documentation or not needed
• No breaking changes were made, or a BREAKING CHANGE: xxx message was included in the description
• Added references to related issues and PRs
• Provided any useful hints for running manual tests
• Added new benchmarks to generated graphs, if any. More info here.

[Gno2D2]

🛠 PR Checks Summary

All Automated Checks passed. ✅

Manual Checks (for Reviewers):

• IGNORE the bot requirements for this PR (force green CI check)

Read More

🤖 This bot helps streamline PR reviews by verifying automated checks and providing guidance for contributors and reviewers.

✅ Automated Checks (for Contributors):

🟢 Maintainers must be able to edit this pull request (more info)

☑️ Contributor Actions:

1. Fix any issues flagged by automated checks.
2. Follow the Contributor Checklist to ensure your PR is ready for review.
   • Add new tests, or document why they are unnecessary.
   • Provide clear examples/screenshots, if necessary.
   • Update documentation, if required.
   • Ensure no breaking changes, or include BREAKING CHANGE notes.
   • Link related issues/PRs, where applicable.

☑️ Reviewer Actions:

1. Complete manual checks for the PR, including the guidelines and additional checks if applicable.

📚 Resources:

• Report a bug with the bot.
• View the bot’s configuration file.

Debug

Automated Checks

Maintainers must be able to edit this pull request (more info)

If

🟢 Condition met
└── 🟢 The pull request was created from a fork (head branch repo: n0izn0iz/gno)

Then

🟢 Requirement satisfied
└── 🟢 Maintainer can modify this pull request

Manual Checks

**IGNORE** the bot requirements for this PR (force green CI check)

If

🟢 Condition met
└── 🟢 On every pull request

Can be checked by

• Any user with comment edit permission

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

📢 Thoughts on this report? Let us know!

[thehowl]

What is still pending on this PR? Just the CI?

[n0izn0iz]

well, that, and it's outdated code, I wonder if we should update this with the latest version we have in our monorepo