Add protected interaction evidence and measured debugging phases

This commit is contained in:
Karl committed 2026-10-13 18:04:02 +02:00
1 parent ea448de2d4
commit 244f01630b
42 files changed
+640 -87

No files matched your search

+5
View File
@@ -25,6 +25,11 @@ debugging, optimization and feature work, not merely implemented and left idle.
- Check collector `storedBytes` and exporter failures before long debug sessions.
The local protected receiver has a finite storage budget; missing exports or
rejected writes must not be mistaken for a successful observability proof.
- Check diagnostics `lifetimeFailedExports` as well as the current generation's
`failedExports`; disable/reconfiguration must not erase evidence of earlier
failures within the same browser process. Pre-enrollment startup has no signed
export authorization: use bounded local startup snapshots, and do not infer a
timeout's cause from later successful traces.
- Do not hide failed tests, weaken enforcement, or repeat a protected operation
because telemetry failed. Diagnostic traces are distinct from durable security
audit and encrypted forensic evidence.