Eighteen days after the briefing where council first learned its city had been running networked plate readers for two years, the first Real-Time Intelligence Center funding came to a vote, as consent agenda item G. This page reconstructs how, from the March 21 agenda-review video and the March 25 meeting video. Captions don’t label speakers; attributions follow meeting context.
How it got on consent (March 21, 6:44)
At the agenda-review briefing four days earlier, staff previewed the item in one breath:
“Items G, H and I are recurring grants that APD applies for annually… these three grants help fund the real-time intelligence center, bulletproof vests for officers, and then DEA… activities.”
The RTIC’s first funding, introduced between body armor and drug enforcement, labeled routine. Then: “any other questions on consent or anything I missed?… great, I’m going to keep moving.” No questions. On March 25, the opacity worked exactly as designed: mid-comment, the clerk had to explain to residents what item G even was (22:43). Staff also acknowledged the only prior council-adjacent discussion had been an informational committee session on September 24, 2024, three days before Helene, with no vote (45:09). This maneuver has a name on this site: see the tactics table in the Claims Library, and The Check-In Meetings for where the real deliberation happens.
The public saw it anyway (20:31)
Residents pulled the item into the light. One commenter, identifying as a former lawyer: “A lot of this stuff is arguably unconstitutional… at the end of this, they had the mayor saying, ‘If we build it, they will come. If you pass this, ICE will come.‘” Another: “I just don’t believe that it won’t be accessible to federal organizations… It could be used to locate undocumented people… track people seeking feminine healthcare.” March 2025. Both predictions came true within the year: Who Gets Watched.
”I kind of feel robbed” (30:00)
Councilmember Sheneika Smith, on the record, before voting:
“We usually have this conversation during Public Safety, so we can ask all the questions and get feedback from the community as well as our law enforcement professionals — but I kind of feel robbed of having those conversations in this decision tonight.”
Kim Roney went further (30:45): citing “significant legal and social concerns about real-time intelligence and companies like Fusus, including 29 questions I compiled and submitted to staff and my colleagues on council in the absence of… advisory committee meetings,” she said legal experts agreed “more time is needed for analysis” and recommended delaying the vote: “especially around the security of data and privacy of our residents and the implications of how this federally funded equipment might not be exclusively used by our staff.” The delay was refused. (Her 29 questions and the city’s answers remain a records target; see Documents.)
”We’re not buying surveillance. We’re buying chairs.” (32:30)
Councilmember Bo Hess carried the item:
“Just to be clear, the real-time intelligence center already exists. We’re not buying surveillance. We’re buying chairs and workstations for the officers to do their job.”
And again minutes later (35:06): the center “already exists… The funding buys basic infrastructure like desk, chairs, workstations. It’s already been established and has already helped apprehend dangerous individuals.”
Hess’s reassurance contains the admission: the surveillance center already existed (established and operating) before council’s first vote on it. And the “chairs” framing didn’t survive the meeting: Chief Mike Lamb, answering questions moments later (41:09), said “we do have a lot of the hardware that we need… We don’t necessarily have the Fusus software yet or the finalized agreement with Axon as far as managing the data.” The money wasn’t for furniture. It was the start of the software and contract spending council approved in full fourteen months later. (Bo Hess · Their Claims vs The Record)
The vendor-access question, dodged (39:02)
Roney asked the question that mattered: “do you share any concern that the data in other cities is showing that it will be potentially used not only by our police department, but can also be used by the company that we contract with?” Lamb’s answer described sharing with the sheriff’s office and local partners, and confirmed the architecture without addressing the concern (41:38): “all that data has to go within the Axon system so that it’s accessible to us, our officers, and also the district attorney’s office and legal partners.” Whether the vendor can use the data was never answered. (What Axon’s paper actually permits is documented in What Axon Contracts Do.)
The Ring-camera blueprint (42:09)
APD technology specialist Jimmy Wingo, explaining private-camera integration: “whether it’s businesses or the Ring camera at your home, it can be optioned to feed into the public’s real-time intelligence center data… There’s a registry, just so we know where a camera is in a city — and then there’s also one where you could provide us full viewing capability.” When Roney noted that courts elsewhere have compelled private footage, Wingo conceded: “if the court comes to your house and has a warrant for that Ring camera footage, then you would have to give it to us.” Business owners weighing that “option” should read Before You Plug In; residents of properties whose landlords already opted in, Watching the Poor.
The vote (46:18)
Items G1 and G2: moved by Hess (“I’m going to give the motion to Bo because he made such an impassioned speech,” the chair said), seconded, approved by hand vote, no roll call in the captions. The minutes (approved May 28, 2026; see Documents) are the only official record of who voted how. Two residents’ warnings, two councilmembers’ process objections, one requested delay, and the first RTIC money moved anyway, filed under “recurring.”
Related: Timeline · 2025-03-07 Agenda Briefing · 2026-05-12 City Council · Bo Hess · Claims Library · Oversight Theater