Raleigh’s Public-Safety Maze Needs a Concierge

A city can put a remarkable amount of information online and still make it hard to use.

You can find Raleigh police records, fire statistics, old incident summaries, inspection histories, and a public active-incident map. But each service has its own vocabulary, its own search form, and its own idea of what the result means. A resident arrives with a normal question. The city replies with a database.

That gap is where an AI can be genuinely useful. But public-safety data is where it has to know when to stop. It is not a police scanner, an emergency dispatcher, or a machine that turns a block-level incident row into a story about a person.

I introduced the Raleigh Agent Skill as a way for Ralwegians to begin with the question they actually have. Version 2 gave it more doors into the city’s digital maze. The new public-safety work takes that idea into places where a good answer needs a little more restraint.

I captured these examples late on July 26, 2026. They’re snapshots, not promises about what a public feed will say tomorrow.

First, what happened nearby?#

A person moving into a neighborhood might ask:

“What public police reports of burglaries were recorded in Raleigh this week?”

The concierge can take that question to the Raleigh Police Department’s public crime-data service and bring back this:

That’s context. Not a conviction, an arrest record, or a disposition. The locations are block-level, and the city may randomize or redact them. Leave the row there.

Why should you have to know that the city keeps several public police views, each with a different name? You don’t. Someone who wants the rolling 90-day CrimeMapper view of Downtown might ask:

“What has the public Downtown feed shown over the last week?”

And a morning-after question has a different route:

“What did the previous-day public police feed return?”

But it still can’t promise completeness. That feed can lag. “No records returned” is not the same as “nothing happened.”

Older records have a different shape again. Ask for older larceny reports, and the concierge can return them without treating redacted locations as a puzzle to solve:

The blank address is part of the answer. The concierge should leave it blank.

Sometimes a resident does not want incident rows at all. They want the official document the city published. This is a different request:

“Where can I find Raleigh’s official 2025 crime reports?”

The result links to the city’s annual and quarterly documents. It doesn’t add up a different public feed and pretend the result is official.

Fire records answer a different question#

Fire data carries another kind of temptation: seeing a few records and assuming that they describe every department response. They do not.

A resident could ask:

“What has the public Raleigh Fire feed recorded over the past week?”

The current public source returned:

The Raleigh Fire Department’s public incident layer has dispatch, arrival, clearance, station, and classification fields. It excludes EMS-related categories for privacy, though, so it is not a complete record of every RFD response. It is never a reason to delay calling 911.

Same public fields. Narrower question:

“For the records you found, how long was it from dispatch to arrival?”

Those are labeled durations for three records, not a citywide response-time verdict. That distinction sounds fussy until it prevents somebody from taking a few rows as a promise about their own emergency.

A property question travels through another public system. A Ralwegian considering an address can ask:

“What fire-protection information does the public Wake County record associate with 222 West Hargett Street?”

The Wake County public fire-protection record supplies those rankings and distances. The source doesn’t publish distance units, so the concierge doesn’t guess. And it doesn’t suggest which apparatus would respond to a real emergency. That’s dispatch’s job.

Published totals are not incident rows#

A person trying to understand the department at a larger scale might ask:

“What statistics has Raleigh Fire published for 2026?”

The Raleigh Fire Department’s statistics page returned these source-published counts:

That answer keeps an important wall intact. The public incident feed excludes some EMS-related records. The city-published medical total is an aggregate number, not a set of incident rows waiting to be reconstructed.

The skill also finds the documents behind the numbers:

“Show me Raleigh’s public fire-statistics report for the first quarter of 2025.”

The returned link points to the city’s published report. Again, the concierge doesn’t pretend it has numbers the document index hasn’t parsed.

A report summary is not a safety certificate#

Two more public services are useful, but only for narrow questions.

“What did the structured public fire summary show for July 24?”

That’s an abridged excerpt from the city’s rolling structured feed, not a claim that it has every record for that day. If you need help with a current gas odor, electrical hazard, or fire, call 911. Don’t search a public site.

The city also refers residents to its public Fire Report System. An installed concierge can search a specific business or address when someone asks:

“Does the public record list fire inspections for Raleigh Swim School?”

The city publicly refers residents to the RFD Report System, and its report site served the lookup over HTTP when I checked. The command requires --acknowledge-insecure-rfd for each lookup. And those inspection entries aren’t a safety certificate: they show only the entries returned by that search, not what happened beyond them.

What is active right now?#

The last new doorway is the most delicate one. Somebody might ask:

“What is the public active-incident map showing for Raleigh Police right now?”

On the evening I checked, the Raleigh-Wake Emergency Communications Center public map returned:

The map itself says its data is informational only. The skill goes further: it tells you this is a filtered public snapshot, says when it retrieved the records, and doesn’t pretend it represents every 911 call or the city’s authoritative emergency status.

That matters when the result is empty, too. A fire-filtered request in the same capture returned no active incidents. The right response is not, “Raleigh is clear.” It is, “No active incidents were returned by this filtered public feed at this moment.”

That is a better concierge. It knows that a blank page sometimes means a blank page.

The digital city should start with a question#

This is not a story about putting more surveillance in an AI chat window. Raleigh already publishes these records across separate services. The gap is that each one asks a resident to understand its own rules before asking a normal question.

The order matters. You ask about a move, a property, a historical pattern, a city report, or a public record. The concierge finds the right door, brings back the smallest answer that fits, and tells you where the evidence stops.

For Ralwegians, that’s a useful thing to install. For anyone facing an emergency, the answer is shorter: call 911.