Core Concepts
Data Maps
Entities, identifiers, DELETE vs SKIP, discovery, graph, and preview.
Data Maps
Source: app_docs/guide/data-maps.md, app_docs/guide/faq.md.
What it is
A per-connector inventory of entities (usually tables), identifier mappings, and actions: DELETE or SKIP.
Why it exists
You cannot delete what you cannot find. SQL connectors do not guess tables. Without a map, start readiness fails for SQL systems.
How it works
Connect SQL System
│
▼ Discover schema (information_schema, capped)
Snapshot on Data Map
│
▼ Suggestions (heuristics + confidence)
│
▼ Accept / ignore / edit entities
Data Map entities
sourceName · identifiers · DELETE | SKIP
│
▼ Validate + readiness
Operational Graph · Execution Preview (COUNT only)
│
▼
Rights delete job uses plans| Concept | Detail |
|---|---|
| Entity | One table (or source) with identifier mappings |
| Identifier | Subject field (email, externalId, …) → column |
| DELETE | Included in execution plans |
| SKIP | Documented, not deleted (e.g. invoices kept) |
| Ignored sources | Tables excluded from mapping pressure |
| Coverage / drift | Discovered vs mapped; snapshot changes over time |
| Discovery limit | Large catalogs capped (product: thousands of tables max per discovery) |
Graph
Operational relationship graph: systems, entities, FK edges, ignore/unmapped samples.
Not a full enterprise ERD.
Execution preview
Dry-run: COUNT matching rows per entity for a sample subject.
Never deletes.
HTTP and Webhook systems run from connector config without a SQL map.
How to implement
- Systems → select SQL connector → Data Map.
- Discover.
- Accept high-confidence suggestions or add entities.
- Fix validation errors (delete without identifiers is invalid).
- Confirm readiness green for that system.
- Use Preview with a test subject before first start.
Best practices
| Do | Don’t |
|---|---|
| Map only personal-data tables | Map every table “just in case” |
| Prefer stable identifiers (email, external id) | Free-text names as keys |
| Re-discover after migrations | Assume snapshot forever |
| Use SKIP for legal retention tables | Silent partial deletes without documentation |