Concordia DAO Council V1.5¶
Agentic payments on Casper are arriving. The unsolved half is authorization: when an autonomous agent can move funds, what proves a decision was actually approved — and what refuses the ones that weren't?
A gateway can be routed around. Concordia binds Dissent Receipts, browser-wallet quorum, and refusal to the exact approved hash in the governed action path, where an unapproved, altered, or replayed request still fails.
Concordia is an evidence-first governance council for AI-assisted DAOs on Casper Testnet. Named agents deliberate, challenge, and explain. Deterministic code evaluates policy, seals the transcript, binds approval to exact hashes, and prepares the receipt path. A human remains the final authority for execution.
What V1.5 proves¶
The canonical proposal DAO-PROP-6CB25C records:
- a complete V1 council and policy transcript;
- a canonical Testnet reviewer receipt
e926582f3dacd05d9bd59a4fe0ae3c3c884ad57f23ab7318925cef34c286d852; - an on-chain rejection before quorum and acceptance after 2-of-3 approval;
- downloadable JSON, CSV, HTML, PDF, certificate, and IPFS evidence; and
- SafePay Lite as recorded native-CSPR evidence under the Concordia apex.
Start with the 90-second judge path, then inspect the receipt and quorum lineage and verification limits.
Scope is intentionally narrow¶
V1.5 boundary
Casper-native x402 v2 is implemented as an HTTP 402 payment request, payment intent, and native-transfer verification on Testnet. A later official facilitator service and successful external-provider settlement are not shipped or claimed in V1.5. SafePay Lite remains recorded Testnet native-CSPR evidence.
The npm verifier retains historical V2/V3 parser and refusal compatibility. That compatibility does not promote those paths into the V1.5 product.
Core invariants¶
- Advisory output cannot directly mutate governance state.
- Policy and allocation arithmetic are deterministic.
- Human approval binds the exact proposal, plan revision, and action hash.
- Nonces are single-use.
- Missing, contradictory, unknown, or unavailable evidence never becomes success.
- Every public claim should resolve to source, a transcript, or a recorded Testnet artifact.
Public surfaces¶
Publication and hosted-state claims remain subject to the release gates in V1.5 Release Scope.