Evidence
Export evidence for review
Evidence is local-first, which means getting it to a reviewer is a deliberate act rather than something that happens continuously in the background.
- Activity & evidence
- 4 min read
Export before these
- Shortening retention. The window you drop is gone.
- Restoring a database backup. You will get an earlier chain, not this one.
- Uninstalling with data removal opted in.
- Handing a site to a new owner or agency.
- Any incident you may need to explain later. Export while the record is complete, not after you have started fixing things.
What an export contains
- The decision records for the range you selected.
- Redaction applied, so sensitive input does not leave the site in the clear.
- Request fingerprints, so records can still be matched to approvals and executions.
- The chain information needed to verify the exported range.
Handling the file
An export is still operational data about your site. Treat it accordingly: send it over a channel you would use for other sensitive material, keep it only as long as the review needs it, and do not paste it into a public forum thread.
A redacted export plus the request context is usually everything a support conversation needs. Never send credentials alongside it — see what to include.
Who reads it
Records are written in operational language, so an export is readable by someone who did not build the integration — an auditor, a client, a colleague picking up an incident. That is deliberate: evidence only counts if the person who needs it can read it.
Activity & evidence
Keep the boundary while you fix the problem.
A good fix restores intended behaviour without creating a second path around WordPress or the governed request lifecycle.