Summary: PolicyKit is best cataloged as a governance-authoring and governance-execution layer for online communities rather than as an onchain governor or a simple voting bot. Its official materials describe a system where governance is expressed as policies over actions, proposals, roles, and community objects, then automatically carried out on the platforms where a community already operates. The reusable mechanism is not just “programmable voting”; it is the attempt to turn governance into a portable policy engine whose real power depends on which outside actions can be observed, intercepted, reverted, or executed across Slack, Reddit, Discourse, GitHub, Open Collective, and related tools.
What it does:
Lets communities author governance procedures as short policy scripts tied to actions and trigger events
Models one community across multiple platforms plus a dedicated constitutional layer for governance-specific actions
Supports platform integrations that can observe events, perform actions, run votes, and in some cases govern or revert platform-native actions
Uses roles, proposals, and evaluation loops to decide whether actions should pass, fail, notify users, or trigger follow-on behavior
Leverages Metagov Gateway for cross-platform integrations and governance-process execution
Key claims:
The official site and docs say PolicyKit empowers community members to author governance procedures and automatically carry them out on their home platforms, which is the clearest reason to model it as governance execution infrastructure instead of just a policy editor
The design overview defines the core data model around Community, CommunityPlatforms, Policy, Proposal, Role, and Action types, showing that PolicyKit treats governance as programmable state layered across multiple services
The same docs say each community includes both external community platforms and a PolicyKit constitutional layer, which means governance changes can themselves be treated as governable actions
The integrations docs distinguish Actions, Trigger Actions, Governable Actions, and Voting, making the external integration surface the practical control point for what PolicyKit can actually govern
Those integration docs also show that governance power depends on admin credentials, OAuth scopes, API keys, webhooks, and whether a platform supports revert/re-execute behavior, so authority is partly constrained by upstream platform APIs
The official README says PolicyKit is a governance-authoring application that leverages Metagov Gateway, which makes it a useful comparison class against Metagov’s middleware role and DAOstar-style metadata legibility layers
The official docs link PolicyKit’s design to Elinor Ostrom and the ACM UIST 2020 paper, reinforcing that the project is grounded in governance-design research rather than only in app-specific workflow automation
Whitepaper: No standalone whitepaper surfaced in this pass. The strongest primary materials were the official site, official docs, integrations and design-overview pages, repository README, and the UIST 2020 paper linked from the docs; see ../whitepapers/policykit-primary-sources-2026-05-09.md.