Metagov is best understood as governance middleware: a gateway that connects governance drivers to outside services rather than a voting application or a standalone standards spec.
The core architectural split is driver versus gateway. The driver decides governance policy; Metagov exposes outside tools through plugins, actions, listeners, and governance-process abstractions.
Plugin design is the key reusable mechanism. A plugin can expose actions, webhook listeners, and asynchronous governance processes, which means integration design determines what a governance engine can even see or do.
Community-specific plugin activation/configuration is a major control surface. Governance depends not just on nominal policies but on which integrations a community enables and how they are configured.
The API surface matters because it defines how external platforms send events into the governance system and how HTTP drivers invoke governance-related actions and processes.
The Gateway README’s June 2024 note that development was largely folded into PolicyKit is useful lineage information: even where active development shifted, Metagov remains important as an architecture for cross-platform governance composition.
Specific source signals worth retaining
Official docs landing page: describes Metagov as a unified API gateway for digital governance services designed for rapid prototyping of governance systems, decision-making processes, and social workflows.
Site mission page: frames Metagov as a laboratory for digital governance and a governance layer for the internet, which helps explain why the project spans standards, community work, and software.
Gateway README: lists supported external services such as Discord, Slack, Discourse, GitHub, Open Collective, Loomio, SourceCred, and NEAR, showing the cross-platform governance thesis.
plugin_tutorial.rst: makes explicit that plugins expose actions, listeners, and governance processes through registry decorators and community-specific configuration.
PolicyKit README: confirms the close relationship where PolicyKit acts as a governance-authoring application leveraging Metagov Gateway.
Why this entry belongs in the corpus
Metagov belongs in the corpus because it captures a reusable but easy-to-miss governance control surface: middleware that governs how policies interact with real communication and execution platforms.
It improves comparisons across DAO tooling, standards, chat/forum governance, and cross-platform policy engines by showing that authority can sit in integration layers long before anything reaches an onchain vote or multisig.
The reusable insight is that self-governance often depends not only on who votes, but on the middleware that decides which platforms are connected, which events become governable, and which actions a policy engine may trigger.