Collaborate on PEAC
PEAC grows through verification work: independent implementations, audits, conformance, and pilots where cross-org evidence is a real requirement.
What we are seeking
Institutional pilots
Where auditability or reconciliation crosses organizational boundaries.
Research partnerships
On privacy-preserving evidence, reproducibility, and incident review workflows.
OSS collaboration
On adapters, mappings, and independent implementations.
Funding
For security reviews, conformance tooling, documentation, and verification ergonomics.
What we will not do
- Accept funding conditioned on exclusive control of the standard.
- Turn PEAC into a proprietary gatekeeper or hosted requirement.
- Claim impact that cannot be evaluated from shipped artifacts.
What you can expect
- Conservative compatibility practices and explicit stability boundaries.
- Verifiable milestones (fixtures, schemas, bundles, verification reports), not slideware.
- A neutrality posture designed to work alongside existing ecosystems.
Concrete ways to support
Sponsor a security review
Third-party security review of verification behavior.
Sponsor independent implementation
Independent implementation and conformance work in Go, Rust, or other languages.
Sponsor applied research
Research on public-sector auditability and data minimization.
Contribute adapters
Adapters, mappings, and cross-ecosystem test vectors.
Ready to evaluate?
If you want to evaluate PEAC, start with a technical review call grounded in artifacts: policy discovery, receipt verification, evidence bundles, conformance. We can then scope a pilot or research collaboration.
Get in touch