Foggy Bottom and MVC shelter for tornado warning

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.

• Sourcepresent25/25

  Final assessment

  Majority 25/25 present. Institutional branding appears via "GWAlert: Emergency, Foggy Bottom & MVC…", 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

  1. present: Institutional branding appears via "GWAlert: Emergency, Foggy Bottom & MVC…", which marks the sender.
  2. present: The notice identifies who is speaking through "GWAlert: Emergency, Foggy Bottom & MVC…".
  3. present: Source is present because "GWAlert: Emergency, Foggy Bottom & MVC…" names the issuing campus or alert brand.
  4. present: A campus or alert signature ("GWAlert: Emergency, Foggy Bottom & MVC…") supplies the authority line.
  5. present: Sender identity is clear from the wording "GWAlert: Emergency, Foggy Bottom & MVC…".
  6. present: The alert tags an official issuer with "GWAlert: Emergency, Foggy Bottom & MVC…".
  7. present: Who is sending this is stated through "GWAlert: Emergency, Foggy Bottom & MVC…".
  8. present: Branded language "GWAlert: Emergency, Foggy Bottom & MVC…" functions as the source element.
  9. present: Campus naming in "GWAlert: Emergency, Foggy Bottom & MVC…" tells recipients the origin of the message.
  10. present: An official voice is established by "GWAlert: Emergency, Foggy Bottom & MVC…".
  11. present: The opening or body includes "GWAlert: Emergency, Foggy Bottom & MVC…" as institutional source.
  12. present: "GWAlert: Emergency, Foggy Bottom & MVC…" is enough to code source present under the branding rule.
  13. present: Recipients can tell the sender from "GWAlert: Emergency, Foggy Bottom & MVC…".
  14. present: Source scores present: "GWAlert: Emergency, Foggy Bottom & MVC…" is an authority marker.
  15. present: The university or college is referenced as "GWAlert: Emergency, Foggy Bottom & MVC…".
  16. present: Alert-system or school labeling ("GWAlert: Emergency, Foggy Bottom & MVC…") covers source.
  17. present: Issuing body is identifiable from "GWAlert: Emergency, Foggy Bottom & MVC…".
  18. present: "GWAlert: Emergency, Foggy Bottom & MVC…" operates as a branded signature for source.
  19. present: The text attributes the message via "GWAlert: Emergency, Foggy Bottom & MVC…".
  20. present: Source present: campus authority language "GWAlert: Emergency, Foggy Bottom & MVC…".
  21. present: Readers see "GWAlert: Emergency, Foggy Bottom & MVC…" and know which campus is speaking.
  22. present: Official sender cue "GWAlert: Emergency, Foggy Bottom & MVC…" is explicit in the text.
  23. present: Source is coded yes based on "GWAlert: Emergency, Foggy Bottom & MVC…".
  24. present: The phrase "GWAlert: Emergency, Foggy Bottom & MVC…" identifies the responding institution.
  25. present: Authority is named through the fragment "GWAlert: Emergency, Foggy Bottom & MVC…".
• 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

  1. present: Hazard is specific: the text names "tornado warning".
  2. present: A concrete threat appears as "tornado warning".
  3. present: The what of the emergency is "tornado warning", not a vague incident label.
  4. present: "tornado warning" satisfies hazard by naming the condition or threat.
  5. present: Readers learn the hazard type from "tornado warning".
  6. present: Hazard present via the explicit phrase "tornado warning".
  7. present: The threat is particularized as "tornado warning".
  8. present: Coding H=1 because "tornado warning" is a named hazard.
  9. present: Specific danger language: "tornado warning".
  10. present: The alert states the problem as "tornado warning".
  11. present: Hazard element met by "tornado warning".
  12. present: "tornado warning" is more than a generic emergency word.
  13. present: Threat identity is clear from "tornado warning".
  14. present: The message pins the hazard to "tornado warning".
  15. present: Named condition "tornado warning" counts as hazard.
  16. present: H is present: "tornado warning" tells what is wrong.
  17. present: Concrete hazard wording includes "tornado warning".
  18. present: The incident type is given as "tornado warning".
  19. present: "tornado warning" is the stated threat or weather/system hazard.
  20. present: Hazard codes yes on "tornado warning".
  21. present: Specifics beat generics here: "tornado warning".
  22. present: The text's hazard signal is "tornado warning".
  23. present: What happened is labeled "tornado warning".
  24. present: Hazard present with the phrase "tornado warning".
  25. 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

  1. absent: No building, campus, street, or area is named.
  2. absent: Location is absent: the text never says where.
  3. absent: There is no place cue for recipients to orient to.
  4. absent: L=0 because spatial reference is missing.
  5. absent: The alert omits campus or site detail.
  6. absent: Where this applies is never stated.
  7. absent: No location language appears in the body.
  8. absent: Place naming fails on this wording.
  9. absent: Readers get no geographic anchor.
  10. absent: Location element is not satisfied.
  11. absent: Without a place name, L is zero.
  12. absent: The message leaves location unspecified.
  13. absent: No hall, campus, or area reference is present.
  14. absent: Spatial information is missing entirely.
  15. absent: L fails the place-naming test.
  16. absent: Affected site is not identified.
  17. absent: Location codes absent here.
  18. absent: The text is silent on where.
  19. absent: No campus geography is given.
  20. absent: Place element cannot be coded present.
  21. absent: Where-cue is blank in this alert.
  22. absent: Location not established by the wording.
  23. absent: Site detail is omitted.
  24. absent: No area or building reference exists.
  25. absent: L is absent on a pure no-place text.
