Campus Alert Archive
Oregon

Law-enforcement activity at 18th and Agate then cleared

AI-generated · every claim is source-linked
ORpolice activityemergency notificationhigh confidence
Compare →

UO Alert told the campus to avoid 18th Ave and Agate Street for law-enforcement activity, then posted an all-clear 19 minutes later.

Alerts
2
Response
—
Killed
—
Injured
—
Institution
University of Oregon
Public R1 · OR
All Oregon cases →
UO Alert
Official alert policy
Read when and how Oregon says it will use UO Alert: summarized, quoted, and analyzed.
Documented Timeline

Alert Sequence

2 messages in sequence · 2 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.

INITIAL ALERTWebsite
Verified verbatim129 chars
10/25/25 11:40 PM AVOID 18th Ave and Agate Street due to law enforcement activity. For updates, visit safety.uoregon.edu/alerts
Verify this quote
UO Alert Eugene AVOID 18th Ave and Agate Streetsafety.uoregon.edufind archived copies
Dual independent HTML fetch 2026-08-24. Drupal empty-paragraph runs collapsed to double newlines. Second blind sha256 b58fa9949a2f123878a412ddbfa27b97e802571be419e4ec72c9085dc4e3e181.
Thread N/A (web posting, not X).
Distinct incident from 2025-12-08-university-of-oregon-12th-patterson-medical-call: different date and intersection.
ALL CLEARWebsite+19 min
Verified verbatim150 chars
10/25/25 11:59 PM ALL CLEAR - There is no longer law enforcement activity at 18th Ave and Agate Street. For updates, visit safety.uoregon.edu/alerts
Verify this quote
UO Alert Eugene ALL CLEAR 18th Ave and Agate Streetsafety.uoregon.edufind archived copies
Dual independent HTML fetch 2026-08-24. Archive path dated 10/26; product clock is 11:59 PM Oct 25. Second blind sha256 95c41c6d07f6932d1f79bb8d680c9723060f6861312441b96fc888f62006b2b0.
Message elements

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.

