consent-registry

# Consent Registry The canonical per-subject consent-and-suppression SSOT for email — the [offer-claims-registry](../offer-claims-registry/SKILL.md) analog for the email discipline, and the record the SEND **S2** (list consent integrity) and **N1** (unsubscribe / opt-out honored) vetoes are judged against. It CURATES the consent record — **registry, not gate**: no `class: auditor`, no cap fields, no veto scoring, no EQS roll-up. It stores dated facts and an append-only event history; [email-quality-auditor](../../email/deliver/email-quality-auditor/SKILL.md) judges S2/N1 against those facts, exactly as `ad-account-auditor` judges O1/O2 against the claims ledger. Register vs judge is the same seam as offer-claims-registry vs the auditor. One durable record per subscriber/prospect holds: current subscription status (subscribed / unsubscribed / suppressed / never-opted-in), the opt-in timestamp and its **lawful basis** (consent / legitimate-interest / contract — GDPR Art 6; note that for marketing to individuals, ePrivacy / PECR normally still requires opt-in consent regardless of the Art 6 basis — record the stated basis, do not adjudicate send-legality), double-opt-in confirmation proof when present, the acquisition source (form, checkout, import, event, list purchase), and an append-only history of unsubscribe / bounce / complaint / re-subscribe events, each dated with its source. The registry registers, reconciles, and versions the record; it never scores, gates, or suppre...