Campus Alert Archive
Oregon

Barricaded person near Garden Ave and Moss Street

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

UO Alert told the campus to avoid Garden Ave and Moss St for a person barricaded near campus, then posted an all-clear after EPD left.

Alerts
3
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

3 messages in sequence · 3 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 verbatim69 chars
UO Alert Eugene AVOID: Garden Ave/ Moss St. Law Enforcement Activity.
Verify this quote
UO Alert Eugene AVOID: Garden Ave/ Moss St. Law Enforcement Activity.safety.uoregon.edufind archived copies
Dual independent HTML fetch 2026-08-24. Drupal body field held only the timestamp; official product recovered from twitter:title / meta description, including a location-update sentence in the description. Second blind sha256 f9c6f4529d586be241a0728325f61e7d34ae7e7582b350a97fa2dfbc93a132b8.
Thread N/A (web posting, not X).
Distinct incident from 2026-07-24-university-of-oregon-2345-patterson-barricade: different date and place.
UPDATEWebsite+43 min
Verified verbatim2175 chars
UO Eugene Campus Alert: AVOID Garden Ave and Moss St area July 29, 2026 | 11:15 p.m. Continue to avoid the area around the intersection of Garden Ave and Moss St (correction of location). Eugene Police Department is on the scene of a person barricaded near campus. More information, when and if available, will be posted at alerts.uoregon.edu If you have information about this situation, call Eugene Police Department at 541-682-5111. What is this notice? Campus Alerts are sent by the University of Oregon Police Department when certain crimes are reported on or near campus property, and in compliance with federal law. These advisories provide information for campus community members to take precautions for personal safety. All crimes should be reported as soon as possible to local law enforcement.  SAFETY TIPS FROM UOPD    No action or inaction by a crime survivor makes that person responsible for his or her victimization. Perpetrators are responsible for crimes and their effects. The following suggestions may help reduce the possibility of experiencing such a crime or may improve opportunities to receive prompt assistance.    Make sure to lock all doors and windows when leaving the room or building.   Secure your belongings and don’t leave them unattended.   Don’t hold doors open for unknown people to let them enter private, secure areas.   Report criminal activity (such as a break-in or intruder, robbery, or assault) immediately to 911, or for non-emergency situations on campus, to UOPD at 541-346-2919.    RESOURCES AVAILABLE FOR SURVIVORS OF CRIME    Student survivors of crime may find support and resource options at  safe.uoregon.edu or call the 24-hour SAFE hotline at 541-346-SAFE (7233).   Employee survivors of crime may find services and support options through Canopy at https://www.cascadecenters.com/index.php?. Canopy is a comprehensive employee assistance program for faculty and staff and their dependents. The services are at no cost to eligible members and all your information is kept confidential. University Counseling Services is open until 5:00 p.m. on weekdays and offers 24-hour support via phone; 541-346-3227.
Verify this quote
UO Eugene Campus Alert: AVOID Garden Ave and Moss St area (location correction / barricade)safety.uoregon.edufind archived copies
Dual independent HTML fetch 2026-08-24. Official continue-avoid with location correction recovered from twitter:description. Second blind sha256 93cdc6b5bbf1835311ac323569f041ee68308a6b0c461bab8e20988a5ace25fe.
2026-09-21 second deep audit b46 P3 partial: listing-page-composite. Recapture official product (listing chrome/dateline stitch off). Dual. Cap-exempt R1.
ALL CLEARWebsite+4h 53m
Verified verbatim412 chars
UO Eugene Campus All Clear: Garden Ave and Moss St area July 30, 2026 | 3:25 a.m. The Eugene Police Department has resolved the situation near the intersection of Garden Ave and Moss St. and have left the area. Normal access has resumed. More information, when and if available, will be posted at alerts.uoregon.edu If you have information about this situation, call Eugene Police Department at 541-682-5111.
Verify this quote
UO Eugene Campus All Clear: Garden Ave and Moss St areasafety.uoregon.edufind archived copies
Dual independent HTML fetch 2026-08-24. Official all-clear recovered from twitter:description. Incident date remains 2026-07-29; all-clear posted 3:25 a.m. July 30 PDT. Second blind sha256 a06744452d8a40eeb90dd666a57bea532aa56fea93e4aa678225c3be8f8b8569.
2026-09-21 second deep audit b46 P3 partial: listing-page-composite. Recapture official product (listing chrome/dateline stitch off). Dual. Cap-exempt R1.
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.

