WordPress Mutations

Last verified: 2026-07-11

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.

Redacted diff evidence

Eligible file-integrity changes can store encrypted redacted diff evidence outside the raw audit context. WordPress content mutation rows remain metadata-only and show fingerprints instead of plaintext body diffs. Default list, report, REST, CLI, and export views show diff status or hashes, not plaintext diff bodies.

Reveal or export diff evidence only when the support or incident workflow requires it.