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 · request req-2026-002
Erasure-Completeness Certificate
GDPR Art. 17 erasure request — marketing-signups subject; clean source + Q1 deployment-log redaction completed.
◆ Substrate gap — P7 verifier pending
P7 erasure-completeness verifier pending — substrate gap. Render shows what a future certificate WILL look like.
P7 implementation pending. The substrate primitive is a reverse-direction T6 information-flow walker over the workspace tag graph; the kernel currently exposes T6 in forward mode only (silver-l8 / l12 protocols). Closing this gap is its own workstream — see references.
trigger: First customer pilot requires a real erasure-completeness certificate (D7 in product surface §3) OR a Phase-P substrate workstream lands the reverse-T6 walker. Whichever fires first.
references
docs/g2m/vertical-opportunities/ai-provenance-product-surface-2026-05-02.md §P7docs/g2m/vertical-opportunities/ai-provenance-implementation/IMPLEMENTATION-PLAN-2026-05-04.md §1.B BE5crates/silver-dsar-v2 — the per-subject reverse walker shares the substrate
Request facts
- user_id
- 7728034
- model
- mdl-vertical-B
- filed
- 2026-03-01
- snapshot
- sha:1a2b3c4d5e6f7a8b9c0d1e2f3a4b5c6d
What a real certificate will carry
preview · VERIFIEDThe fields below are synthetic. They mirror the shape the future ErasureProofResult::Verified (or ::Refuted) variant will expose. Not a live computation today.
- target node
- src-marketing
- scope
- user_id=7728034
- workspace snapshot
- sha:1a2b3c4d5e6f7a8b9c0d1e2f3a4b5c6d
- depth of walk
- 3 hops
- artefacts covered
- 3
- surviving references
- 0
- signed by
- sigstore: [email protected]
- attestation hash
- sha256:c1f2e3d4b5a6978876543210fedcba0987654321abcdef0123456789abcdef01
Verified: no path remains from src-marketing to any pinned downstream artefact. Erasure-completeness certificate valid against snapshot 1a2b3c…