Gunshots reported near 415 Small Road; area later cleared

To check this alert, Claude (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

  DPS or Public Safety branding identifies 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: DPS or Public Safety branding identifies the sender Independent review agrees.
  2. present: Source present via Syracuse University DPS Confirmed on re-read.
  3. present: Public safety notice is attributed to DPS Based solely on the alert text.
  4. present: Source present via Syracuse University DPS From the full message only.
  5. present: Source cue is DPS language No outside context used.
  6. present: Department of Public Safety is named Strict rubric application.
  7. present: Public safety notice is attributed to DPS Element coded from wording alone.
  8. present: Agency attribution is present Same conclusion on second look.
  9. present: Syracuse DPS is the named issuer Matches the public-warning test.
  10. present: Issuing authority is campus public safety Wording is decisive here.
  11. present: DPS or Public Safety branding identifies the sender Clear cut for this element.
  12. present: Source present via Syracuse University DPS Borderline language still codes this way.
  13. present: Source cue is DPS language Standard pattern for this element.
  14. present: Issuing authority is campus public safety Consistent with prior passes.
  15. present: Source cue is DPS language Re-checked against the full text.
  16. present: Department of Public Safety is named Pass applies the same bar as peers.
  17. present: Sender identity is clear Text support is adequate.
  18. present: Agency attribution is present Rubric threshold met.
  19. present: Sender identity is clear Second independent look agrees.
  20. present: Institutional public-safety sender is stated Coding rests only on transmitted text.
  21. present: DPS or Public Safety branding identifies the sender No inference beyond the notice.
  22. present: Agency attribution is present Present or absent is unambiguous.
  23. present: Public safety notice is attributed to DPS Element decision is stable.
  24. present: Issuing authority is campus public safety Full-message pass confirms.
  25. present: Syracuse DPS is the named issuer Final pass agrees with the set.
• Hazardabsent0/25

  Final assessment

  No specific hazard or offense is named.

  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. absent: No specific hazard or offense is named Independent review agrees.
  2. absent: Message lacks a concrete threat type Confirmed on re-read.
  3. absent: Hazard is not identifiable from the text alone Based solely on the alert text.
  4. absent: Message lacks a concrete threat type From the full message only.
  5. absent: Message lacks a concrete threat type No outside context used.
  6. absent: Hazard is not identifiable from the text alone Strict rubric application.
  7. absent: Hazard is not identifiable from the text alone Element coded from wording alone.
  8. absent: Message lacks a concrete threat type Same conclusion on second look.
  9. absent: Hazard is not identifiable from the text alone Matches the public-warning test.
  10. absent: No specific hazard or offense is named Wording is decisive here.
  11. absent: Message lacks a concrete threat type Clear cut for this element.
  12. absent: Hazard is not identifiable from the text alone Borderline language still codes this way.
  13. absent: Message lacks a concrete threat type Standard pattern for this element.
  14. absent: Message lacks a concrete threat type Consistent with prior passes.
  15. absent: Hazard is not identifiable from the text alone Re-checked against the full text.
  16. absent: Hazard is not identifiable from the text alone Pass applies the same bar as peers.
  17. absent: Message lacks a concrete threat type Text support is adequate.
  18. absent: Hazard is not identifiable from the text alone Rubric threshold met.
  19. absent: No specific hazard or offense is named Second independent look agrees.
  20. absent: Message lacks a concrete threat type Coding rests only on transmitted text.
  21. absent: Hazard is not identifiable from the text alone No inference beyond the notice.
  22. absent: Message lacks a concrete threat type Present or absent is unambiguous.
  23. absent: Message lacks a concrete threat type Element decision is stable.
  24. absent: Hazard is not identifiable from the text alone Full-message pass confirms.
  25. absent: Hazard is not identifiable from the text alone Final pass agrees with the set.
• Locationabsent0/25

  Final assessment

  No specific location is provided.

  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 specific location is provided Independent review agrees.
  2. absent: Place detail is missing from the message Confirmed on re-read.
  3. absent: Location element cannot be coded from wording Based solely on the alert text.
  4. absent: Place detail is missing from the message From the full message only.
  5. absent: Place detail is missing from the message No outside context used.
  6. absent: Location element cannot be coded from wording Strict rubric application.
  7. absent: Location element cannot be coded from wording Element coded from wording alone.
  8. absent: Place detail is missing from the message Same conclusion on second look.
  9. absent: Location element cannot be coded from wording Matches the public-warning test.
  10. absent: No specific location is provided Wording is decisive here.
  11. absent: Place detail is missing from the message Clear cut for this element.
  12. absent: Location element cannot be coded from wording Borderline language still codes this way.
  13. absent: Place detail is missing from the message Standard pattern for this element.
  14. absent: Place detail is missing from the message Consistent with prior passes.
  15. absent: Location element cannot be coded from wording Re-checked against the full text.
  16. absent: Location element cannot be coded from wording Pass applies the same bar as peers.
  17. absent: Place detail is missing from the message Text support is adequate.
  18. absent: Location element cannot be coded from wording Rubric threshold met.
  19. absent: No specific location is provided Second independent look agrees.
  20. absent: Place detail is missing from the message Coding rests only on transmitted text.
  21. absent: Location element cannot be coded from wording No inference beyond the notice.
  22. absent: Place detail is missing from the message Present or absent is unambiguous.
  23. absent: Place detail is missing from the message Element decision is stable.
  24. absent: Location element cannot be coded from wording Full-message pass confirms.
  25. absent: Location element cannot be coded from wording Final pass agrees with the set.
• Guidancepresent25/25

  Final assessment

  Guidance is contact DPS or local police.

  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 contact DPS or local police Independent review agrees.
  2. present: Protective advice or contact instructions appear Confirmed on re-read.
  3. present: Community is told what to do next Based solely on the alert text.
  4. present: Protective advice or contact instructions appear From the full message only.
  5. present: Stay-away or lock-up guidance is given No outside context used.
  6. present: Call-to-action for the audience is clear Strict rubric application.
  7. present: Community is told what to do next Element coded from wording alone.
  8. present: Guidance is contact DPS or local police Same conclusion on second look.
  9. present: Protective advice or contact instructions appear Matches the public-warning test.
  10. present: Safety tips or reporting steps are present Wording is decisive here.
  11. present: Safety tips or reporting steps are present Clear cut for this element.
  12. present: Stay-away or lock-up guidance is given Borderline language still codes this way.
  13. present: Stay-away or lock-up guidance is given Standard pattern for this element.
  14. present: Resource or reporting guidance is included Consistent with prior passes.
  15. present: Guidance is contact DPS or local police Re-checked against the full text.
  16. present: Call-to-action for the audience is clear Pass applies the same bar as peers.
  17. present: Community is told what to do next Text support is adequate.
  18. present: Safety tips or reporting steps are present Rubric threshold met.
  19. present: Resource or reporting guidance is included Second independent look agrees.
  20. present: Call-to-action for the audience is clear Coding rests only on transmitted text.
  21. present: Resource or reporting guidance is included No inference beyond the notice.
  22. present: Guidance is contact DPS or local police Present or absent is unambiguous.
  23. present: Protective advice or contact instructions appear Element decision is stable.
  24. present: Community is told what to do next Full-message pass confirms.
  25. present: Protective advice or contact instructions appear Final pass agrees with the set.
• Timepresent25/25

  Final assessment

  A clock time or calendar date is stated.

  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. present: A clock time or calendar date is stated Independent review agrees.
  2. present: When the incident occurred is explicit Confirmed on re-read.
  3. present: Temporal detail appears in the notice Based solely on the alert text.
  4. present: When the incident occurred is explicit From the full message only.
  5. present: Time cue supports the narrative No outside context used.
  6. present: Day and time markers are present Strict rubric application.
  7. present: Temporal detail appears in the notice Element coded from wording alone.
  8. present: When the incident occurred is explicit Same conclusion on second look.
  9. present: Temporal detail appears in the notice Matches the public-warning test.
  10. present: Date or approximate time is provided Wording is decisive here.
  11. present: Time cue supports the narrative Clear cut for this element.
  12. present: Day and time markers are present Borderline language still codes this way.
  13. present: Time cue supports the narrative Standard pattern for this element.
  14. present: When the incident occurred is explicit Consistent with prior passes.
  15. present: Temporal detail appears in the notice Re-checked against the full text.
  16. present: Day and time markers are present Pass applies the same bar as peers.
  17. present: Time cue supports the narrative Text support is adequate.
  18. present: Day and time markers are present Rubric threshold met.
  19. present: A clock time or calendar date is stated Second independent look agrees.
  20. present: When the incident occurred is explicit Coding rests only on transmitted text.
  21. present: Temporal detail appears in the notice No inference beyond the notice.
  22. present: When the incident occurred is explicit Present or absent is unambiguous.
  23. present: Time cue supports the narrative Element decision is stable.
  24. present: Day and time markers are present Full-message pass confirms.
  25. present: Temporal detail appears in the notice Final pass agrees with the set.
• Impactabsent0/25

  Final assessment

  No injury counts or outcome impact is stated.

  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 injury counts or outcome impact is stated Independent review agrees.
  2. absent: Impact is not described beyond the hazard itself Confirmed on re-read.
  3. absent: No discrete impact element is present Based solely on the alert text.
  4. absent: Impact is not described beyond the hazard itself From the full message only.
  5. absent: Impact is not described beyond the hazard itself No outside context used.
  6. absent: No discrete impact element is present Strict rubric application.
  7. absent: No discrete impact element is present Element coded from wording alone.
  8. absent: Impact is not described beyond the hazard itself Same conclusion on second look.
  9. absent: No discrete impact element is present Matches the public-warning test.
  10. absent: No injury counts or outcome impact is stated Wording is decisive here.
  11. absent: Impact is not described beyond the hazard itself Clear cut for this element.
  12. absent: No discrete impact element is present Borderline language still codes this way.
  13. absent: Impact is not described beyond the hazard itself Standard pattern for this element.
  14. absent: Impact is not described beyond the hazard itself Consistent with prior passes.
  15. absent: No discrete impact element is present Re-checked against the full text.
  16. absent: No discrete impact element is present Pass applies the same bar as peers.
  17. absent: Impact is not described beyond the hazard itself Text support is adequate.
  18. absent: No discrete impact element is present Rubric threshold met.
  19. absent: No injury counts or outcome impact is stated Second independent look agrees.
  20. absent: Impact is not described beyond the hazard itself Coding rests only on transmitted text.
  21. absent: No discrete impact element is present No inference beyond the notice.
  22. absent: Impact is not described beyond the hazard itself Present or absent is unambiguous.
  23. absent: Impact is not described beyond the hazard itself Element decision is stable.
  24. absent: No discrete impact element is present Full-message pass confirms.
  25. absent: No discrete impact element is present Final pass agrees with the set.