Start with the symptom
Users receive AI results and the provider records usage, yet no corresponding request appears in the WordPress control layer.
Start with the symptom for “The site is using AI, but the protection dashboard shows no activity”: Users receive AI results and the provider records usage, yet no corresponding request appears in the WordPress control layer. You must identify the real request path before a limit, webhook, or retry policy can be trusted.
List competing causes for “The site is using AI, but the protection dashboard shows no activity”: A safe rollout needs evidence, reversible changes, and a recovery path that does not erase the incident.
List competing causes
Collect discriminating evidence for this case: Trace the request from plugin to provider, identify direct or unsupported paths, and describe uncovered scope before claiming complete protection.
Test in the safest order for “The site is using AI, but the protection dashboard shows no activity”: identify the evidence that would make this proposed action unsafe—Trace the request from plugin to provider, identify direct or unsupported paths, and describe uncovered scope before claiming complete protection.
- Evidence 2 for “The site is using AI, but the protection dashboard shows no activity”: actual request path
- Evidence 3 for “The site is using AI, but the protection dashboard shows no activity”: production-only integrations
- Evidence 4 for “The site is using AI, but the protection dashboard shows no activity”: alert delivery
- Evidence 1 for “The site is using AI, but the protection dashboard shows no activity”: tested rollback
Collect discriminating evidence
Record the finding for this exact problem: the acceptable end state must resolve the original condition—Users receive AI results and the provider records usage, yet no corresponding request appears in the WordPress control layer.
evidence-led diagnostic table decision for “The site is using AI, but the protection dashboard shows no activity”: Trace the request from plugin to provider, identify direct or unsupported paths, and describe uncovered scope before claiming complete protection.
Test in the safest order
Build the evidence-led diagnostic table for “The site is using AI, but the protection dashboard shows no activity.” List at least two competing causes. For each, name one observation that would support it and one that would rule it out. Test the least disruptive distinction first.
Record the finding
Use the evidence-led diagnostic table from “The site is using AI, but the protection dashboard shows no activity” on a real first installation. Download AI Cost Circuit Breaker for free, begin in Monitoring, and move to enforcement only after the expected signals and rollback are verified.