A verified connected-Drive PDF titled “160.pdf,” filed under Court Docs › Scofield v. Guillard. The authorized folder context identifies it as part of court filings and related litigation records organized by jurisdiction or proceeding. This record preserves the original source link, filename, folder placement, media type, byte size, and Drive dates. Content-level facts are not inferred from the filename alone; exact quotations, image interpretation, named participants, event dates, exhibit identifiers, and conclusions require review of the linked original.
A verified connected-Drive PDF titled “161.pdf,” filed under Court Docs › Scofield v. Guillard. The authorized folder context identifies it as part of court filings and related litigation records organized by jurisdiction or proceeding. This record preserves the original source link, filename, folder placement, media type, byte size, and Drive dates. Content-level facts are not inferred from the filename alone; exact quotations, image interpretation, named participants, event dates, exhibit identifiers, and conclusions require review of the linked original.
A verified connected-Drive PDF titled “162.pdf,” filed under Court Docs › Scofield v. Guillard. The authorized folder context identifies it as part of court filings and related litigation records organized by jurisdiction or proceeding. This record preserves the original source link, filename, folder placement, media type, byte size, and Drive dates. Content-level facts are not inferred from the filename alone; exact quotations, image interpretation, named participants, event dates, exhibit identifiers, and conclusions require review of the linked original.
A verified connected-Drive PDF titled “165.pdf,” filed under Court Docs › Scofield v. Guillard. The authorized folder context identifies it as part of court filings and related litigation records organized by jurisdiction or proceeding. This record preserves the original source link, filename, folder placement, media type, byte size, and Drive dates. Content-level facts are not inferred from the filename alone; exact quotations, image interpretation, named participants, event dates, exhibit identifiers, and conclusions require review of the linked original.
A verified connected-Drive PDF titled “166.pdf,” filed under Court Docs › Scofield v. Guillard. The authorized folder context identifies it as part of court filings and related litigation records organized by jurisdiction or proceeding. This record preserves the original source link, filename, folder placement, media type, byte size, and Drive dates. Content-level facts are not inferred from the filename alone; exact quotations, image interpretation, named participants, event dates, exhibit identifiers, and conclusions require review of the linked original.
A verified connected-Drive PDF titled “56-1.pdf,” filed under Court Docs › Scofield v. Guillard. The authorized folder context identifies it as part of court filings and related litigation records organized by jurisdiction or proceeding. This record preserves the original source link, filename, folder placement, media type, byte size, and Drive dates. Content-level facts are not inferred from the filename alone; exact quotations, image interpretation, named participants, event dates, exhibit identifiers, and conclusions require review of the linked original.
The first WSU production installment begins with WSU Police incident 22-W4386 and materials concerning assistance to Moscow Police after Bryan Kohberger’s arrest. It documents warrant preparation and service for apartment G201 at Steptoe Village and an office in Wilson-Short Hall, scene security, personnel involved, property/evidence handling, related reports, later administrative processing, and supporting communications. The extraction also contains BOLO, vehicle, public-records, FERPA/redaction, and follow-up material; individual pages must be consulted before attributing a statement or evidence item to a particular author.
The fourth installment compiles WSU safety concerns, institutional communications, media-related correspondence, public-records handling, and investigative support. Visible examples include a parent’s November 22, 2022 questions about campus safety and academic options, a January 2023 message circulating a Kohberger internship-related video, and a January 2024 request concerning memorial coins for WSU Police staff who worked the Idaho Four response. The large production also references parking, LPR, warrant, and administrative records; each thread must be read with its own date and sender context.
The fifth installment continues WSU safety and investigative-coordination records. It includes WSU’s response to community safety concerns, discussion of increased patrols and critical-incident coordination, correspondence about providing campus video to Moscow Police, prosecutor and Washington Attorney General communications concerning WSU records warrants, and other investigative or administrative follow-up extending beyond the immediate arrest period.
The eighth and largest text installment compiles media requests, interview invitations, press releases, campus-safety communications, public-records correspondence, parking/LPR references, warrant-related material, and institutional messaging. Examples include a December 27, 2022 podcast invitation to WSU Police leadership, January 3 Moscow releases on extradition and nondissemination, and WSU communications describing increased patrols, safe-ride and escort resources, academic flexibility, and employee/student support after the homicides and arrest. Repetition and forwarded chains are substantial; each item’s sender, date, attachment, and status should be verified in the original.
This record indexes “social_media_results_2.pdf,” a PDF stored under “Pullman Social Media Records.” Connected extraction recovered 34,965 searchable characters. A sanitized full-text extraction is included for research and must be checked against the original layout.
This record indexes “social_media_results.pdf,” a PDF stored under “Pullman Social Media Records.” Connected extraction recovered 83,981 searchable characters. A sanitized full-text extraction is included for research and must be checked against the original layout.
This record indexes “bn_01225.png,” a social-media screenshot or image stored in the Social Media Archive section “Steve G & Brat Norton Messages.” The artifact is preserved for provenance, but searchable source text is withheld because this section may contain private communications, payment activity, anonymous accusations, health-related posts, harassment, or unverified account attribution. The record does not authenticate an account, identify a user behind a handle, or treat statements in the artifact as established facts.
This record indexes “bn_02225.png,” a social-media screenshot or image stored in the Social Media Archive section “Steve G & Brat Norton Messages.” The artifact is preserved for provenance, but searchable source text is withheld because this section may contain private communications, payment activity, anonymous accusations, health-related posts, harassment, or unverified account attribution. The record does not authenticate an account, identify a user behind a handle, or treat statements in the artifact as established facts.
This record indexes “bn_03265.png,” a social-media screenshot or image stored in the Social Media Archive section “Steve G & Brat Norton Messages.” The artifact is preserved for provenance, but searchable source text is withheld because this section may contain private communications, payment activity, anonymous accusations, health-related posts, harassment, or unverified account attribution. The record does not authenticate an account, identify a user behind a handle, or treat statements in the artifact as established facts.
This record indexes “bn_04905.png,” a social-media screenshot or image stored in the Social Media Archive section “Steve G & Brat Norton Messages.” The artifact is preserved for provenance, but searchable source text is withheld because this section may contain private communications, payment activity, anonymous accusations, health-related posts, harassment, or unverified account attribution. The record does not authenticate an account, identify a user behind a handle, or treat statements in the artifact as established facts.
This record indexes “v09044g40000c20uqbvrscu33260huv0.MP4,” a video/mp4 file stored under “TikToks Featuring Victims .” Drive confirms the file identity and size, but no reliable transcript, captions, speaker identification, or complete timestamp map was available through the connected extraction. The record therefore makes no action-level or dialogue-level claims and links to the original media for direct review.
Source file “Backdoor - Person Detected, 111322 326AM_Redacted.mp4” from Security Camera Footage › Eric Gower (Uber Driver) Ring Cam Footage. The original file remains in Google Drive. This entry indexes the supplied filename and folder placement; the recording itself has not been reviewed.
Source file “787 Indian Hills Dr. 326 AM (1min)_Redacted.mp4” from Security Camera Footage › 787 Indian Hills Drive. The original file remains in Google Drive. This entry indexes the supplied filename and folder placement; the recording itself has not been reviewed.
Source file “763 Indian Hills Dr. 326 AM (1min).mp4” from Security Camera Footage › 763 Indian Hills Drive. The original file remains in Google Drive. This entry indexes the supplied filename and folder placement; the recording itself has not been reviewed.
Source file “755 Indian Hills Dr. 326 AM (1 min ).mp4” from Security Camera Footage › 755 Indian Hills Drive. The original file remains in Google Drive. This entry indexes the supplied filename and folder placement; the recording itself has not been reviewed.
Source file “1112 King Rd 11.13.22_0800-0900_Redacted.mp4” from Security Camera Footage › 1112 King Road Footage. The original file remains in Google Drive. This entry indexes the supplied filename and folder placement; the recording itself has not been reviewed.
Source file “10___Entrance GROC_Friday January 6 2023200638 6a18636.avi” from Security Camera Footage › Walmart › 12 › 02 › 22. The original file remains in Google Drive. This entry indexes the supplied filename and folder placement; the recording itself has not been reviewed.
Source file “16___01 Action Alley Grocery Front to Back_Friday January 6 2023202252 b4e9c0e.avi” from Security Camera Footage › Walmart › 12 › 02 › 22. The original file remains in Google Drive. This entry indexes the supplied filename and folder placement; the recording itself has not been reviewed.