PolicyKit

• Name: PolicyKit
• URL: https://policykit.org/
• Category: governance-authoring infrastructure / online-community policy engine / cross-platform governance execution layer
• Summary: PolicyKit is governance-execution software for online communities. The real point is not programmable voting; it is which outside actions the system can observe, block, revert, or execute across Slack, Reddit, Discourse, GitHub, Open Collective, and similar platforms. That keeps it in cross-platform governance execution, not in the onchain-governor bucket.
• 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 lets communities author governance procedures and carry them out on home platforms. That is enough to classify it as governance execution infrastructure rather than just a policy editor.
  • The design overview defines the core model around Community, CommunityPlatforms, Policy, Proposal, Role, and Action types, so governance here is programmable state spread across multiple services.
  • The docs say each community includes both external platforms and a PolicyKit constitutional layer, which means governance changes can themselves become governable actions.
  • The integrations docs distinguish Actions, Trigger Actions, Governable Actions, and Voting. That external integration surface is the practical limit on what PolicyKit can actually govern.
  • Governance power depends on admin credentials, OAuth scopes, API keys, webhooks, and whether a platform supports revert or re-execute behavior. Authority is partly borrowed from upstream APIs.
  • The official README says PolicyKit leverages Metagov Gateway. That makes the Metagov-versus-PolicyKit split worth keeping: middleware below, policy authoring and execution above.
  • The theory references are fine, but the practical read is simpler: this is a cross-platform policy engine whose real power depends on integration coverage and admin scope.
• 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.
• Sources:
  • https://policykit.org/
  • https://policykit.readthedocs.io/
  • https://policykit.readthedocs.io/en/latest/design_overview.html
  • https://policykit.readthedocs.io/en/latest/integrations.html
  • https://raw.githubusercontent.com/policykit/policykit/master/README.md
  • https://github.com/policykit/policykit
  • https://policykit.org/static/policyengine/pdf/policykit_uist2020.pdf

Internal linkages

• Middleware beneath it: metagov.
• Stronger voting-layer anchor it can wrap or execute around: snapshot.

Control surface

• The leverage sits in which outside platforms are integrated, which actions count as governable, what credentials the operator has on those platforms, and which policies are allowed to intercept or auto-execute behavior.

• Read it as cross-platform governance execution with borrowed upstream API power, not as a general-purpose governor.

• Last reviewed: 2026-06-09 UTC