Governance
Community-driven development and neutral foundation planning for PEAC Protocol.
Current Model
PEAC Protocol currently operates under an open-source, community-driven model:
- Open Development: All specifications and code developed in public repositories
- Community Input: Decisions made through GitHub Discussions and PEIPs process
- Collaborative Design: Multiple stakeholders contributing to protocol evolution
- Neutral Stance: No single vendor or organization controls the specification
Stewardship
PEAC is developed in the open by a community of maintainers. Originary provides project stewardship during the 0.9.x development phase. Originary builds infrastructure for the agentic web and maintains the reference implementations, but the protocol specification is community-governed through the PEIPs process.
No organization has exclusive control over the specification. All decisions are made through public discussion on GitHub.
Foundation Planning
We are exploring a neutral, multi-stakeholder governance model to steward the specification, conformance suite, and PEIPs process.
Proposed Structure
- Technical Steering Committee with multi-party representation
- Clear IP policies and contributor agreements
- Transparent decision-making processes
- Standards body engagement (IETF, W3C)
- Industry liaison and adoption support
PEIPs Process
PEAC Enhancement and Integration Proposals (PEIPs) provide a structured way to propose changes:
Submit initial proposal for community feedback
Technical review and community discussion
Incorporation into specification
Participation
Organizations interested in governance participation:
Stakeholder Groups
Key stakeholder categories in PEAC governance: