A Rust-based common data model and set of platform adaptors for deliberative-democracy tools, from the Metagov research collective (metagov/ontology). Core entities: Person, Statement (roles: Question, Belief, Fact, Evidence, Refutation, Summary, Proposal, Decision), Project, Phase, Reaction, Collection, Event; decision mechanisms include ranked-choice and quadratic voting. Exports to three target formats — RDF/JSON-LD (semantic web/research publication), AT Protocol lexicons (Bluesky/ATproto integration), and JSON Schema (API validation/OpenAPI) — rather than depending on any single transport substrate. Ships platform adaptors for Polis (opinion clustering), HeyForm (forms/polls), and Talk to the City (API-based report generation). Its data-model and adaptor structure appears extracted from CrownShy's Comhairle (github.com/crownshy/comhairle, AGPL-3.0, 1,518 commits) — a real architectural lineage, though Comhairle itself is a conventional AWS/K8s deliberation web platform with no inter-instance protocol of its own and is not itself part of this matrix. Distinct from, and complementary to, this project's existing Decentralized Deliberation Stack (DDS) entry: DDS is a W3C Community Group protocol/interface spec (Plan/Collect/Analyze) built specifically on AT Protocol as a required transport layer, whereas this project defines a transport-agnostic data model with ATProto lexicons as only one of several optional export targets, plus concrete adaptors to existing tools rather than new interfaces.
LicenseMPL-2.0 per README header; no LICENSE file detected (GitHub's automated license detection returns none for this repo — a deliberate sourcing distinction from a formally-filed license, not equivalent to a flat MPL-2.0 grant)
Dev Status 📝 Draft
OwnerMetagov research collective (metagov GitHub org)
Owner - List
Metagovernance Project
Governing BodyMetagov research collective (no single commercial owner)
CountryInternational (Metagov research collective; no single-country affiliation stated)
Start Year 2025
StackRust (data model, exporters, adaptors)
FundingUnknown — no funder or sponsor disclosed
Last Investigated Aug 22, 2026
Topology view
This tool in the centre and the things it is directly related to. Each line names the kind of relationship.
OriginsDeliberative democracy / civic tech interoperability — motivated by the same tool-siloing problem DDS addresses (data from one deliberation tool can't be read by another), approached via a common data model + adaptors rather than a new transport protocol
DatabaseN/A — defines a data model and exporters, not storage; data lives wherever the exporting platform or ATProto lexicon target stores it
Query LanguageN/A
Data FormatsRDF/JSON-LD; AT Protocol Lexicon schemas; JSON Schema — three parallel export targets for the same underlying data model
Collaborative Live EditingN/A
Rich Text EditingN/A
Mobile SupportN/A (data model/library, not an end-user app)
Web SupportN/A directly; consumed by web-based adaptor targets (Polis, HeyForm, Talk to the City)
Native AppsN/A
TermsFree / open (license intent stated as MPL-2.0; see license nuance above)
FundsUnknown
Based OnDeliberation-tool data drawn from Polis, HeyForm, and Talk to the City (adaptor targets); AT Protocol Lexicon spec (one of three export targets); data-model and adaptor structure appears extracted from CrownShy's Comhairle (github.com/crownshy/comhairle, AGPL-3.0)
Semantic Web CompatibilityYes — RDF/JSON-LD is one of the three first-class export targets, explicitly for semantic-web/research-publication use
Protocol Maturity / StandardizationPre-standard, single-repository research project; no formal standards-body involvement; overlaps in subject matter with the W3C Community Group-backed DDS entry but pursues a different (data-model-first, multi-target-export) approach
Usage PatternLibrary/exporter consumed by adaptors for existing deliberation platforms (Polis, HeyForm, Talk to the City), not a standalone end-user tool
Relationships
How this tool connects to other tools and organizations, from relationships reviewed by the OpenHaven data steward. They describe how projects connect, not how good they are.