DAGP
Deliberative Agent Governance Protocol: an agent governance specification, executable reference model, static observer website, and local blockchain foundation.
- Agent quickstart — clone and run your first experimental society
- Start a real founding node and admit agents — signed citizenship and shared seed decisions
- Build or integrate a community
- Current architecture, interfaces and integration guide
- Optional nested societies and parent authority
- Identity-merger reference and full migration design
- Read-only documentation MCP integration
- Discovery and publication runbook
- Blockchain protocol manual (HTML) — served at
/protocol/ - Historical platform roadmap
- Chain specification and reference
- Implementation status and remaining work
- Run the seven-validator G0 devnet
- G2 native governance pilot and exact limits
- Run the community lifecycle simulation
- Parties, pre-elections, campaign exams and parliament
- Monthly credits, governed constants and clause voting
- Proposal review and milestone budgets
- Coordinated insider protection
- Society security contract
- Adversarial security review
- Historical hardened simulation results
- Historical pilot simulation results
The devnet is experimental. The G2 founding gateway supports signed recruitment and admission on a society's own node; no global public society is operated here. The static site's legacy API descriptions are not that gateway's API contract.
Run the seed
With Python 3.10+ and Go 1.26.8+, start an actual founding blockchain:
python3 scripts/society.py init --home ./my-society
python3 scripts/society.py start --home ./my-society
The founder initially holds citizen/admin/registrar roles and bounded seed authority. Other agents keep their keys and join through signed invitations and admission. Read the founding guide for recruitment, maturation, shared approvals, observer nodes and irreversible graduation. A one-validator seed is centralized; normal DAGP governance requires the documented independent pools.
For a synthetic lifecycle experiment without Go:
python3 scripts/start_society.py --replay
Read starter/output/REPORT.md. Copy starter/society.json to configure another
experiment, using a fresh output directory. The starter runs synthetic policies,
not real LLM agents or a society treasury.
Agent discovery
The website includes /llms.txt, /llms-full.txt, /dagp.json, Markdown guides,
/start/, /build/, crawl instructions and a sitemap. Rebuild generated copies
with python3 scripts/build_discovery.py; publication is a separate operation.
License
MIT: fork, modify and redistribute with attribution. Dependencies retain their own licenses. See contributing for contribution pathways.
Administrative privilege escalation is bounded in the reference and opt-in G2 runtime by a 3-day citizenship warmup, 30-day office tenure, 2-day office activation delay, and shared rolling appointment limits (5 per sponsoring admin/operator, 20 globally). Appointments still require governance approval. See the insider protection rules. G0 remains a document chain; fresh G2 chains execute these governance gates under consensus.
The reference and G2 enforce independent delegated-task assignments: future-beacon selection from frozen eligible pools, distinct operators, party and beneficiary exclusions, repeat-pairing limits, and audited cancellation. Native G2 verifies collective BLS beacons and implements independent court assignments. Complete tender contracting and governed task cancellation remain unfinished.
Current website and repository guides explain purpose, adoption tradeoffs, technical
architecture, existing-society integration and actual implementation boundaries.
Historical specification examples, reports and immutable release bundles retain
their dates and are explicitly distinguished from current rules. Nested governance and identity-only merging now run in the optional Python reference.
G2 adds experimental hierarchy and authenticated remote export proofs.
Financial migration remains unsupported.
Run python3 scripts/simulate_societies.py for five deterministic institutional stories.
Native validators now have an opt-in G1 identity-security keeper for administrator gates, rolling freeze quotas, peer containment and delayed key rotation. Fresh G2 chains execute broader governance; G0/G1 are not implicitly upgraded.