Consent Review — the human gate on the consent ledger
Sign in with a staff account to review consent evidence.
The consent ledger isn’t applied on this database — apply db/2026-07-29_1401_consent-ledger-staged.sql, then reload.
Mining is dark. config.consent_mine is off, so a scan reads nothing and writes nothing. Reviewing evidence already on file still works — flipping the switch is Mike’s act.
Consent Ledger
The contract: a detection is usable only when it is granted AND reviewed AND accepted — and never over a DNC or suppression hit. Consent is necessary, never sufficient: nothing on this page dials, texts, or emails anyone.
Review queue
The ledger exposes no list door (by design its table is RLS deny-all) — evidence is reached by subject through mcp_consent_for, which returns the ruling row per channel with its evidence_id. Load a subject to review its detections. Nothing you type here is stored by this page.
Matching is exact on subject_ref or phone as the scanner stored them — try the number formatted the way the call rail records it.
Consent lookup
The question the campaign rail asks: do we have consent for this person, on which channels, and why?
Pure MLS Tech · Acquisto Real Estate · Consent Review over mcp_consent_status / mcp_consent_for / mcp_consent_review / mcp_consent_scan (db/2026-07-29_1401, applied live) · evidence only — zero outbound ·