Preview a temporary response safely

1. From an eligible request observation, choose Preview temporary policy and a finite duration. If the preview is unavailable, review the stated evidence or permission requirement.
2. Read the exact site, path or reviewed source conditions, GET/HEAD methods, expiry and matcher examples. Inspect optional exact-path exceptions when offered.
3. Keep OS-level recovery access available. Observation-only is the initial choice and never denies a request.
4. Only after reviewing the effect, choose active mode and acknowledge the scope and recovery procedure. Activation also enables local response for valid existing policies.
5. Use Response → Manual policies to inspect the current mode and retained policies. Choose Revoke for a policy you no longer need.

A server operator can run wp logged-ai response disable --url=YOUR_SITE, or set define('LOGGED_AI_DISABLE_RESPONSE', true); before WordPress loads. There is no public recovery URL or bypass cookie.

Policy expiry is checked on eligible requests without waiting for cron. Exact-source targeting can affect shared-network users and ordinary login, checkout or API reads. Exceptions apply only to the selected policy; they do not grant WordPress access or override other policies.

This is a temporary WordPress-layer control. It does not replace an upstream firewall, and earlier code may already have run. Ambiguous or encoded input can remain observation-only.