Core Concepts

These pages define Erasure’s vocabulary. Each concept answers: what it is, why it exists, how Erasure uses it, and where to go next.

Platform shell

Concept	One-liner
Organizations & projects	Tenancy, RBAC, entitlements
Publishable keys	SDK credentials (`pk_live_…`)
Operational readiness	Can we execute deletions confidently?

Concept	One-liner
Consent	Draft → publish → SDK → versions
Receipts	Append-only proof of choices

Concept	One-liner
Systems	Connectors to real stores/APIs
Data Maps	Where subject data lives; DELETE vs SKIP
Deletion jobs	Cases, verification, worker jobs
Evidence	Exportable packages of outcomes

Organization
  ├── Projects (Accord: consent, keys, receipts)
  ├── Systems + Data Maps
  └── Rights cases → Jobs → Evidence

Use Accord alone for consent proof, Rights alone for deletion ops (with Systems/maps), or both for the full loop.

What to do next

New to Erasure? Start with Getting Started, then return here when a term is unclear.