The Missing Origin Complaint
The complaint that initiated Case 23-009185 was filed in March 2023 under 311 ticket number 230317-1609966. This ticket does not appear in the City's 311 data export. The record that should establish the origin of the case — who filed it, what they reported, and how it was categorized — is absent from the dataset provided.
The existence of this ticket is confirmed by a later reference: a November 7, 2023 complaint entry explicitly cites ticket 230317-1609966 as the prior filing. The ticket existed. It simply is not in the export.
311 Activity Timeline
March 17, 2023
Original complaint filed — ticket
230317-1609966 Missing from exportApril 12–17, 2023
Earliest entries present in the 311 export. These are solid-waste complaints — not the original code-enforcement intake. The case was already open by this point; these are secondary filings.
November 7, 2023
New complaint entry references the missing ticket
230317-1609966, confirming its prior existence in the system.2024 — Full Calendar Year
Zero 311 activity. No complaints, no follow-ups, no status updates appear for the entire year. Gap
September 19, 2025
Cluster of 3 calls in 6 minutes. One of the three was placed via GoogleAI. Anomaly
Summary of Gaps
| Issue | Detail |
|---|---|
| Origin complaint missing | Ticket 230317-1609966 (March 2023) absent from City's 311 export |
| Full-year silence | Zero 311 records for all of 2024 |
| Burst cluster | 3 calls in 6 minutes on September 19, 2025; one via GoogleAI |
| Export begins late | Earliest available entries are April 12–17, 2023 (solid-waste category, not original intake) |
The missing origin ticket means the foundational document of this case — the initial complaint — cannot be reviewed, verified, or audited from the data the City has provided.