Governance Model
Transparent, structured, and designed for the commons
Open standards fail when governance is left implicit. The PVC adopts governance principles proven by decades of commons research and open-source institutional practice — because credible governance is what makes an open standard trustworthy enough to build on.
Why Governance is a First-Class Product
The PVC specification is a commons — a shared resource that benefits everyone who uses it. Commons succeed or fail based on how they're governed. Elinor Ostrom's research on successful commons governance identified key institutional design principles: clear boundaries, proportional costs and benefits, collective decision-making, monitoring, graduated sanctions, conflict resolution, and nested governance at multiple scales.
The PVC governance model adapts these principles for a digital knowledge commons. Unlike natural commons (fisheries, forests), the PVC specification is non-rival — using it doesn't deplete it. But the maintenance, evolution, and coordination capacity of the consortium is rivalrous: maintainer attention, review bandwidth, and governance participation are scarce resources that require institutional design.
Foundation-governed open source projects (Apache, Eclipse, Linux Foundation) have demonstrated that governance credibility — neutrality, transparency, earned authority — is itself a competitive advantage. The PVC builds on this proven foundation.
Governance Structure
The Steering Council is the top-level governance body. It ratifies specification changes, approves new working groups, manages trademark policy, and ensures the consortium remains vendor-neutral. Members are elected from active contributors and stakeholder representatives.
- - Composed of elected members from venues, partners, and individual contributors
- - No single organization may hold more than one-third of seats
- - Terms are staggered to ensure institutional continuity
- - All votes and decisions are published
Domain-specific working groups handle detailed specification work, conformance testing, and ecosystem guidance. Working groups are where most day-to-day governance happens.
- - Specification WG: Evolves the four pillars and conformance criteria
- - Certification WG: Manages certification process, tiers, and audit procedures
- - Transparency WG: Develops venue media transparency profiles and tooling
- - Ecosystem WG: Coordinates partner programs, events, and community building
Regional chapters enable local adaptation while maintaining global coherence. Chapters can organize events, develop localized guidance, and represent regional perspectives in the governance process. This nested structure follows Ostrom's principle that governance should operate at the scale closest to the affected community.
Decision-Making Process
All specification and policy changes follow a structured, public process. This ensures changes are deliberate, well-reviewed, and reflect broad stakeholder input.
1. Proposal
Anyone — member or non-member — can submit a proposal to modify the specification, add guidance, or change policy. Proposals follow a standard template and are publicly filed.
2. Working Group Review
The relevant working group reviews the proposal, solicits feedback, and may request revisions. Discussion is public and archived.
3. Public Comment Period
Proposals that pass working group review enter a public comment period (minimum 30 days for specification changes). All stakeholders — including non-members — can submit feedback.
4. Ratification
The Steering Council ratifies proposals that have achieved rough consensus. Ratification votes are recorded and published. Dissenting views are documented.
5. Implementation
Ratified changes are incorporated into the next specification version. Certification criteria are updated accordingly, with transition periods for existing certified venues.
Contributor Pathways
Governance standing is earned through sustained, quality contribution — not purchased. This follows the "earned authority" model proven by Apache and other foundation-governed projects.
Anyone can read the specification, attend public meetings, and submit feedback during comment periods. No membership required.
Members who actively submit proposals, review others' proposals, or contribute to working group activities. Contributors sign the IPR commitment.
Sustained contributors who are granted editing rights on specification drafts and working group documents. Nominated by working groups, confirmed by the Steering Council.
Elected to the Steering Council from the committer pool and stakeholder representatives. Council members ratify specification changes and set consortium policy.
Conflict Resolution
Governance capture — where a single vendor or faction gains disproportionate control — is the primary failure mode for open standards. The PVC includes explicit safeguards:
Concentration Limits
No single organization may hold more than one-third of Steering Council seats. Working group chairs must represent different organizations.
Escalation Path
Disputes within working groups escalate to the Steering Council. Disputes with Steering Council decisions can be appealed through a documented mediation process.
Transparency as Accountability
All votes, decisions, and financial flows are published. Sunlight is the best disinfectant against governance capture.
Fork Rights
Because the specification is openly licensed, the community always retains the right to fork. This is the ultimate safeguard: governance must remain credible because participants can leave.
Funding & Stewardship
The standard is free. Maintaining it is not. The PVC funds stewardship through a portfolio model — not by making the specification scarce.
Membership Dues
Certified venues and partners pay membership dues proportional to their scale. Dues fund spec maintenance, governance operations, and community coordination.
Certification Revenue
Certification review and audit processes generate revenue that supports the quality and credibility of the certification program.
Targeted Grants
Public and philanthropic grants for specific initiatives: transparency tooling, conformance test suites, accessibility guidance, and ecosystem security.
Event & Summit Revenue
The annual Programmable Venue Summit and regional events generate revenue while building community and advancing the ecosystem.
All financial flows are published transparently. The PVC will explore fiscal hosting and transparent budgeting to ensure accountability.