Sunday, August 10, 2025

The Wonderland Murders: A Forensic-Grade Strategic Investigation into John Holmes, Eddie Nash, and the Weaponized Gray Zone

Post #3: Wonderland — Dispatch-Log Deep Dive (Teaser & Method)

Post #3 — Dispatch-Log Deep Dive (Teaser & Method)

By Randy Gipe & ChatGPT — follow-up to Part I: Forensic Strategic Review and the follow-up thread.


We’ve mapped the actors and the anomalies. Now we go after the timing: the minute-by-minute decisions (or non-decisions) that turned a homicide into a contained event. This post explains exactly what we’ll publish next and how you can help get the dispatch logs we need.

Why dispatch logs matter: They record who was asked to do what and when—dispatch times, unit assignments, call taker notes, and any supervisor directives. A 30-minute delay in orders or a redirection in assignments can be the difference between an arrest and a preserved asset.

What we’re looking for (concrete)

  • Dispatch call timestamp for 8763 Wonderland Avenue (who called, time received).
  • First responding unit — badge number, arrival time, initial actions taken.
  • Detective assignment sheet — who was assigned to the investigation and when.
  • Any supervisor directives or inter-unit messages (e.g., “stand down,” “hold action,” or redirections to other priorities).
  • Warrant execution logs — were any warrants for Nash properties requested/executed in the first 72 hours? If not, why?

Sample dispatch-log excerpt (mock, illustrative)

07/01/1981 07:12 — Call received (unknown caller) — report of multiple injured at 8763 Wonderland Ave.
07:13 — Unit 12A dispatched (Patrol) — ETA 07:21
07:16 — Unit 44B (Narcotics) notified (info: possible drug-related incident) — no immediate detective assignment in CAD
07:22 — First officer on scene (12A) reports multiple deceased — requests homicide unit
07:25 — Homicide notified — no supervisor message recorded in CAD that orders warrants on related addresses
07:50 — Unit 44B reports known connection to suspected Eddie Nash — message: "recommend follow-up" — no dispatch to execute search warrant

If the real log looks anything like the mock above (a gap between knowledge of Nash linkage and immediate warrant initiation), that gap is a high-value anomaly.

What we’ll publish next

  1. Side-by-side real dispatch excerpts with our annotated timeline (we’ll redact personal identifiers as required).
  2. Analysis of any supervisor messages that suggest containment or rerouting of priorities.
  3. Dispatch-to-action delta chart: time from call → first officer → homicide unit → warrant initiation (visualized).

How you can help

If you want to help accelerate this, here’s how:

  1. File a records request for LAPD CAD/dispatch logs for July 1–10, 1981 (we’ll post a copy/paste FOIA template shortly). If you want the template now, reply and I’ll post it here.
  2. Search newspaper microfilm for the first 48 hours of reporting — note timestamps of published facts vs. what later records show (helps identify narrative seeding).
  3. Share this post with retired LAPD, local journalists, or anyone who worked in city dispatch/records in the early 1980s — they may remember how the CAD system logged messages and if any messages were “pulled” from record-keeping.

Next steps from our end

We will:

  1. Draft and publish the FOIA dispatch-log template in the next 24 hours.
  2. Begin ordering court transcripts already publicly available (Holmes contempt hearing; Nash 1990 terminology) and post key snippets where allowed.
  3. Publish the annotated dispatch timeline as soon as logs are obtained — or as they arrive from public requests.
Quick reminder: We separate fact from inference. When we publish dispatch logs, we’ll annotate facts (timestamps, unit numbers) and keep our strategic interpretation clearly labeled as inference — so readers and officials can see exactly where the gaps occur.

If you want the FOIA template now, say the word. Otherwise: watch this space — Post #3 will be the first public place to show LAPD timing vs. action in the Wonderland case.


— Randy Gipe & ChatGPT

No comments:

Post a Comment