PEAC
v0.10.0Pre-1.0

Governance

How PEAC Protocol is maintained, governed, and how to contribute.

Current Stewardship

PEAC Protocol is maintained by Originary during the pre-1.0 phase.

-All development happens in public on GitHub
-Community input via GitHub Issues and Discussions
-Pull requests welcome from all contributors

Scope Discipline

What PEAC standardizes

  • -Policy surface (/.well-known/peac.txt)
  • -Signed record format (receipt files)
  • -Deterministic verification rules
  • -Evidence bundles for disputes and audits

What PEAC does NOT standardize

  • -Identity systems or registries
  • -Payment rails or custody
  • -Observability platforms
  • -Agent orchestration protocols

Neutrality and Non-capture Commitments

  • No exclusive control as a condition of funding
  • Multi-implementation expectation: the standard is not one codebase
  • Published conformance fixtures as the enforcement mechanism, not trust

Decision Process

-Where proposals live: GitHub Issues and Discussions
-How decisions are recorded: Decision log and release notes
-Multi-implementation expectation: Conformance fixtures are the arbiter, not any single implementation

Verification-first Posture

  • -Deterministic verification using portable artifacts and public keys
  • -Conformance levels (L0-L3) with golden test vectors
  • -Third party can reach the same result without issuer cooperation

Privacy and Minimization Stance

  • -Prefer hashes and references over raw payloads
  • -No identity collection required by the protocol
  • -Minimize data exposure while preserving audit utility

Security Posture

  • -Fail-closed defaults: ambiguity is an attack surface
  • -Strict parsing: reject malformed inputs rather than guess
  • -Replay and time-window protection built in

Standards Posture

  • -Conformance fixtures published for cross-implementation parity
  • -Cross-language parity targets (TypeScript, Go)
  • -Interoperability bridges with existing ecosystems, not replacement

Contributing

Code

Submit pull requests to the main repository.

github.com/peacprotocol/peac

Proposals

Propose changes via GitHub Discussions or open an issue.

GitHub Discussions

Contact

For collaboration inquiries.

contact@peacprotocol.org

Future Plans

Governance evolution is planned as the protocol matures:

  • -Broader maintainer base after v1.0
  • -Formal contribution guidelines
  • -Community governance model under consideration

License

PEAC Protocol is released under the Apache-2.0 license.

Back to home