Wayne County tornado seek shelter now
AI-generated · every claim is source-linkedIU Police @IUpolice issued a IU East seek-shelter tornado warning.
- Alerts
- 1
- Response
- —
- Killed
- —
- Injured
- —
Alert Sequence
1 message in sequence · 1 verified verbatim
Confirmed wording is transcribed character-for-character from a primary source. Use Verify this quote under each message to open that source in a new tab and compare the text yourself.
How the first alert is built
To check this alert, SuperGrok Heavy 4.5 (an AI) read it in full 25 separate times, independently. Each read decided whether the message answers each of the six questions and gave a short reason. A final reviewer then weighed all 25 and wrote the plain-English verdict you see when you open a row. The score (for example 22/25) is how many reads agreed; the 25 individual reads are tucked underneath if you want to check them.
IUE Alert:Wayne County: SEEK SHELTER NOW. Tornado Warning issued August 1 at 7:31PM EDT until August 1 at 8:00PM EDT by NWS Wilmington OH
Sourcepresent25/25
Final assessment
Majority 25/25 present. Institutional branding appears via "Alert:", which marks the sender.
Who is sending the alert and who is responding. People act faster on a message from a clearly identifiable, credible sender, such as a named department, the police, or a branded alert system, than on an anonymous notice. A branded signature counts.
See all 25 individual reads
- present: Institutional branding appears via "Alert:", which marks the sender.
- present: The notice identifies who is speaking through "Alert:".
- present: Source is present because "Alert:" names the issuing campus or alert brand.
- present: A campus or alert signature ("Alert:") supplies the authority line.
- present: Sender identity is clear from the wording "Alert:".
- present: The alert tags an official issuer with "Alert:".
- present: Who is sending this is stated through "Alert:".
- present: Branded language "Alert:" functions as the source element.
- present: Campus naming in "Alert:" tells recipients the origin of the message.
- present: An official voice is established by "Alert:".
- present: The opening or body includes "Alert:" as institutional source.
- present: "Alert:" is enough to code source present under the branding rule.
- present: Recipients can tell the sender from "Alert:".
- present: Source scores present: "Alert:" is an authority marker.
- present: The university or college is referenced as "Alert:".
- present: Alert-system or school labeling ("Alert:") covers source.
- present: Issuing body is identifiable from "Alert:".
- present: "Alert:" operates as a branded signature for source.
- present: The text attributes the message via "Alert:".
- present: Source present: campus authority language "Alert:".
- present: Readers see "Alert:" and know which campus is speaking.
- present: Official sender cue "Alert:" is explicit in the text.
- present: Source is coded yes based on "Alert:".
- present: The phrase "Alert:" identifies the responding institution.
- present: Authority is named through the fragment "Alert:".
Hazardpresent25/25
Final assessment
Majority 25/25 present. Hazard is specific: the text names "Tornado Warning".
What the threat actually is. A complete warning names the specific danger, such as a shooter, a fire, a tornado, or a gas leak, rather than a vague emergency, because people decide what to do based on what they are facing.
See all 25 individual reads
- present: Hazard is specific: the text names "Tornado Warning".
- present: A concrete threat appears as "Tornado Warning".
- present: The what of the emergency is "Tornado Warning", not a vague incident label.
- present: "Tornado Warning" satisfies hazard by naming the condition or threat.
- present: Readers learn the hazard type from "Tornado Warning".
- present: Hazard present via the explicit phrase "Tornado Warning".
- present: The threat is particularized as "Tornado Warning".
- present: Coding H=1 because "Tornado Warning" is a named hazard.
- present: Specific danger language: "Tornado Warning".
- present: The alert states the problem as "Tornado Warning".
- present: Hazard element met by "Tornado Warning".
- present: "Tornado Warning" is more than a generic emergency word.
- present: Threat identity is clear from "Tornado Warning".
- present: The message pins the hazard to "Tornado Warning".
- present: Named condition "Tornado Warning" counts as hazard.
- present: H is present: "Tornado Warning" tells what is wrong.
- present: Concrete hazard wording includes "Tornado Warning".
- present: The incident type is given as "Tornado Warning".
- present: "Tornado Warning" is the stated threat or weather/system hazard.
- present: Hazard codes yes on "Tornado Warning".
- present: Specifics beat generics here: "Tornado Warning".
- present: The text's hazard signal is "Tornado Warning".
- present: What happened is labeled "Tornado Warning".
- present: Hazard present with the phrase "Tornado Warning".
- present: Threat naming succeeds through "Tornado Warning".
Locationabsent0/25
Final assessment
Majority 25/25 absent. No building, campus, street, or area is named.
Where the threat is. Saying whether danger is in a specific building, a part of campus, or area-wide lets people judge their own proximity and choose a safe direction. Without a where, a warning is hard to act on precisely.
See all 25 individual reads
- absent: No building, campus, street, or area is named.
- absent: Location is absent: the text never says where.
- absent: There is no place cue for recipients to orient to.
- absent: L=0 because spatial reference is missing.
- absent: The alert omits campus or site detail.
- absent: Where this applies is never stated.
- absent: No location language appears in the body.
- absent: Place naming fails on this wording.
- absent: Readers get no geographic anchor.
- absent: Location element is not satisfied.
- absent: Without a place name, L is zero.
- absent: The message leaves location unspecified.
- absent: No hall, campus, or area reference is present.
- absent: Spatial information is missing entirely.
- absent: L fails the place-naming test.
- absent: Affected site is not identified.
- absent: Location codes absent here.
- absent: The text is silent on where.
- absent: No campus geography is given.
- absent: Place element cannot be coded present.
- absent: Where-cue is blank in this alert.
- absent: Location not established by the wording.
- absent: Site detail is omitted.
- absent: No area or building reference exists.
- absent: L is absent on a pure no-place text.
Guidancepresent25/25
Final assessment
Majority 25/25 present. Guidance is the instruction "SEEK SHELTER".
The protective action to take. A clear, specific instruction, such as shelter in place, evacuate, avoid the area, or run-hide-fight, drives faster and more correct protective behavior than describing the threat alone.
See all 25 individual reads
- present: Guidance is the instruction "SEEK SHELTER".
- present: Protective action appears as "SEEK SHELTER".
- present: Recipients are told to act via "SEEK SHELTER".
- present: "SEEK SHELTER" is a direct what-to-do line.
- present: G=1 because "SEEK SHELTER" instructs the audience.
- present: The alert directs action with "SEEK SHELTER".
- present: Guidance present: "SEEK SHELTER".
- present: A clear instruction is "SEEK SHELTER".
- present: What to do is stated as "SEEK SHELTER".
- present: "SEEK SHELTER" counts as protective guidance.
- present: Action language "SEEK SHELTER" meets guidance.
- present: The message tells people "SEEK SHELTER".
- present: Guidance codes yes on "SEEK SHELTER".
- present: Operational direction: "SEEK SHELTER".
- present: Instructional content includes "SEEK SHELTER".
- present: "SEEK SHELTER" is audience-facing guidance.
- present: G is present via the cue "SEEK SHELTER".
- present: Protective or operational order "SEEK SHELTER" is explicit.
- present: The text's guidance signal is "SEEK SHELTER".
- present: Recipients receive the directive "SEEK SHELTER".
- present: What-to-do element satisfied by "SEEK SHELTER".
- present: "SEEK SHELTER" tells the public how to respond or operate.
- present: Guidance met through "SEEK SHELTER".
- present: Action instruction present: "SEEK SHELTER".
- present: The alert's order to the audience is "SEEK SHELTER".
Timepresent25/25
Final assessment
Majority 25/25 present. Time is marked by "7:31PM".
When the message applies. A timestamp, the word now or immediately, or a phrase like until further notice tells the reader whether the danger is current and how quickly to act.
See all 25 individual reads
- present: Time is marked by "7:31PM".
- present: A temporal cue appears as "7:31PM".
- present: When is answered with "7:31PM".
- present: "7:31PM" supplies timing or recency.
- present: T=1 because "7:31PM" is a time reference.
- present: Clock or calendar language: "7:31PM".
- present: The alert times the event with "7:31PM".
- present: Temporal detail "7:31PM" is present.
- present: Time element met by "7:31PM".
- present: Recipients see timing via "7:31PM".
- present: "7:31PM" counts as the time cue.
- present: When-language includes "7:31PM".
- present: T codes yes on "7:31PM".
- present: A schedule or day marker "7:31PM" appears.
- present: Timing is explicit: "7:31PM".
- present: The text anchors time with "7:31PM".
- present: "7:31PM" is enough for the time element.
- present: Recency or clock cue "7:31PM" is stated.
- present: T is present via "7:31PM".
- present: Date or hour language "7:31PM" supports T=1.
- present: Temporal reference: "7:31PM".
- present: The when signal is "7:31PM".
- present: Time present through "7:31PM".
- present: "7:31PM" tells recipients the relevant when.
- present: Schedule wording "7:31PM" meets time.
Impactabsent0/25
Final assessment
Majority 25/25 absent. No consequence or severity language appears beyond naming a hazard.
What the hazard could do to the people in its path. Beyond naming the threat, a complete warning conveys its potential consequences or severity, such as that a tornado can level buildings or that a leak could be explosive, so recipients grasp how much danger they are in. Research on warning message content finds that a concrete impact statement helps people personalize their risk and act sooner.
See all 25 individual reads
- absent: No consequence or severity language appears beyond naming a hazard.
- absent: Impact is absent: the text does not say what the threat could do.
- absent: Nothing states danger level, injuries, or disruptive effect.
- absent: I=0 because severity or harm is not conveyed.
- absent: Hazard may be named, but impact language is missing.
- absent: The alert omits consequence wording.
- absent: Impact fails the harm-or-severity test.
- absent: Readers are not told stakes or effects.
- absent: No life-safety or operational impact phrase is present.
- absent: Impact element codes absent.
- absent: Without consequence language, I is zero.
- absent: Severity is left unstated.
- absent: The text stops short of impact.
- absent: Harm potential is not described.
- absent: I fails on bare description without effects.
- absent: No dangerous/closed/injury-style impact cue appears.
- absent: Impact not established by the wording.
- absent: Consequence detail is missing.
- absent: The message lacks severity framing.
- absent: I is absent under the impact rule.
- absent: Stakes for people or property are not stated.
- absent: No disruption or harm language is included.
- absent: Impact cannot be coded present here.
- absent: Effect-on-campus language is omitted.
- absent: Severity/consequence element fails.
Coded by SuperGrok Heavy 4.5
Systematic AI judgments with visible reasoning, not human-validated codings.
Background
Key Findings
Sources
Every claim on this page is meant to be checkable. Open the links below (and the Verify this quote control under each confirmed alert) to read the original university, news, or archive page yourself. Hostnames are shown so you can see where you are going; archived copies survive when live pages move or disappear. See also our methodology.
- Social
Campus Alert Archive. "Indiana University: Wayne County tornado seek shelter now." Incident of August 1, 2026. Added August 2026. https://campusalertarchive.com/case/indiana-university-east-wayne-county-tornado-warning-2026-08-01/
Alert text quoted on this page remains the work of the issuing institution; the archive is a secondary source.