UO Alert Eugene AVOID: Garden Ave/ Moss St. Law Enforcement Activity.

  • Sourcepresent25/25

    Final assessment

    UO Alert Eugene is a branded sender tag. Majority 25/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. present: Opens with branded UO Alert Eugene, which identifies the sending alert system (UO Garden AVOID, pass 1).
    2. present: UO Alert Eugene is a branded signature counting as Source (UO Garden AVOID, pass 2).
    3. present: The message identifies the sender as UO Alert Eugene before AVOID (UO Garden AVOID, pass 3).
    4. present: Source is present via the UO Alert Eugene brand (UO Garden AVOID, pass 4).
    5. present: I count S 1 because UO Alert Eugene names who is issuing the product (UO Garden AVOID, pass 5).
    6. present: A branded UO Alert opener is the rubric example of a sender tag (UO Garden AVOID, pass 6).
    7. present: Source holds: UO Alert Eugene is an explicit alerting-system signature (UO Garden AVOID, pass 7).
    8. present: I mark S present due to UO Alert Eugene (UO Garden AVOID, pass 8).
    9. present: The issuing identity is the branded UO Alert Eugene line (UO Garden AVOID, pass 9).
    10. present: Sender tag is present: UO Alert Eugene at the front (UO Garden AVOID, pass 10).
    11. present: This is a branded signature of the kind the rubric lists (UO Garden AVOID, pass 11).
    12. present: I score S 1; the campus alert brand is stated (UO Garden AVOID, pass 12).
    13. present: UO Alert Eugene tells the reader which campus system is talking (UO Garden AVOID, pass 13).
    14. present: Source element is satisfied by the opening brand (UO Garden AVOID, pass 14).
    15. present: The text leads with UO Alert Eugene (UO Garden AVOID, pass 15).
    16. present: Branded opener UO Alert Eugene is sufficient Source (UO Garden AVOID, pass 16).
    17. present: I treat UO Alert Eugene as a sender identity stamp (UO Garden AVOID, pass 17).
    18. present: Who is sending: UO Alert Eugene (UO Garden AVOID, pass 18).
    19. present: A school-named alert brand counts as Source (UO Garden AVOID, pass 19).
    20. present: The product is signed UO Alert Eugene (UO Garden AVOID, pass 20).
    21. present: I find a sender brand in UO Alert Eugene (UO Garden AVOID, pass 21).
    22. present: Source is the UO Alert Eugene label (UO Garden AVOID, pass 22).
    23. present: Present: branded UO Alert Eugene identifies the authority (UO Garden AVOID, pass 23).
    24. present: Without UO Alert Eugene this would lack source (UO Garden AVOID, pass 24).
    25. present: Eugene in the brand is part of the sender tag (UO Garden 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 Garden AVOID, pass 1).
    2. present: LAW ENFORCEMENT ACTIVITY names the threat class (UO Garden AVOID, pass 2).
    3. present: H is present via law enforcement activity, not a generic emergency (UO Garden AVOID, pass 3).
    4. present: I count H 1 because law enforcement activity is specified (UO Garden AVOID, pass 4).
    5. present: The body names law enforcement activity as the event (UO Garden AVOID, pass 5).
    6. present: Readers are told the hazard is police activity (UO Garden AVOID, pass 6).
    7. present: Hazard coding is 1 for LAW ENFORCEMENT ACTIVITY (UO Garden AVOID, pass 7).
    8. present: What is happening is law enforcement activity at Garden/Moss (UO Garden AVOID, pass 8).
    9. present: I mark H present (UO Garden AVOID, pass 9).
    10. present: Named threat: law enforcement activity (UO Garden AVOID, pass 10).
    11. present: The text does not hide behind incident; it says law enforcement activity (UO Garden AVOID, pass 11).
    12. present: Specific threat language is LAW ENFORCEMENT ACTIVITY (UO Garden AVOID, pass 12).
    13. present: Hazard element is satisfied by naming law enforcement activity (UO Garden AVOID, pass 13).
    14. present: Police activity is the hazard (UO Garden AVOID, pass 14).
    15. present: This is not a vague situation; it is law enforcement activity (UO Garden AVOID, pass 15).
    16. present: I score H present for law enforcement activity (UO Garden AVOID, pass 16).
    17. present: H holds because law enforcement activity is more specific than emergency (UO Garden AVOID, pass 17).
    18. present: The alert tells you the threat is law enforcement activity (UO Garden AVOID, pass 18).
    19. present: I read LAW ENFORCEMENT ACTIVITY as a specified hazard (UO Garden AVOID, pass 19).
    20. present: A law-enforcement event is a specific named hazard (UO Garden AVOID, pass 20).
    21. present: AVOID plus law enforcement activity names the situation (UO Garden AVOID, pass 21).
    22. present: I find a specific threat: law enforcement activity (UO Garden AVOID, pass 22).
    23. present: Hazard is present (UO Garden AVOID, pass 23).
    24. present: H is 1 on this AVOID product (UO Garden AVOID, pass 24).
    25. present: The all-caps law enforcement activity line is the hazard (UO Garden AVOID, pass 25).
  • Locationpresent25/25

    Final assessment

    Garden Ave/ Moss St is a named location. 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 Garden Ave/ Moss St, a named street address (UO Garden AVOID, pass 1).
    2. present: 2345 PATTERSON is a specific place (UO Garden AVOID, pass 2).
    3. present: L is present: Garden Ave/ Moss St (UO Garden AVOID, pass 3).
    4. present: The geographic target is Garden Ave/ Moss St (UO Garden AVOID, pass 4).
    5. present: A street address satisfies the location element (UO Garden AVOID, pass 5).
    6. present: Where: Garden Ave/ Moss St (UO Garden AVOID, pass 6).
    7. present: I code L 1 because Garden Ave/ Moss St is an identifiable place (UO Garden AVOID, pass 7).
    8. present: The text locates the activity at Garden Ave/ Moss St (UO Garden AVOID, pass 8).
    9. present: Named address Garden Ave/ Moss St is a location (UO Garden AVOID, pass 9).
    10. present: Place is specified as Garden Ave/ Moss St (UO Garden AVOID, pass 10).
    11. present: Readers are told where: Garden Ave/ Moss St (UO Garden AVOID, pass 11).
    12. present: L holds on Garden Ave/ Moss St (UO Garden AVOID, pass 12).
    13. present: The AVOID footprint is Garden Ave/ Moss St (UO Garden AVOID, pass 13).
    14. present: Location is not omitted; the address is written out (UO Garden AVOID, pass 14).
    15. present: I treat Garden Ave/ Moss St as the location phrase (UO Garden AVOID, pass 15).
    16. present: Named place: Garden Ave/ Moss St (UO Garden AVOID, pass 16).
    17. present: The sentence pins the product to that address (UO Garden AVOID, pass 17).
    18. present: Street-address location is present (UO Garden AVOID, pass 18).
    19. present: Where to avoid is Garden Ave/ Moss St (UO Garden AVOID, pass 19).
    20. present: L is satisfied by the address (UO Garden AVOID, pass 20).
    21. present: The alert states a place: Garden Ave/ Moss St (UO Garden AVOID, pass 21).
    22. present: I mark location present for Garden Ave/ Moss St (UO Garden AVOID, pass 22).
    23. present: Garden/Moss is a street name with a number (UO Garden AVOID, pass 23).
    24. present: I score L 1 for Garden Ave/ Moss St (UO Garden AVOID, pass 24).
    25. present: Address-level location is present (UO Garden 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 to stay away (UO Garden AVOID, pass 1).
    2. present: AVOID is an instruction to recipients (UO Garden AVOID, pass 2).
    3. present: G is present via AVOID (UO Garden AVOID, pass 3).
    4. present: I count G 1 for AVOID (UO Garden AVOID, pass 4).
    5. present: The text tells people to avoid Garden Ave/ Moss St (UO Garden AVOID, pass 5).
    6. present: Guidance element is met by AVOID (UO Garden AVOID, pass 6).
    7. present: I score G present because recipients are told to avoid the address (UO Garden AVOID, pass 7).
    8. present: Action language is AVOID (UO Garden AVOID, pass 8).
    9. present: G holds: avoid is a protective action in the rubric (UO Garden AVOID, pass 9).
    10. present: The alert directs people away from the address (UO Garden AVOID, pass 10).
    11. present: AVOID is imperative guidance (UO Garden AVOID, pass 11).
    12. present: I mark G 1 for AVOID (UO Garden AVOID, pass 12).
    13. present: Stay away is the sense of AVOID (UO Garden AVOID, pass 13).
    14. present: I treat AVOID as rubric guidance (UO Garden AVOID, pass 14).
    15. present: The body instructs avoidance (UO Garden AVOID, pass 15).
    16. present: Guidance is present (UO Garden AVOID, pass 16).
    17. present: I read AVOID as the protective step (UO Garden AVOID, pass 17).
    18. present: Avoid-area guidance is present (UO Garden AVOID, pass 18).
    19. present: G is 1 on this AVOID product (UO Garden AVOID, pass 19).
    20. present: The colon after AVOID introduces the place to avoid (UO Garden AVOID, pass 20).
    21. present: I find an imperative AVOID (UO Garden AVOID, pass 21).
    22. present: Protective instruction is AVOID (UO Garden AVOID, pass 22).
    23. present: Guidance present via AVOID (UO Garden AVOID, pass 23).
    24. present: I will not ignore AVOID as a label; it is an instruction (UO Garden AVOID, pass 24).
    25. present: G present (UO Garden AVOID, pass 25).
  • Timeabsent0/25

    Final assessment

    No clock, date, now, or immediately in this short product. Majority 0/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. absent: No clock time, date, now, or immediately appears in this short product (UO Garden AVOID, pass 1).
    2. absent: T is absent: 2345 is an address number, not a time (UO Garden AVOID, pass 2).
    3. absent: I code T 0 because no date or clock is in the twitter:title product (UO Garden AVOID, pass 3).
    4. absent: The rubric examples are not matched (UO Garden AVOID, pass 4).
    5. absent: I mark T absent (UO Garden AVOID, pass 5).
    6. absent: No recency word such as now is present (UO Garden AVOID, pass 6).
    7. absent: Time element fails (UO Garden AVOID, pass 7).
    8. absent: I score T absent (UO Garden AVOID, pass 8).
    9. absent: The timestamp lived in the Drupal date field, not this product string (UO Garden AVOID, pass 9).
    10. absent: T 0: no today, now, or clock (UO Garden AVOID, pass 10).
    11. absent: I find no time cue in the AVOID line (UO Garden AVOID, pass 11).
    12. absent: Time is not present (UO Garden AVOID, pass 12).
    13. absent: I decline to treat 2345 as a time (UO Garden AVOID, pass 13).
    14. absent: No immediately appears (UO Garden AVOID, pass 14).
    15. absent: T is 0 on this short AVOID (UO Garden AVOID, pass 15).
    16. absent: The body has no when (UO Garden AVOID, pass 16).
    17. absent: I read no Time element (UO Garden AVOID, pass 17).
    18. absent: Without a clock or now, Time is absent (UO Garden AVOID, pass 18).
    19. absent: Date is not in this product string (UO Garden AVOID, pass 19).
    20. absent: I code time absent on the short title (UO Garden AVOID, pass 20).
    21. absent: Time fails (UO Garden AVOID, pass 21).
    22. absent: No as of or until appears (UO Garden AVOID, pass 22).
    23. absent: I will not import the Drupal timestamp into the product (UO Garden AVOID, pass 23).
    24. absent: T absent (UO Garden AVOID, pass 24).
    25. absent: The short SMS-like title has no time words (UO Garden AVOID, pass 25).
  • Impactabsent0/25

    Final assessment

    No explicit consequence. 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 consequence or severity is stated (UO Garden AVOID, pass 1).
    2. absent: Law enforcement activity names the situation, not a harm clause (UO Garden AVOID, pass 2).
    3. absent: I code I 0 because no deadly or injury language appears (UO Garden AVOID, pass 3).
    4. absent: AVOID is guidance, not impact (UO Garden AVOID, pass 4).
    5. absent: I mark I absent (UO Garden AVOID, pass 5).
    6. absent: The rubric example list is not matched (UO Garden AVOID, pass 6).
    7. absent: I find no harm-to-people sentence (UO Garden AVOID, pass 7).
    8. absent: Impact fails (UO Garden AVOID, pass 8).
    9. absent: I will not infer a barricade the first-burst omits (UO Garden AVOID, pass 9).
    10. absent: No dangerous wording is present (UO Garden AVOID, pass 10).
    11. absent: I score I absent (UO Garden AVOID, pass 11).
    12. absent: A named address is not impact (UO Garden AVOID, pass 12).
    13. absent: Consequence language is missing (UO Garden AVOID, pass 13).
    14. absent: I 0 on this AVOID (UO Garden AVOID, pass 14).
    15. absent: The body does not state severity (UO Garden AVOID, pass 15).
    16. absent: I decline to treat law enforcement activity as Impact (UO Garden AVOID, pass 16).
    17. absent: No injury is named (UO Garden AVOID, pass 17).
    18. absent: Impact is not present (UO Garden AVOID, pass 18).
    19. absent: I read no consequence clause (UO Garden AVOID, pass 19).
    20. absent: Without harm language, Impact is absent (UO Garden AVOID, pass 20).
    21. absent: The text never says why in consequence terms (UO Garden AVOID, pass 21).
    22. absent: I 0 because no explicit impact appears (UO Garden AVOID, pass 22).
    23. absent: ALL CAPS is emphasis not impact (UO Garden AVOID, pass 23).
    24. absent: I do not count a police presence as impact (UO Garden AVOID, pass 24).
    25. absent: Impact element fails on this AVOID (UO Garden 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

Barricaded person near Garden Ave and Moss St; location corrected mid-incident; all-clear after EPD left.
Outcome
Eugene Police resolved the situation and left; normal access resumed.
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 Garden Ave/Moss St
    safety.uoregon.edu
    archived copy
  2. Official
    UO Alert Eugene continue-avoid Garden Ave and Moss St
    safety.uoregon.edu
    archived copy
  3. Official
    UO Alert Eugene ALL CLEAR Garden Ave and Moss St
    safety.uoregon.edu
    archived copy
Cite this case

Campus Alert Archive. "University of Oregon: Barricaded person near Garden Ave and Moss Street." Incident of July 29, 2026. Added August 2026; last updated September 2026. https://campusalertarchive.com/case/university-of-oregon-garden-ave-moss-st-barricade-2026-07-29/

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-activitybarricade
Added August 2026Updated September 2026Via ingestion