Layout, contracts, and data shapes are real. The data shown is illustrative. Real customer data flows live with our first design partner.
T7 · GDPR Art. 17
Erasure-Completeness
One row per Article-17 deletion request. The future certificate either positively proves no path remains from the target to any pinned downstream artefact, or names the residual reachability path. Today the prover silver-p7-erasure-v2::StubProver always returns Stub — see per-request pages for the substrate-gap banner.
- req-2026-001user_id 4192813 · model mdl-foundation-Afiled 2026-04-15stub · preview REFUTED
GDPR Art. 17 erasure request — subject withdrew consent; FAISS index + foundation-model-A weights flagged as residual.
- req-2026-002user_id 7728034 · model mdl-vertical-Bfiled 2026-03-01stub · preview VERIFIED
GDPR Art. 17 erasure request — marketing-signups subject; clean source + Q1 deployment-log redaction completed.
- req-2026-003user_id 9981255 · model mdl-fine-tune-Cfiled 2026-04-22stub · preview REFUTED
GDPR Art. 17 erasure request — support-conversations subject; Art. 17 vs Art. 18 tension on retention-pinned fine-tune corpus.
- req-2026-004user_id 4192813 · model mdl-fine-tune-Cfiled 2026-04-28stub · preview REFUTED
Cross-model follow-up: same subject as req-2026-001, scoped to fine-tune-C deployment lineage.
The prover stub returns Stub for every call — see any per-request page for the substrate-gap explainer.