WordPress Mutations

WordPress mutation reporting records selected changes to site state that matter for security and support: content status, comments, users, roles, options, plugin/theme/core changes, and related operational signals.

What is recorded

Awthy records safe keys, IDs, statuses, hashes, previews, timestamps, actors, and audit references. It does not store broad editorial analytics, raw post bodies, raw option values, full request payloads, or customer data as mutation evidence.

Select View changes on a site-change row to see what changed. Title, URL slug, and status changes show bounded display-safe before and after values. Content and excerpt changes show before and after fingerprints because Awthy does not retain the post body for this report. Open audit event links to the exact underlying event.

File and plugin metadata

Plugin and file paths are represented as root-relative previews and hashes. Absolute server paths are not shown. Plugin metadata changes should be useful for support without exposing source code or secrets.

Review a change

Open Awthy → Reporting → Site changes.
Narrow the period to the change you are investigating.
Select View changes for the relevant row, then Open audit event if you need its actor and outcome.
Compare the result with the change you expected, such as a scheduled plugin update.

File-integrity rows retain metadata and content hashes locally. WordPress does not store file or generated diff bodies. An unknown or missing fingerprint is not proof that content was unchanged. If the record is incomplete, check the related scan or reporting error before drawing a conclusion.