1. Find the original and its dates
Record who published the claim, when it was published and when the event reportedly happened. A recently shared old report is not a new incident. Check whether the image, location and source are actually connected to the described event.
For threatening messages, NIST’s phishing guidance supports verifying through an independent known channel. Do not use a contact detail embedded in the alarming message as the only confirmation.
Basis: NIST — Phishing guidance
2. Separate evidence from explanation
An original fictional example is “the utility’s official notice reports a local outage at 14:00.” A separate claim might be “AI caused it.” The first statement does not establish the second. Leave the cause unknown unless credible evidence supports it.
Rogue AI’s robot and arm-wrestling artwork is a generated fictional illustration. It is not a documentary image, evidence of consciousness or proof that a plant is controlled by an AI attacker. Treat other striking imagery with the same source questions.
3. Choose a proportionate next task
If the verified problem is a local outage, use the household outage plan and official notices. If it is an unfamiliar account alert, use the provider’s recovery process. Do not turn an unverified claim into instructions to isolate your only communication method.
Infrastructure reference records may show historical coordinates, categories or reported capacity. They do not report live operational health, grant site access or identify a safe destination. Record the next check time and keep uncertainty visible when discussing the claim in the shared community.
ORIGINAL WORKSHEET
Claim-check worksheet
The first row is a fictional example. No live incident is asserted.
| Claim / observation | Source + event date | Established / unknown | Next practical task |
|---|---|---|---|
| Example: local outage reported | Known utility notice; sample 14:00 | Outage reported; cause unknown | Household outage plan |
| Claim to check | ________ | ________ | ________ |
| Image or map record | ________ | ________ | ________ |
| Next review | Time: ________ | Remaining uncertainty: ________ | ________ |
Save it. Then test it.
One reading file, 5.2 KB. No maps, external images, scripts or personal records. External source links still need internet.
Checks remain only during this visit. They do not certify readiness, safe equipment or successful delivery. The saved worksheet has blank prompts.
Save on this computer, or copy the completed download to a compatible USB drive. Reopen from that location for the offline test.
READ THE BASIS
Sources, dates and limits
A verification worksheet, not live intelligence or an AI-attack detector. No speculative consciousness or infrastructure-control scenario is presented as an established event.
Source links checked 2026-10-11. The organization and sample worksheets are original editorial work. A source check is not a qualified review or a physical-device test. Downloaded files are dated snapshots; use current local guidance and equipment instructions.
- NIST — Phishing guidanceUnited States security awareness
CONTINUE WHEN IT IS USEFUL
Use the matching Prepper task
Reference locations are not live status, access permission or an emergency-routing recommendation.
Read the dated infrastructure-reference explanation →The installed product is Prepper. AI Rogue is a section inside it. An article or website release does not verify a public store listing, an update received by your phone, live LoRa messaging or an OS lock.