Systems
Connectors to real data stores and APIs for Rights fulfillment.
Systems
What it is
A System is a configured connector: non-secret config, encrypted secrets, health, enablement, and execution behaviour for Rights jobs. In the console, the product name is Systems; engineering docs may say connectors.
Why it exists
Deletion must touch real systems, not spreadsheets. Systems are the controlled outbound edge of Rights fulfillment.
Catalog (definition identity)
Identity is a catalog definitionId. Multiple Systems of the same definition are allowed; plan entitlements cap total count.
| Product type | definitionId | Role |
|---|---|---|
| PostgreSQL | postgres | Parameterized DELETE via Data Map plans |
| MySQL | mysql | Same model with MySQL dialect |
| MongoDB | mongodb | Document delete via mapped collections |
| HTTP API | http_api | HTTP call to customer delete endpoint |
| Webhook | webhook | Signed outbound notify for delete |
| OAuth sandbox | oauth_sandbox | Dev/demo OAuth install + optional notify |
How Systems participate in deletion
Operator configures System (+ secrets encrypted)
│
▼ Health check
HEALTHY / DEGRADED / UNHEALTHY / UNKNOWN / DISABLED
│
▼ Data Map (required for SQL / map-backed modules)
entities + identifier bindings
│
▼ Rights job (worker)
module executes DELETE_SUBJECT or NOTIFY
│
▼ Timeline + EvidenceSQL modules do not invent tables. They use Data Map entities. HTTP/Webhook execute from connector config (maps still matter for org readiness where documented).
Secrets & safety
- Secrets: AES-256-GCM (
CONNECTOR_SECRETS_KEY); lists do not return raw secrets - Rotate via Owner-capable rotate endpoints
- SQL: identifier allowlists + parameterized values; production TLS required (unless documented private-network insecure flag)
- HTTP: SSRF checks; unsafe redirects not followed
- Worker must reach customer networks you configure. Control egress
Health statuses
| Status | Meaning |
|---|---|
| HEALTHY | Recent check succeeded |
| DEGRADED | Slow or partial issues |
| UNHEALTHY | Check failed |
| UNKNOWN | Not checked yet |
| DISABLED | System off |
Lifecycle states (e.g. READY) may gate fulfillment when lifecycle enforcement is enabled in a deploy.