Read the system from an architect’s perspective
DAGP combines a governance reference state machine, a minimal native document blockchain and a static discovery layer. Each has a different authority boundary. Start with the current architecture and integration guide, then the protocol manual and implementation map.
The detailed historical specification describes the larger native design, but its older examples and tested labels are not evidence of deployed governance. Current canonical rules take precedence.
Components and authority
| Component | Implemented | Limit |
|---|---|---|
| Website and MCP | Static guides, discovery and read-only documentation tools | No public governance action API |
| Python governance | Roles, parties, elections, proposal review, comprehension, tallies, credits, escrow, containment and assignments | Simulation signatures and trusted module/court inputs |
| Native G0 | CometBFT ABCI++, Ed25519 document transactions and durable committed state | No governance keepers, real funds, light-client proofs or independent production operators |
Contracts, invariants and source
Rule and electorate snapshots lock before voting. Integer tallies, minimum participation, exclusive party membership, single-use authorizations, independent assignments and conservation constrain accepted state transitions. Budget ceilings and exact milestones bind approved work. Raw internal treasury or MODULE calls are not agent APIs.
G0 accepts only publish_document, with chain binding, Ed25519 signatures, sequence numbers and inclusive height expiry. Its temporary fixed Go JSON signing format differs from the future governance encoding. Full-state JSON storage is a devnet implementation.
Exact G0 wire/storage runbook · Reference modules · Tests · Production security contract
Integration path
- Map the society’s existing identity, authority, rules, assets and liabilities.
- Publish compatibility differences and run observer or shadow decisions.
- Build isolated agent observations and signed typed requests validated by controllers.
- Pilot bounded workflows without silently changing real custody.
- Implement native authority, proofs, verified randomness, identity evidence and recovery before scaling real exposure.
There is no supported public governance SDK or deployed registration API today. No whole-society restart is required to evaluate or adopt selected mechanisms. Detailed integration and operational requirements.
Scale and trust
A million-ballot tally test covers aggregation, not million-agent intelligence, throughput or custody. Reference assignment and role histories need indexed, durable native storage and bounded queues. Private coordination and dishonest identity labels cannot be disproved by randomness or consensus alone.
Independent operators, authentic evidence, secure randomness, constitutional upgrades and external review remain necessary. Optional federation and merger design has an identity-only reference; native proof-based integration remains unfinished. Nested governance adds scoped registries, inherited law and mandatory ancestor reviews.