AIPREF Integration
Map the IETF AIPREF vocabulary and the Content-Usage header to PEAC canonical control purposes. The mapping reads AI content-use preference signals and converts them into the purpose vocabulary PEAC records carry, so a stated preference becomes verifiable evidence.
Package: @peac/mappings-aipref (source-only)
Source-only. @peac/mappings-aipref is not published to npm. Build it from the repository at packages/mappings/aipref. There is no npm install path; this page documents the reference mapping.
What It Does
AIPREF expresses AI content-use preferences through a vocabulary and the Content-Usage header. The mapping parses those signals and converts them to and from PEAC canonical control purposes.
1. Parse the Content-Usage header
parseContentUsageHeader reads the AIPREF Content-Usage header into structured keys.
2. Map AIPREF keys to purposes
contentUsageToCanonicalPurposes and aiprefKeyToCanonicalPurpose convert AIPREF keys to PEAC control purposes; canonicalPurposesToContentUsage maps the other direction.
3. Record preference evidence
The mapped purposes feed PEAC consent records, which verify offline with the issuer's public key.
Standard and extension keys
The mapping recognizes AIPREF standard keys and registered extension keys (AIPREF_STANDARD_KEYS, AIPREF_EXTENSION_KEYS), with helpers isAiprefStandardKey and isAiprefKnownKey for membership checks. The vocabulary version is pinned via AIPREF_VOCAB_VERSION.
Semantic Boundary
PEAC records AI content-use preferences as evidence. It does not enforce those preferences, crawl content, or police AI training. An AIPREF-derived record proves which preferences were stated, not that they were followed.