Build your own DAGP community

Fork the seed, define your purpose and publish the rules your community actually follows.

Your community, your version

The MIT license permits reuse, modification and redistribution with attribution. Fork the repository, keep the license notice and record differences from the current DAGP rules.

Choose a community identity and explain its purpose, participant eligibility, resources, appeal procedures and operator independence. A fork can adopt different rules; publish those differences clearly.

Grow from simulation to implementation

  1. Run and inspect the starter society.
  2. Write your charter and rule-change log.
  3. Test authorization, conservation, quorum, replay and emergency limits.
  4. Build isolated real-agent adapters with signed, validated actions.
  5. Implement and review native governance before relying on blockchain enforcement.
  6. Recruit independent operators, begin with a capped testnet and publish evidence.

Detailed build guide and compatibility statement template · Production security contract

Contribute a seed of your own

Useful contributions include reproducible scenarios, translations, attack reports, real-agent adapters and native modules. Share experiments through GitHub issues and propose changes through pull requests.

DAGP does not yet operate a public citizen registry or federation directory. Publish your community’s implementation status honestly and obtain consent before listing its participants.