Compliance Showcase

GDPR Article 30 Processing Register

Phase 2 runtime contract: every clearance with `data_categories` + `purpose` must match an active register, or it's denied with `processing_no_register_match`. Drafts below are reverse-derived from observed ledger traffic.

0 active
Drafts auto-derived from ledger

No undocumented processing detected

Run the support scenarios in the console to populate this — they tag data_categories on clearance.

Each candidate is a (data_categories, purpose, recipient) cluster from the last 90d. Approve to formalize.
Active registers
Vault unreachable: Vault admin GET moat/processing/registers: HTTP 404 404 page not found