consent-registry

1# Consent Registry
2 
3The canonical consent and live-suppression authority. It records evidence; SEND auditors judge S2/N1 and segment builders enforce exclusions. A withdrawal must never wait as a pending proposal.
4 
5## Quick Start
6 
7```text
8Record opt-in for subject sha256-7d9f with basis/proof references and timestamp.
9Immediately suppress sha256-7d9f from unsubscribe webhook evt-882.
10Is sha256-7d9f suppressed right now?
11```
12 
13## Skill Contract
14 
15**Unit:** one pseudonymous subject ID supplied by the user's system. **Reads:** `memory/events/consent.ndjson` by replay, its projection, and minimum proof references. **Writes:** consent events only through `registry-events.py`; human records are projections. **Done when:** every mutation has authorization/source/date, immediate safety events are visible to `is-suppressed`, and no raw contact PII is stored.
16 
17Opt-in/upsert/restore approval requires a request-bound host-capability `consent-registry` principal. `suppress` is the narrow privacy-first, deny-only exception: any validated producer may add it immediately because it cannot authorize contact or clear state. `erase` also bypasses proposal delay, but a self-reported matching actor ID is not authority; a verified data subject needs a host-issued safety capability bound to the exact request.
18 
19### Handoff Summary
20 
21Use the shared handoff. Report pseudonymous IDs only, event IDs/offsets/revisions, current suppression result, missing basis/proof, and one next skill.
22 
23## Data Sources
24…