{
  "schema_version": "initiative-changes.v1",
  "registry_version": "2026.06.10-8752c9d",
  "initiative_id": "onchain-governance-readiness",
  "change_count": 7,
  "changes": [
    {
      "schema_version": "initiative-change.v1",
      "id": "governance-dao-ops-tooling-surface",
      "initiative_id": "onchain-governance-readiness",
      "type": "external_reference",
      "status": "reviewed",
      "summary": "DAO operations tooling covers proposal creation, delegate profiles, voting interfaces, templates, Safe integration, organization settings, and governance admin workflows.",
      "affected_roles": [
        "governance_operators",
        "dao_builders",
        "ai_agents"
      ],
      "affected_builder_groups": [
        "dao_operations_teams",
        "protocol_teams",
        "grant_program_teams"
      ],
      "affected_protocols": [
        "safe"
      ],
      "affected_chains": [
        "ethereum",
        "arbitrum-one",
        "base",
        "optimism"
      ],
      "affected_intents": [
        "gasless-onboarding"
      ],
      "possible_consequences": [
        "Tally and Aragon are official-source-backed DAO operations surfaces but are registry coverage gaps until first-class records exist.",
        "Agents should avoid recommending a governance UI without checking whether the underlying contract framework and voting model are supported.",
        "Safe-first governance can be appropriate for treasuries and smaller organizations, but it should not be described as token-holder governance unless voting controls actually route execution."
      ],
      "priority": "medium",
      "recommended_action": "assess",
      "recommendation_strength": "actionable",
      "evidence_refs": [
        "official:tally-docs",
        "official:aragon-docs",
        "official:aragon-osx-setup",
        "official:safe-docs"
      ],
      "last_verified_at": "2026-06-09"
    },
    {
      "schema_version": "initiative-change.v1",
      "id": "governance-governor-contract-surface",
      "initiative_id": "onchain-governance-readiness",
      "type": "protocol_architecture",
      "status": "reviewed",
      "summary": "Governor contracts define proposal creation, voting, quorum, vote counting, and execution mechanics, but they are only one layer of a complete governance stack.",
      "affected_roles": [
        "dao_builders",
        "smart_contract_developers",
        "ai_agents"
      ],
      "affected_builder_groups": [
        "protocol_governance_teams",
        "token_governance_builders",
        "hackathon_governance_projects"
      ],
      "affected_protocols": [
        "safe"
      ],
      "affected_chains": [
        "ethereum",
        "arbitrum-one",
        "base",
        "optimism"
      ],
      "affected_intents": [
        "deploy-on-a-low-cost-l2"
      ],
      "possible_consequences": [
        "Agents should separate the Governor contract from the UI, treasury wallet, timelock, indexer, voting token, and delegation layer.",
        "OpenZeppelin Governor, Tally Governor deployment flows, and Aragon OSx are official-source-backed surfaces but are registry coverage gaps until first-class records exist.",
        "Builders should not claim a DAO is production-ready from a Governor contract alone without reviewing token voting, roles, timelock, execution, and recovery controls."
      ],
      "priority": "high",
      "recommended_action": "assess",
      "recommendation_strength": "actionable",
      "evidence_refs": [
        "official:openzeppelin-governance-guide",
        "official:openzeppelin-governance-api",
        "official:tally-deploy-governor"
      ],
      "last_verified_at": "2026-06-09"
    },
    {
      "schema_version": "initiative-change.v1",
      "id": "governance-indexing-auditability-surface",
      "initiative_id": "onchain-governance-readiness",
      "type": "indexer_surface",
      "status": "reviewed",
      "summary": "Governance UIs and agents need reliable indexing for proposals, votes, delegation, quorum, queueing, execution, cancellation, and treasury actions.",
      "affected_roles": [
        "indexer_teams",
        "governance_operators",
        "ai_agents"
      ],
      "affected_builder_groups": [
        "governance_dashboard_builders",
        "governance_agent_builders",
        "protocol_monitoring_teams"
      ],
      "affected_protocols": [
        "the-graph",
        "goldsky",
        "safe"
      ],
      "affected_chains": [
        "ethereum",
        "arbitrum-one",
        "base",
        "optimism"
      ],
      "affected_intents": [
        "deploy-on-a-low-cost-l2"
      ],
      "possible_consequences": [
        "Agents should verify proposal lifecycle state from contract events or indexed sources before claiming a proposal passed, queued, executed, or failed.",
        "Governance frontends should account for Governor proposal IDs, description hashes, vote events, timelock operation hashes, and Safe treasury actions.",
        "The Graph and Goldsky are registry-covered indexing options, but exact governance schemas and event coverage should be validated per framework."
      ],
      "priority": "medium",
      "recommended_action": "assess",
      "recommendation_strength": "actionable",
      "evidence_refs": [
        "official:openzeppelin-governance-api"
      ],
      "last_verified_at": "2026-06-09"
    },
    {
      "schema_version": "initiative-change.v1",
      "id": "governance-private-voting-surface",
      "initiative_id": "onchain-governance-readiness",
      "type": "external_reference",
      "status": "reviewed",
      "summary": "Private governance voting requires choosing between membership privacy, vote privacy, coercion resistance, tally verification, and coordinator trust assumptions.",
      "affected_roles": [
        "privacy_builders",
        "dao_builders",
        "grant_program_teams",
        "ai_agents"
      ],
      "affected_builder_groups": [
        "private_voting_projects",
        "quadratic_funding_teams",
        "anonymous_membership_governance_builders"
      ],
      "affected_protocols": [
        "maci",
        "semaphore"
      ],
      "affected_chains": [
        "ethereum",
        "arbitrum-one",
        "base",
        "optimism"
      ],
      "affected_intents": [
        "build-private-onchain-voting"
      ],
      "possible_consequences": [
        "Semaphore is a strong fit for anonymous group membership proofs and double-signaling prevention, but it is not a full DAO execution stack by itself.",
        "MACI is a strong fit for private onchain voting and anti-collusion properties, but builders must document coordinator assumptions and supported networks.",
        "Agents should avoid broad anonymity or coercion-resistance claims unless the chosen primitive and operational model support them."
      ],
      "priority": "high",
      "recommended_action": "assess",
      "recommendation_strength": "actionable",
      "evidence_refs": [
        "official:maci-docs",
        "official:semaphore-docs"
      ],
      "last_verified_at": "2026-06-09"
    },
    {
      "schema_version": "initiative-change.v1",
      "id": "governance-snapshot-signal-vs-execution-surface",
      "initiative_id": "onchain-governance-readiness",
      "type": "external_reference",
      "status": "reviewed",
      "summary": "Snapshot-style governance can mean offchain gasless signaling or Snapshot X fully onchain voting, and agents should not collapse those into one execution model.",
      "affected_roles": [
        "dao_builders",
        "governance_operators",
        "ai_agents"
      ],
      "affected_builder_groups": [
        "signaling_governance_teams",
        "executable_governance_teams",
        "hackathon_governance_projects"
      ],
      "affected_protocols": [],
      "affected_chains": [
        "ethereum",
        "arbitrum-one",
        "base",
        "optimism"
      ],
      "affected_intents": [
        "gasless-onboarding"
      ],
      "possible_consequences": [
        "Agents should distinguish offchain Snapshot voting from Snapshot X, which documents fully onchain voting, onchain voting-power computation, and trustless proposal execution.",
        "Offchain signaling can be useful for governance process and UX but should not be described as binding onchain execution without a separate execution path.",
        "Snapshot and Snapshot X are official-source-backed surfaces but are registry coverage gaps until first-class records exist."
      ],
      "priority": "medium",
      "recommended_action": "assess",
      "recommendation_strength": "actionable",
      "evidence_refs": [
        "official:snapshot-docs",
        "official:snapshot-x-overview"
      ],
      "last_verified_at": "2026-06-09"
    },
    {
      "schema_version": "initiative-change.v1",
      "id": "governance-timelock-execution-surface",
      "initiative_id": "onchain-governance-readiness",
      "type": "protocol_architecture",
      "status": "reviewed",
      "summary": "Timelocks and execution roles decide when approved proposals can affect protocol contracts, treasuries, and permissions.",
      "affected_roles": [
        "smart_contract_developers",
        "governance_operators",
        "security_reviewers",
        "ai_agents"
      ],
      "affected_builder_groups": [
        "treasury_governance_teams",
        "protocol_upgrade_teams",
        "grants_program_operators"
      ],
      "affected_protocols": [
        "safe"
      ],
      "affected_chains": [
        "ethereum",
        "arbitrum-one",
        "base",
        "optimism"
      ],
      "affected_intents": [
        "deploy-on-a-low-cost-l2"
      ],
      "possible_consequences": [
        "The timelock should hold governed assets, ownership, and access-control roles when proposals are meant to execute binding actions.",
        "Proposer, executor, canceller, and admin roles are security-critical and should be reviewed before deployers renounce setup permissions.",
        "Governance UIs and agents should distinguish proposal passage from queued, ready, executed, cancelled, or expired execution state."
      ],
      "priority": "high",
      "recommended_action": "assess",
      "recommendation_strength": "actionable",
      "evidence_refs": [
        "official:openzeppelin-governance-guide",
        "official:openzeppelin-governance-api",
        "official:safe-docs"
      ],
      "last_verified_at": "2026-06-09"
    },
    {
      "schema_version": "initiative-change.v1",
      "id": "governance-voting-power-delegation-surface",
      "initiative_id": "onchain-governance-readiness",
      "type": "protocol_architecture",
      "status": "reviewed",
      "summary": "Voting power and delegation determine who can propose, vote, meet quorum, and represent token holders or members.",
      "affected_roles": [
        "dao_builders",
        "governance_operators",
        "ai_agents"
      ],
      "affected_builder_groups": [
        "token_governance_builders",
        "delegate_program_teams",
        "membership_governance_builders"
      ],
      "affected_protocols": [],
      "affected_chains": [
        "ethereum",
        "arbitrum-one",
        "base",
        "optimism"
      ],
      "affected_intents": [
        "gasless-onboarding"
      ],
      "possible_consequences": [
        "Agents should ask whether voting power comes from ERC20Votes, ERC721Votes, a wrapped legacy token, a membership list, or another strategy.",
        "Proposal thresholds, quorum, voting delay, voting period, and delegation support should be treated as governance design choices, not defaults to copy blindly.",
        "Gasless delegation or voting can improve participation, but it does not remove the need to verify voter eligibility and signature handling."
      ],
      "priority": "high",
      "recommended_action": "assess",
      "recommendation_strength": "actionable",
      "evidence_refs": [
        "official:openzeppelin-governance-guide",
        "official:tally-docs"
      ],
      "last_verified_at": "2026-06-09"
    }
  ]
}