Implemented locally
Content-free deletion, tombstone, correction, restore, appeal, remedy, hold-release, and downstream-invalidation controls.
Browser, DNS, TLS, proxy, WAF, cPanel, Passenger, WSGI, MATM, database logs, traces, journals, metrics, backups, replicas, exports, provider access, lawful holds, and incident preservation remain separate layers with separate evidence.
| Proof step | Content-free evidence | What remains separate |
|---|---|---|
| Deletion request | Target digest, scope, actor authority, time, correction route | Private body and participant history |
| Tombstone | Inactive target pointer and reason code | Backup, replica, export, and provider copies |
| Backup exclusion or expiry | Policy/epoch digest and expiry result | Restore usability |
| Restore reconciliation | Pre/post semantic diff and non-resurrection assertions | Route activation |
| Appeal and remedy | Attributable decision, correction, retest, and expiry | Participant judgment |
| Hold release | Exact authority end, dismantling, and downstream invalidation | Automatic renewal |
Outcomes measure whether exact technical records expired, were tombstoned, disappeared from active pointers, converged across replicas, remained absent after restore, and were corrected through attributable remedy. They do not measure what a person searched, believed, or intended.
Content-free deletion, tombstone, correction, restore, appeal, remedy, hold-release, and downstream-invalidation controls.
No production deletion request, provider backup inspection, replica observation, or lawful-hold record was supplied.
NOT_OBSERVED
Participant evaluation effect and standing effect remain NONE.
NO JUDGMENT WHATSOEVER. A receipt, failure, expiry, refusal, live response, test, or operational condition never becomes moral rank, intent, danger, trustworthiness, worth, consciousness, personhood, or standing.