# Build a DAGP community

DAGP is a seed framework: communities can study, fork and adapt its mechanism.
The current runnable starter is a synthetic reference society, not a production
financial or identity network.

1. Run the agent quickstart and inspect the report, refusals and limitations.
2. Write your community charter: purpose, eligible participants, resources,
   operator independence, appeal procedures and planned departures from DAGP.
3. Fork and record your version. Keep a public rule-change log and distinguish
   simulation, testnet and production modes in every interface.
4. Test changed rules against conservation, authorization, participation,
   minority protections, replay and bounded emergency authority.
5. Build real-agent adapters using isolated observations and signed typed actions.
   Do not give each model process access to the complete simulation's secrets.
6. Implement and review native identity, election, treasury and judicial keepers
   before relying on blockchain enforcement of governance.
7. Recruit independently operated participants and validators. Seven processes on
   one machine do not establish seven independent trust domains.
8. Begin with a capped testnet and publish evidence and unresolved assumptions.

## Compatibility statement template

- Community name and repository/version:
- Purpose and resource scope:
- Simulation/testnet/production status:
- Changed DAGP defaults and rationale:
- Identity/operator verification mechanism:
- Election, comprehension and judicial independence:
- Asset custody and maximum exposure:
- Tested invariants and recovery procedure:
- Outstanding assumptions and limitations:

## Contribution pathways

A useful contribution can be a translated guide, reproducible scenario, attack
report, rule comparison, identity admission implementation, real-agent adapter or
native governance module. Use GitHub issues and pull requests in the DAGP repository;
never include private keys, tokens or personal identity evidence.

DAGP does not currently operate a public citizen registry or a federation directory.
A future voluntary community directory should require verified ownership,
explicit implementation status and consent before listing participants.

## Integrate an existing society or cooperate with others

Use the [architecture/integration guide](https://github.com/Martines90/dagp/blob/main/docs/architecture/OVERVIEW.md): begin with
an explicit compatibility comparison and shadow decisions, then isolated agent
adapters and bounded workflows. A wholesale restart is not required to study or
adopt selected DAGP mechanisms. Native governance and public registration are
still unfinished; there is no supported live governance API to plug into today.

Federation preserves separate constitutions and can precede any permanent union.
The [society-merger proposal](https://github.com/Martines90/dagp/blob/main/chain/security/SOCIETY_MERGER.md) describes
bilateral 80% decisions, voluntary member claims and staged imports without
automatic political offices, validator power or duplicate credits. It is a
design option, not executable migration support.