Skip to content
Campus Alert Archive
Duke

Public safety advisory after a stabbing on Douglas Street near Medical Center

AI-generated · every claim is source-linked
NCaggravated assaultcommunity notificationhigh confidence
Under Investigation

Duke University published a public safety notice concerning this incident. Full text is preserved from Duke Today / Campus Police public communications.

Alerts
1
Response
Killed
0
Injured
1
Institution
Duke University
Private R1 · NC
All Duke cases →
~17,000 studentsDukeALERT
Official alert policy
Read when and how Duke says it will use DukeALERT: summarized, quoted, and analyzed.
Documented Timeline

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.

INITIAL ALERTEmail
Verified verbatim697 chars
Public Safety Advisory: Stabbing on Douglas Street Suspect fled the scene in a gold pickup truck Earlier Tuesday morning, the Durham Police received a report of a person who had been stabbed on Douglas Street between the BP gas station and the Refuel convenience store on Ewrin Road across from Duke's Medical Center Campus. The two subjects had been in a fight prior to the stabbing. Shots were also fired in the area. Police are searching for the suspect who left the area in a gold pickup truck. There is no known Duke affiliation. The area is blocked and should be avoided. Anyone with information about this incident should contact the Durham Police Crimestoppers at 919-683-1200 or go to
Full text recovered from Duke Today public page body
Message elements

How the first alert is built

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.