10/25/25 11:40 PM AVOID 18th Ave and Agate Street due to law enforcement activity. For updates, visit safety.uoregon.edu/alerts

  • Sourceabsent0/25

    Final assessment

    No branded sender in the Drupal AVOID body. Majority 0/25.

    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. absent: No branded UO Alert tag appears; the body opens with a date stamp then AVOID (UO Agate AVOID, pass 1).
    2. absent: Source is absent: UO Alert Eugene is not in this Drupal product (UO Agate AVOID, pass 2).
    3. absent: I code S 0 because the sender is not identified (UO Agate AVOID, pass 3).
    4. absent: A date line is not a source signature (UO Agate AVOID, pass 4).
    5. absent: I mark S absent (UO Agate AVOID, pass 5).
    6. absent: Law Enforcement Activity is the hazard, not a sender (UO Agate AVOID, pass 6).
    7. absent: Source fails (UO Agate AVOID, pass 7).
    8. absent: I score S 0 (UO Agate AVOID, pass 8).
    9. absent: No UOPD or UO Alert colon tag is in the text (UO Agate AVOID, pass 9).
    10. absent: I find no branded signature (UO Agate AVOID, pass 10).
    11. absent: S is 0 on this AVOID (UO Agate AVOID, pass 11).
    12. absent: alerts.uoregon.edu is a URL not a sender brand (UO Agate AVOID, pass 12).
    13. absent: I will not treat a URL as Source (UO Agate AVOID, pass 13).
    14. absent: No police agency is named in the first-burst AVOID (UO Agate AVOID, pass 14).
    15. absent: Source element is missing (UO Agate AVOID, pass 15).
    16. absent: I read no sender identity (UO Agate AVOID, pass 16).
    17. absent: Without UO Alert Eugene in this body, Source is absent (UO Agate AVOID, pass 17).
    18. absent: I do not import twitter:title brand into the product (UO Agate AVOID, pass 18).
    19. absent: S absent (UO Agate AVOID, pass 19).
    20. absent: Named streets are location not source (UO Agate AVOID, pass 20).
    21. absent: I code source absent (UO Agate AVOID, pass 21).
    22. absent: Sender identity is unspecified (UO Agate AVOID, pass 22).
    23. absent: S 0 (UO Agate AVOID, pass 23).
    24. absent: The AVOID line does not name who is sending it (UO Agate AVOID, pass 24).
    25. absent: No agency byline appears (UO Agate AVOID, pass 25).
  • Hazardpresent25/25

    Final assessment

    Law enforcement activity names a specific situation. Majority 25/25.

    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 Law Enforcement Activity, a specific named situation (UO Agate AVOID, pass 1).
    2. present: Law Enforcement Activity names the threat class (UO Agate AVOID, pass 2).
    3. present: H is present (UO Agate AVOID, pass 3).
    4. present: I count H 1 (UO Agate AVOID, pass 4).
    5. present: Not a generic emergency (UO Agate AVOID, pass 5).
    6. present: I mark H present (UO Agate AVOID, pass 6).
    7. present: Named hazard: Law Enforcement Activity (UO Agate AVOID, pass 7).
    8. present: H holds (UO Agate AVOID, pass 8).
    9. present: I score H 1 (UO Agate AVOID, pass 9).
    10. present: Police activity is specified (UO Agate AVOID, pass 10).
    11. present: Hazard element is satisfied (UO Agate AVOID, pass 11).
    12. present: I read Law Enforcement Activity as the hazard (UO Agate AVOID, pass 12).
    13. present: H is 1 (UO Agate AVOID, pass 13).
    14. present: The AVOID names law enforcement activity (UO Agate AVOID, pass 14).
    15. present: Specific situation language is present (UO Agate AVOID, pass 15).
    16. present: I treat Law Enforcement Activity as Hazard (UO Agate AVOID, pass 16).
    17. present: H present (UO Agate AVOID, pass 17).
    18. present: The product tells you what is happening (UO Agate AVOID, pass 18).
    19. present: I code H 1 (UO Agate AVOID, pass 19).
    20. present: Not a vague incident (UO Agate AVOID, pass 20).
    21. present: Hazard is law enforcement activity (UO Agate AVOID, pass 21).
    22. present: I find a named situation (UO Agate AVOID, pass 22).
    23. present: H 1 (UO Agate AVOID, pass 23).
    24. present: Law Enforcement Activity is specific (UO Agate AVOID, pass 24).
    25. present: The threat class is named (UO Agate AVOID, pass 25).
  • Locationpresent25/25

    Final assessment

    18th Ave and Agate Street is a named intersection. Majority 25/25.

    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. present: Location is 18th Ave and Agate Street, a named intersection (UO Agate AVOID, pass 1).
    2. present: 18th Ave and Agate Street is a specific place (UO Agate AVOID, pass 2).
    3. present: L is present (UO Agate AVOID, pass 3).
    4. present: I count L 1 (UO Agate AVOID, pass 4).
    5. present: Named streets satisfy location (UO Agate AVOID, pass 5).
    6. present: I mark L present (UO Agate AVOID, pass 6).
    7. present: Where: Franklin Blvd. and Orchard St (UO Agate AVOID, pass 7).
    8. present: L holds (UO Agate AVOID, pass 8).
    9. present: I score L 1 (UO Agate AVOID, pass 9).
    10. present: An intersection is a place (UO Agate AVOID, pass 10).
    11. present: Location element is satisfied (UO Agate AVOID, pass 11).
    12. present: I read Franklin and Orchard as location (UO Agate AVOID, pass 12).
    13. present: L is 1 (UO Agate AVOID, pass 13).
    14. present: The AVOID names the intersection (UO Agate AVOID, pass 14).
    15. present: Street-level location is present (UO Agate AVOID, pass 15).
    16. present: I treat 18th Ave and Agate Street as location (UO Agate AVOID, pass 16).
    17. present: Named place (UO Agate AVOID, pass 17).
    18. present: L present (UO Agate AVOID, pass 18).
    19. present: The site is specified (UO Agate AVOID, pass 19).
    20. present: I code L 1 (UO Agate AVOID, pass 20).
    21. present: Two named streets are a location (UO Agate AVOID, pass 21).
    22. present: Where to avoid is named (UO Agate AVOID, pass 22).
    23. present: Location is not omitted (UO Agate AVOID, pass 23).
    24. present: I find a named intersection (UO Agate AVOID, pass 24).
    25. present: L 1 (UO Agate AVOID, pass 25).
  • Guidancepresent25/25

    Final assessment

    AVOID is a protective instruction. Majority 25/25.

    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 AVOID, a protective instruction (UO Agate AVOID, pass 1).
    2. present: AVOID tells recipients to stay away (UO Agate AVOID, pass 2).
    3. present: G is present (UO Agate AVOID, pass 3).
    4. present: I count G 1 (UO Agate AVOID, pass 4).
    5. present: The text instructs people to avoid the intersection (UO Agate AVOID, pass 5).
    6. present: I mark G present (UO Agate AVOID, pass 6).
    7. present: Avoid-area guidance is in the rubric (UO Agate AVOID, pass 7).
    8. present: G holds (UO Agate AVOID, pass 8).
    9. present: I score G 1 (UO Agate AVOID, pass 9).
    10. present: An imperative AVOID is guidance (UO Agate AVOID, pass 10).
    11. present: Guidance element is satisfied (UO Agate AVOID, pass 11).
    12. present: I read AVOID as the protective step (UO Agate AVOID, pass 12).
    13. present: G is 1 (UO Agate AVOID, pass 13).
    14. present: The product tells you what to do: avoid (UO Agate AVOID, pass 14).
    15. present: I treat AVOID as guidance (UO Agate AVOID, pass 15).
    16. present: Not merely status (UO Agate AVOID, pass 16).
    17. present: G present (UO Agate AVOID, pass 17).
    18. present: Recipients are instructed (UO Agate AVOID, pass 18).
    19. present: I code G 1 (UO Agate AVOID, pass 19).
    20. present: Stay away is the sense of AVOID (UO Agate AVOID, pass 20).
    21. present: I find an instruction (UO Agate AVOID, pass 21).
    22. present: Guidance is AVOID (UO Agate AVOID, pass 22).
    23. present: I will count AVOID as G (UO Agate AVOID, pass 23).
    24. present: G 1 (UO Agate AVOID, pass 24).
    25. present: The AVOID line is protective (UO Agate AVOID, pass 25).
  • Timepresent25/25

    Final assessment

    10/25/25 11:40 PM is a date and clock. Majority 25/25.

    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: 10/25/25 11:40 PM is an explicit date and clock time (UO Agate AVOID, pass 1).
    2. present: T is present via 10/25/25 and 11:40 PM (UO Agate AVOID, pass 2).
    3. present: I count T 1 (UO Agate AVOID, pass 3).
    4. present: A clock time is listed in the rubric (UO Agate AVOID, pass 4).
    5. present: I mark T present (UO Agate AVOID, pass 5).
    6. present: The when is 11:40 p.m. October 25, 2025 (UO Agate AVOID, pass 6).
    7. present: T holds (UO Agate AVOID, pass 7).
    8. present: I score T 1 (UO Agate AVOID, pass 8).
    9. present: Date and clock are in the first line (UO Agate AVOID, pass 9).
    10. present: Time element is satisfied (UO Agate AVOID, pass 10).
    11. present: I read 11:40 PM as Time (UO Agate AVOID, pass 11).
    12. present: T is 1 (UO Agate AVOID, pass 12).
    13. present: A calendar date appears (UO Agate AVOID, pass 13).
    14. present: I treat 10/25/25 11:40 PM as Time present (UO Agate AVOID, pass 14).
    15. present: Without that stamp Time would fail (UO Agate AVOID, pass 15).
    16. present: T present (UO Agate AVOID, pass 16).
    17. present: Clock language is present (UO Agate AVOID, pass 17).
    18. present: I code T 1 (UO Agate AVOID, pass 18).
    19. present: The body names when (UO Agate AVOID, pass 19).
    20. present: I find a date and clock (UO Agate AVOID, pass 20).
    21. present: Time is 11:40 PM (UO Agate AVOID, pass 21).
    22. present: A date of the rubric kind is in the text (UO Agate AVOID, pass 22).
    23. present: I will count 10/25/25 as Time (UO Agate AVOID, pass 23).
    24. present: T 1 (UO Agate AVOID, pass 24).
    25. present: Date plus clock is Time (UO Agate AVOID, pass 25).
  • Impactabsent0/25

    Final assessment

    No explicit consequence in the first-burst AVOID. Majority 0/25.

    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: Impact is absent: no injury or severity is stated (UO Agate AVOID, pass 1).
    2. absent: Law Enforcement Activity names the situation, not a harm clause (UO Agate AVOID, pass 2).
    3. absent: I code I 0 (UO Agate AVOID, pass 3).
    4. absent: AVOID is guidance not impact (UO Agate AVOID, pass 4).
    5. absent: I mark I absent (UO Agate AVOID, pass 5).
    6. absent: The rubric example list is not matched (UO Agate AVOID, pass 6).
    7. absent: I find no harm sentence (UO Agate AVOID, pass 7).
    8. absent: Impact fails (UO Agate AVOID, pass 8).
    9. absent: I score I 0 (UO Agate AVOID, pass 9).
    10. absent: Naming police activity is the hazard, not impact (UO Agate AVOID, pass 10).
    11. absent: I 0 (UO Agate AVOID, pass 11).
    12. absent: Consequence language is missing (UO Agate AVOID, pass 12).
    13. absent: I decline to infer a robbery the first-burst omits (UO Agate AVOID, pass 13).
    14. absent: Impact is not present (UO Agate AVOID, pass 14).
    15. absent: I read no severity clause (UO Agate AVOID, pass 15).
    16. absent: Without harm language, Impact is absent (UO Agate AVOID, pass 16).
    17. absent: The AVOID does not state what the activity could do (UO Agate AVOID, pass 17).
    18. absent: I code I absent (UO Agate AVOID, pass 18).
    19. absent: No injury is named (UO Agate AVOID, pass 19).
    20. absent: Impact element fails (UO Agate AVOID, pass 20).
    21. absent: I will not invent a weapon from later sequence (UO Agate AVOID, pass 21).
    22. absent: I 0 on this AVOID (UO Agate AVOID, pass 22).
    23. absent: A named intersection is not impact (UO Agate AVOID, pass 23).
    24. absent: I do not count police activity as impact (UO Agate AVOID, pass 24).
    25. absent: Impact absent (UO Agate AVOID, pass 25).

Coded by SuperGrok Heavy 4.5

Systematic AI judgments with visible reasoning, not human-validated codings.

About this analysis
Context

Background

University of Oregon posts UO Alert products on safety.uoregon.edu/alerts.
Analysis

Key Findings

19-minute AVOID to ALL CLEAR at 18th Ave and Agate Street. Underlying call type not named.
Outcome
Law-enforcement activity ended the same night. Underlying call type not named in the all-clear.
Provenance

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.

  1. Official
    UO Alert Eugene AVOID 18th Ave and Agate Street
    safety.uoregon.edu
    archived copy
  2. Official
    UO Alert Eugene ALL CLEAR 18th Ave and Agate Street
    safety.uoregon.edu
    archived copy
Cite this case

Campus Alert Archive. "University of Oregon: Law-enforcement activity at 18th and Agate then cleared." Incident of October 25, 2025. Added August 2026. https://campusalertarchive.com/case/university-of-oregon-18th-agate-police-activity-2025-10-25/

Download case JSON

Alert text quoted on this page remains the work of the issuing institution; the archive is a secondary source.

Tags
public-r1oregonuo-alertpolice-activity
Added August 2026Updated August 2026Via ingestion