This is an awesome tool and I have been testing it out myself. I signed up for a user interview tomorrow. @HackHumanity mentioned I should go forth and put up a proposal for the Governance Memory System and the AI Governance Dashboard plugs into this scaffolding nicely.
A few specific data-model upgrades I think would materially improve the dashboard, add to GMS, and set up the ecosystem for proper decision analysis later:
1. Lifecycle Metadata
-
Proposal states (draft → screened → cycle → on-chain open → passed/failed → implemented/abandoned)
-
Timestamps for each state transition
-
On-chain linkages (Agora IDs, tx hashes, vote tallies)
These give us traceability and let us reconstruct how decisions actually moved through the system.
2. Structured Classification
-
Proposal type (param change, budget, program, meta-gov, etc.)
-
Domain tags (technical, treasury, governance, infra, community)
-
Impact scope + time horizon
This makes proposals comparable instead of just chronological.
**3. Stable Evaluation Fields
**
Currently the review categories are helpful for authors, but they provide AI-generated proposal critique categories, not structured metadata fields we can use inside GMS or governance tooling. We need numeric/categorical fields that can be compared across proposals and cycles. Here are some examples:
Core Evaluation Fields
-
clarity_of_problem (0–5)
-
feasibility (0–5)
-
risk_level (0–5 or categorical)
-
alignment_with_mvv (0–5)
-
reversibility (categorical)
-
defined_kpis (boolean + list)
Structural Metadata Fields
-
proposal_type
-
domain
-
lifecycle_state
-
authorship
-
timestamps
This becomes anchorable data for follow-up analysis.
4. Discussion Analytics as Data
- sentiment_score (0–1 or categorical)
- top_themes (list)
- unanswered_questions (list)
- consensus_state (categorical: rough consensus, polarized, etc.)
Super helpful for anyone trying to understand how alignment shifts over a proposal lifecycle.
5. Export / API
Even a simple CSV/JSON export or minimal API makes it possible for researchers, stewards, or tooling teams to build higher-order dashboards on top.
6. Outcome-ready Fields
Something simple like:
-
30/60/90 day check-in fields
-
freeform outcome notes
-
link to follow-up discussion or metrics
This anchors proposals to actual results rather than letting them disappear after a vote.
The MVV update already highlighted the need for a DAO Data Strategy, this would give the ecosystem the data infrastructure to actually pull that off with GMS. Happy to help refine any of this if useful.