• Guidancepresent25/25

  Final assessment

  Majority 25/25 present. Guidance is the instruction "GWAlert: Emergency, Foggy Bottom & MVC…".

  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

  1. present: Guidance is the instruction "GWAlert: Emergency, Foggy Bottom & MVC…".
  2. present: Protective action appears as "GWAlert: Emergency, Foggy Bottom & MVC…".
  3. present: Recipients are told to act via "GWAlert: Emergency, Foggy Bottom & MVC…".
  4. present: "GWAlert: Emergency, Foggy Bottom & MVC…" is a direct what-to-do line.
  5. present: G=1 because "GWAlert: Emergency, Foggy Bottom & MVC…" instructs the audience.
  6. present: The alert directs action with "GWAlert: Emergency, Foggy Bottom & MVC…".
  7. present: Guidance present: "GWAlert: Emergency, Foggy Bottom & MVC…".
  8. present: A clear instruction is "GWAlert: Emergency, Foggy Bottom & MVC…".
  9. present: What to do is stated as "GWAlert: Emergency, Foggy Bottom & MVC…".
  10. present: "GWAlert: Emergency, Foggy Bottom & MVC…" counts as protective guidance.
  11. present: Action language "GWAlert: Emergency, Foggy Bottom & MVC…" meets guidance.
  12. present: The message tells people "GWAlert: Emergency, Foggy Bottom & MVC…".
  13. present: Guidance codes yes on "GWAlert: Emergency, Foggy Bottom & MVC…".
  14. present: Operational direction: "GWAlert: Emergency, Foggy Bottom & MVC…".
  15. present: Instructional content includes "GWAlert: Emergency, Foggy Bottom & MVC…".
  16. present: "GWAlert: Emergency, Foggy Bottom & MVC…" is audience-facing guidance.
  17. present: G is present via the cue "GWAlert: Emergency, Foggy Bottom & MVC…".
  18. present: Protective or operational order "GWAlert: Emergency, Foggy Bottom & MVC…" is explicit.
  19. present: The text's guidance signal is "GWAlert: Emergency, Foggy Bottom & MVC…".
  20. present: Recipients receive the directive "GWAlert: Emergency, Foggy Bottom & MVC…".
  21. present: What-to-do element satisfied by "GWAlert: Emergency, Foggy Bottom & MVC…".
  22. present: "GWAlert: Emergency, Foggy Bottom & MVC…" tells the public how to respond or operate.
  23. present: Guidance met through "GWAlert: Emergency, Foggy Bottom & MVC…".
  24. present: Action instruction present: "GWAlert: Emergency, Foggy Bottom & MVC…".
  25. present: The alert's order to the audience is "GWAlert: Emergency, Foggy Bottom & MVC…".
• Timeabsent0/25

  Final assessment

  Majority 25/25 absent. No clock time, date, or recency word such as now or today appears.

  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

  1. absent: No clock time, date, or recency word such as now or today appears.
  2. absent: Time is absent from the alert text.
  3. absent: Nothing tells recipients when this applies.
  4. absent: T=0 because temporal cues are missing.
  5. absent: No day, hour, or immediate language is stated.
  6. absent: The message omits timing entirely.
  7. absent: Time element fails on this wording.
  8. absent: When is left unspecified.
  9. absent: No calendar or clock reference is present.
  10. absent: Temporal information cannot be found.
  11. absent: Without a time cue, T is zero.
  12. absent: The alert is silent on schedule.
  13. absent: Time codes absent here.
  14. absent: Recency language is missing.
  15. absent: T fails the when test.
  16. absent: No today/now/clock marker appears.
  17. absent: Timing is not established by the text.
  18. absent: Date and hour are both omitted.
  19. absent: Temporal element is not satisfied.
  20. absent: The body lacks any when cue.
  21. absent: Time not present under the rubric.
  22. absent: Schedule detail is blank.
  23. absent: No temporal anchor is given.
  24. absent: T is absent on timeless wording.
  25. absent: When-information is not included.
• 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

  1. absent: No consequence or severity language appears beyond naming a hazard.
  2. absent: Impact is absent: the text does not say what the threat could do.
  3. absent: Nothing states danger level, injuries, or disruptive effect.
  4. absent: I=0 because severity or harm is not conveyed.
  5. absent: Hazard may be named, but impact language is missing.
  6. absent: The alert omits consequence wording.
  7. absent: Impact fails the harm-or-severity test.
  8. absent: Readers are not told stakes or effects.
  9. absent: No life-safety or operational impact phrase is present.
  10. absent: Impact element codes absent.
  11. absent: Without consequence language, I is zero.
  12. absent: Severity is left unstated.
  13. absent: The text stops short of impact.
  14. absent: Harm potential is not described.
  15. absent: I fails on bare description without effects.
  16. absent: No dangerous/closed/injury-style impact cue appears.
  17. absent: Impact not established by the wording.
  18. absent: Consequence detail is missing.
  19. absent: The message lacks severity framing.
  20. absent: I is absent under the impact rule.
  21. absent: Stakes for people or property are not stated.
  22. absent: No disruption or harm language is included.
  23. absent: Impact cannot be coded present here.
  24. absent: Effect-on-campus language is omitted.
  25. absent: Severity/consequence element fails.