How markdown and JSON exports, local history, and evidence preservation work in the current desktop product.
- Markdown and JSON export intent
- Local history and drift tracking
- Diagnostics boundaries
- Why local persistence matters
Applies to
WindowsmacOSLinux
Covers
ExportsHistoryAnalyticsFindings
Exports and history
Export formats
The current product supports:
- markdown exports
- JSON exports
What history is for
Use scan history when you need to know:
- whether the same issue existed before
- whether posture improved after remediation
- whether a finding is new or recurring
Local-first evidence handling
History, findings, annotations, exports, and workspace state are persisted locally.
Diagnostics boundaries
Diagnostics should be explicit, operator-triggered, and redacted. They should never include raw tokens, auth headers, or other credential material.