Profiles
Profiles are documentation overlays that describe how to use PEAC for specific use cases, regulatory contexts, or integration patterns. A profile constrains and documents existing PEAC structures; it does not add new schema fields.
Profiles are documentary, not runtime-enforced. Schema validation (@peac/schema) enforces field structure; verifyLocal() enforces protocol behavior including type-to-extension enforcement. Profiles document recommended usage patterns on top of those layers.
Pillar Profiles
9 pillar profiles document how to use a specific PEAC extension group for a regulatory, operational, or evidence workflow. Each profile includes schema-vs-profile field tables, non-goals, and strict-mode demonstrations.
| Profile | Extension Group | Description |
|---|---|---|
| Access | org.peacprotocol/access | Access control decisions (resource, action, decision) |
| Identity | org.peacprotocol/identity | Identity attestation and proof references |
| Consent | org.peacprotocol/consent | Consent records (basis, scope, expiry) |
| Privacy | org.peacprotocol/privacy | Privacy and data handling evidence |
| Safety | org.peacprotocol/safety | AI safety and guardrail evidence |
| Compliance | org.peacprotocol/compliance | Regulatory compliance evidence |
| Provenance | org.peacprotocol/provenance | Data and content provenance |
| Attribution | org.peacprotocol/attribution | Content attribution and licensing |
| Purpose | org.peacprotocol/purpose | Purpose limitation and use constraints |
Commerce has a typed extension group (org.peacprotocol/commerce) but no pillar profile because it is an adapter/integration concern covered by payment rail adapters.
Adapter Profiles
Adapter profiles document how to normalize external protocol artifacts into PEAC receipts for a specific integration.
| Profile | Package | Description |
|---|---|---|
| Stripe x402 Machine Payments | @peac/adapter-x402 | Payment evidence for Stripe-backed x402 flows |
Profile Structure
Pillar profiles (10 sections): Overview, extension group reference, schema-vs-profile field table, required fields, optional fields, type-to-extension enforcement behavior, non-goals, strict-mode demonstration, interop-mode behavior, examples.
Adapter profiles (8 sections): Overview, package reference, input/output mapping, normalization rules, verification behavior, conformance vectors, limitations, examples.
Related
- Protocol Scope: 10 verification domains
- Wire Format: 12 typed extension groups
- Registries: Extension group and receipt type registries