Error Division Radar
Error Division Radar

Error Division Radar

0/5 (0 ratings) — active installs Updated Nov 8, 2026
Radar Overview: system-state intelligence, operational signals and Black Box capsules.

Radar Overview: system-state intelligence, operational signals and Black Box capsules.

Error Division Radar records plugin, theme, core and privileged-user changes, correlates them with system fingerprints and preserves incident snapshots in the WordPress database. It includes runtime fatal capture after the plugin has loaded, signal filtering, repeat condensation, JSON export and a printable system dossier. Version 1.9.6 also includes a read-only Performance Intelligence screen and a non-destructive Rescue Readiness Check. Browser timing comparisons are not PHP-only or external visitor benchmarks.

Database capsule checksums detect inconsistent payloads. SHA-256 checksums are not keyed authentication and do not establish evidence authenticity against an attacker who can change the database.

On standalone WordPress installations, Radar includes assisted recovery inside the WordPress administrator dashboard. On Multisite, observation and database capsules work per website, while Rescue and plugin isolation are disabled. It lists plugins paused by WordPress in the current Recovery Mode session and permits administrator-confirmed deactivation using WordPress APIs. Known active plugin dependencies block this action. Themes are managed through the WordPress Themes screen.

A manual homepage response check sends a cookie-free request to the configured site URL. It does not send data to Error Division. HTTP success is not proof of complete recovery. No external service, separate host plugin or paid account is required.

Radar does not provide an independent recovery login, create executable files, install MU plugins, rename plugin directories or download external executable code.

This release uses separate tables, settings and hooks. It does not migrate or delete evidence from ED Change Radar Review25. Do not delete the old plugin or its vault as a migration shortcut.

Privacy

Data remains in the local WordPress database. Administrative user IDs, component names, relative error paths and message fingerprints can be recorded. Complete error messages are opt-in. The Core does not record visitor tracking, transmit telemetry or store Recovery credentials.