PEAC Protocol

Problem

Automated interactions increasingly cross organizational boundaries, but evidence does not. Internal logs are not portable proof, and disputes devolve into “trust my dashboard.”

What PEAC standardizes

• -A discoverable policy surface (/.well-known/peac.txt)
• -A signed receipt format attached to responses (portable proof)
• -Deterministic verification using portable artifacts and public keys
• -Evidence bundles for audit/dispute workflows
• -Conformance fixtures for independent implementations

What PEAC does not standardize

Identity systems, payment rails, observability platforms, or agent orchestration.

Current status

• -Wire format and discovery paths are stable under a pre-1.0 compatibility policy
• -Reference libraries and adapters may evolve; conformance fixtures and changelogs document behavior

Why institutions care

• -Vendor-neutral auditability
• -Incident review and dispute workflows
• -Reproducibility for research and evaluation
• -Evidence of consent/terms application
• -Rail-neutral settlement evidence for evolving ecosystems

What support accelerates

Security reviews, conformance tooling, documentation, and real pilots where cross-org verification is required.

Governance commitments

Neutrality, non-capture, multi-implementation expectation, and verification-first posture.

Artifacts you can inspect today