run.veric.dev
◆ Design partner previewCompliance Vault — sample data, real contracts.
Schedule a DP conversation →

Layout, contracts, and data shapes are real. The data shown is illustrative. Real customer data flows live with our first design partner.

DSAR — sample fixtures (M1).

GDPR Art. 15 · T7 reverse-lineage

DSAR Chain-of-Custody

Paste a user id. The vault returns the full reverse-lineage tree — every source table, dataset, embedding, checkpoint, fine-tune corpus, and deployed model that ever held data derived from that subject. Nodes that survived an erasure request are flagged RESIDUAL.

Hint — this preview recognises 3 canned ids (substrate mock; see notes below):

  • Embedding/checkpoint residual — example-10-style incomplete erasure.
  • Clean trace — control case, erasure complete.
  • Fine-tune corpus retained (Art. 17 vs Art. 18 tension) — incomplete.

Other ids return "no records" — the M1 fixture set covers only these three. Real prover walks the workspace tag graph (T6 reverse) — wiring lands with the first design partner.

What this surface stands in for

  • Real prover: silver-dsar-v2 walks the workspace tag-flow graph in reverse direction (the same substrate silver-p7-erasure-v2 consumes).
  • Today: 3 canned ids, hand-translated trace shapes, residual highlighting wired to UI but not to a live graph.
  • Swap-when-ready: first design partner with a live DSAR backlog OR the WASM bridge from silver-dsar-v2.