Public Safety Advisory: Stabbing on Douglas Street Suspect fled the scene in a gold pickup truck Earlier Tuesday morning, the Durham Police received a report of a person who had been stabbed on Douglas Street between the BP gas station and the Refuel convenience store on Ewrin Road across from Duke's Medical Center Campus. The two subjects had been in a fight prior to the stabbing. Shots were also fired in the area. Police are searching for the suspect who left the area in a gold pickup truck. There is no known Duke affiliation. The area is blocked and should be avoided. Anyone with information about this incident should contact the Durham Police Crimestoppers at 919-683-1200 or go to

  • Sourcepresent25/25

    Final assessment

    Present: S per notice.

    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: Duke or police authority is named.
    2. present: Public safety issuer is clear in this notice.
    3. present: Coded: campus or Durham Police is identified.
    4. present: Agency identity present.
    5. present: Sender is explicit in this notice.
    6. present: Coded: duke or police authority is named.
    7. present: Public safety issuer is clear.
    8. present: Campus or Durham Police is identified in this notice.
    9. present: Coded: agency identity present.
    10. present: Sender is explicit.
    11. present: Duke or police authority is named in this notice.
    12. present: Coded: public safety issuer is clear.
    13. present: Campus or Durham Police is identified.
    14. present: Agency identity present in this notice.
    15. present: Coded: sender is explicit.
    16. present: Duke or police authority is named.
    17. present: Public safety issuer is clear in this notice.
    18. present: Coded: campus or Durham Police is identified.
    19. present: Agency identity present.
    20. present: Sender is explicit in this notice.
    21. present: Coded: duke or police authority is named.
    22. present: Public safety issuer is clear.
    23. present: Campus or Durham Police is identified in this notice.
    24. present: Coded: agency identity present.
    25. present: Sender is explicit.
  • Hazardpresent25/25

    Final assessment

    Present: H per notice.

    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: Specific hazard such as stabbing, fire, or robbery.
    2. present: Threat type is concrete in this notice.
    3. present: Coded: hazard wording is specific.
    4. present: Incident type is stated.
    5. present: Specific offense or fire is named in this notice.
    6. present: Coded: specific hazard such as stabbing, fire, or robbery.
    7. present: Threat type is concrete.
    8. present: Hazard wording is specific in this notice.
    9. present: Coded: incident type is stated.
    10. present: Specific offense or fire is named.
    11. present: Specific hazard such as stabbing, fire, or robbery in this notice.
    12. present: Coded: threat type is concrete.
    13. present: Hazard wording is specific.
    14. present: Incident type is stated in this notice.
    15. present: Coded: specific offense or fire is named.
    16. present: Specific hazard such as stabbing, fire, or robbery.
    17. present: Threat type is concrete in this notice.
    18. present: Coded: hazard wording is specific.
    19. present: Incident type is stated.
    20. present: Specific offense or fire is named in this notice.
    21. present: Coded: specific hazard such as stabbing, fire, or robbery.
    22. present: Threat type is concrete.
    23. present: Hazard wording is specific in this notice.
    24. present: Coded: incident type is stated.
    25. present: Specific offense or fire is named.
  • Locationpresent25/25

    Final assessment

    Present: L per notice.

    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: Street, trail, or campus area given.
    2. present: Location is concrete in this notice.
    3. present: Coded: place detail present.
    4. present: Geographic reference appears.
    5. present: Area is named in this notice.
    6. present: Coded: street, trail, or campus area given.
    7. present: Location is concrete.
    8. present: Place detail present in this notice.
    9. present: Coded: geographic reference appears.
    10. present: Area is named.
    11. present: Street, trail, or campus area given in this notice.
    12. present: Coded: location is concrete.
    13. present: Place detail present.
    14. present: Geographic reference appears in this notice.
    15. present: Coded: area is named.
    16. present: Street, trail, or campus area given.
    17. present: Location is concrete in this notice.
    18. present: Coded: place detail present.
    19. present: Geographic reference appears.
    20. present: Area is named in this notice.
    21. present: Coded: street, trail, or campus area given.
    22. present: Location is concrete.
    23. present: Place detail present in this notice.
    24. present: Coded: geographic reference appears.
    25. present: Area is named.
  • Guidancepresent25/25

    Final assessment

    Present: G per notice.

    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: Avoid area, contact, or stay-aware guidance.
    2. present: Protective guidance present in this notice.
    3. present: Coded: audience actions stated.
    4. present: Safety instructions appear.
    5. present: Recipients told what to do in this notice.
    6. present: Coded: avoid area, contact, or stay-aware guidance.
    7. present: Protective guidance present.
    8. present: Audience actions stated in this notice.
    9. present: Coded: safety instructions appear.
    10. present: Recipients told what to do.
    11. present: Avoid area, contact, or stay-aware guidance in this notice.
    12. present: Coded: protective guidance present.
    13. present: Audience actions stated.
    14. present: Safety instructions appear in this notice.
    15. present: Coded: recipients told what to do.
    16. present: Avoid area, contact, or stay-aware guidance.
    17. present: Protective guidance present in this notice.
    18. present: Coded: audience actions stated.
    19. present: Safety instructions appear.
    20. present: Recipients told what to do in this notice.
    21. present: Coded: avoid area, contact, or stay-aware guidance.
    22. present: Protective guidance present.
    23. present: Audience actions stated in this notice.
    24. present: Coded: safety instructions appear.
    25. present: Recipients told what to do.
  • Timepresent25/25

    Final assessment

    Present: T per notice.

    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: Time-of-day or weekday recency.
    2. present: Timing cue present in this notice.
    3. present: Coded: when information appears.
    4. present: Recency language present.
    5. present: Temporal cue exists in this notice.
    6. present: Coded: time-of-day or weekday recency.
    7. present: Timing cue present.
    8. present: When information appears in this notice.
    9. present: Coded: recency language present.
    10. present: Temporal cue exists.
    11. present: Time-of-day or weekday recency in this notice.
    12. present: Coded: timing cue present.
    13. present: When information appears.
    14. present: Recency language present in this notice.
    15. present: Coded: temporal cue exists.
    16. present: Time-of-day or weekday recency.
    17. present: Timing cue present in this notice.
    18. present: Coded: when information appears.
    19. present: Recency language present.
    20. present: Temporal cue exists in this notice.
    21. present: Coded: time-of-day or weekday recency.
    22. present: Timing cue present.
    23. present: When information appears in this notice.
    24. present: Coded: recency language present.
    25. present: Temporal cue exists.
  • Impactpresent25/25

    Final assessment

    Present: I per notice.

    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. present: Harm, smoke, blockage, or unfounded severity.
    2. present: Impact language present in this notice.
    3. present: Coded: consequence indicated.
    4. present: Severity appears.
    5. present: Outcome for people or area stated in this notice.
    6. present: Coded: harm, smoke, blockage, or unfounded severity.
    7. present: Impact language present.
    8. present: Consequence indicated in this notice.
    9. present: Coded: severity appears.
    10. present: Outcome for people or area stated.
    11. present: Harm, smoke, blockage, or unfounded severity in this notice.
    12. present: Coded: impact language present.
    13. present: Consequence indicated.
    14. present: Severity appears in this notice.
    15. present: Coded: outcome for people or area stated.
    16. present: Harm, smoke, blockage, or unfounded severity.
    17. present: Impact language present in this notice.
    18. present: Coded: consequence indicated.
    19. present: Severity appears.
    20. present: Outcome for people or area stated in this notice.
    21. present: Coded: harm, smoke, blockage, or unfounded severity.
    22. present: Impact language present.
    23. present: Consequence indicated in this notice.
    24. present: Coded: severity appears.
    25. present: Outcome for people or area stated.

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

About this analysis
Context

Background

On 2025-07-29, Duke University posted a public safety notice via Duke Today, the university's public news and safety communications channel also indexed from Campus Police news/RSS.
Analysis

Key Findings

Official university-published safety notice with complete public text
Captured for Ivy Plus deep pass from Duke Today / police RSS index
Outcome
See official notice for status and guidance.
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
  2. Official
  3. official
Cite this case

Campus Alert Archive. "Duke University: Public safety advisory after a stabbing on Douglas Street near Medical Center." Incident of July 29, 2025. Added July 2026. https://campusalertarchive.com/case/duke-university-douglas-street-stabbing-advisory-2025-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
aggravated-assaultstabbingshots-firedcommunity-notificationdukedurhamUnder Investigation
Added July 2026Updated July 2026Via ingestion