San Diego Smart City

Original stage labels are preserved. Unverified patterns are research audit entries, not deployments.

[]

# San Diego — Smart City Dispatch v0.2.3 research report

**Status:** PROVISIONAL RESEARCH · prepared 2026-10-11 · **2B — provisional**
**Boundary:** City of San Diego municipal limits; do not conflate San Diego County or regional service areas.

**Scores:** Type 17.92 (exact 17.91666666666666666666666667); Autonomy 9.58 (exact 9.583333333333333333333333334).
**Conclusion:** San Diego qualifies provisionally as Type 2 through material driverless mobility and AI-assisted nonemergency public safety; Level B reflects nonemergency decision assistance. Driverless rides are a single C-capable service domain and do not justify Level C alone.

## Source audit
Discovered: 12; examined: 10; accepted: 10; rejected: 0; inaccessible: 2; distinct publisher families: 5. These are this research edition's unique original URLs, not historical Sites search totals.

## Eight-domain decision table
| Bucket | Type winning technology | T,c,g | Type pts | Autonomy winning technology | A,c,g | Autonomy pts |
|---|---|---|---:|---|---|---:|
| MOB | TECH-001 | 2,.65,1 | 5.42 | TECH-001 | 2,.65,1 | 5.42 |
| ENG | — | —,—,0 | 0.00 | — | —,—,0 | 0.00 |
| WAT | — | —,—,0 | 0.00 | — | —,—,0 | 0.00 |
| BLD | — | —,—,0 | 0.00 | — | —,—,0 | 0.00 |
| SAF | TECH-002 | 2,1,1 | 8.33 | TECH-002 | 1,1,1 | 4.17 |
| ENV | — | —,—,0 | 0.00 | — | —,—,0 | 0.00 |
| GOV | TECH-003 | 1,1,1 | 4.17 | TECH-003 | 0,1,1 | 0.00 |
| HLT | — | —,—,0 | 0.00 | — | —,—,0 | 0.00 |

**Sum, without per-domain rounding:** 17.92 Type, 9.58 Autonomy. The scoring formula is `100 × Σ_d 0.125 × max_i(g_i c_i T_i/3)` and its analogous A formula.
**Mandatory gates:** Type≥2 domains at T≥2 = ['MOB', 'SAF']; Autonomy C domains at A≥2 = ['MOB']. Result: Type2 True; autonomy C False. Type3 and D gates not demonstrated.

## Technology inventory, evidence and exclusions
### TECH-001 — Waymo public fully driverless robotaxi service
- **Bucket:** MOB; **status:** operating production; **T=2, A=2, c=.65, g=1**; scope N.
- Coverage evidence: Approximately 50 square miles inside city at September public launch, several neighborhoods; initial invitations restrict actual rider penetration.
- Human authority / actuation: Vehicle autonomously selects steering, braking, routing within service constraints; remote oversight. Autonomous vehicle movement, pickup/dropoff decisions.
- Basis and limitations: N is provisional: require active vehicle counts and trips/municipal denominator, not just map footprint. Sources: SRC-001;SRC-002.
### TECH-002 — Police nonemergency AI voice triage and dispatcher insights
- **Bucket:** SAF; **status:** operating production; post-June renewal unverified; **T=2, A=1, c=1, g=1**; scope W.
- Coverage evidence: City of San Diego Police Department nonemergency call service, available to callers across municipal jurisdiction.
- Human authority / actuation: Voice AI intake categorization and recommendations; humans handle emergency dispatch and response. Voice routing and transcription; no independent emergency dispatch.
- Basis and limitations: W is service eligibility coverage, not measured penetration. Continuity in October not independently verified. Sources: SRC-003.
### TECH-003 — Get It Done municipal issue intake and CRM
- **Bucket:** GOV; **status:** operating production; **T=1, A=0, c=1, g=1**; scope W.
- Coverage evidence: More than 65 services; 1,000+ municipal requests per day.
- Human authority / actuation: Citizen submits; staff/defined workflow triages and resolves. Routine form/service routing.
- Basis and limitations: No evidence that AI decides city-service operational actions. Sources: SRC-006;SRC-007.
### TECH-004 — City coordinated signal controllers
- **Bucket:** MOB; **status:** operating production; **T=1, A=0, c=1, g=1**; scope W.
- Coverage evidence: Over 1,600 city intersections; coordination along major corridors.
- Human authority / actuation: Preset timing/coordinated plans with local detection. Fixed/triggered signals.
- Basis and limitations: No broad evidence of autonomous strategy selection. Sources: SRC-005.
### TECH-005 — Mira Mesa adaptive signal corridor
- **Bucket:** MOB; **status:** operating historically; current detail unverified; **T=2, A=1, c=.35, g=0**; scope D.
- Coverage evidence: Approximately 4.34 miles in four phases in District 6, not citywide.
- Human authority / actuation: Traffic responsive signal timing within existing corridor. Adaptive timing along corridor (historical report).
- Basis and limitations: g=0: limited district deployment and current operation not reverified. Sources: SRC-004.
### TECH-006 — Smart streetlight surveillance and ALPR cameras
- **Bucket:** SAF; **status:** operating production; **T=1, A=0, c=.65, g=1**; scope N.
- Coverage evidence: Multiple city neighborhoods, report references up to 500-unit program.
- Human authority / actuation: Investigators query vehicle/scene evidence; no independent policing action. Automated capture/plate reading; no physical autonomous response.
- Basis and limitations: Safety and civil liberties limitations; human case decisions. Sources: SRC-008;SRC-009.
### TECH-007 — Automated water meter rollout / AMI
- **Bucket:** WAT; **status:** partial rollout; verified coverage unavailable; **T=1, A=0, c=.15, g=0**; scope P.
- Coverage evidence: Project plan approximately 280k meters citywide, exact installed counts not verified.
- Human authority / actuation: Meter reading/threshold leak alarms only. Meter data transmission.
- Basis and limitations: Budget source original was not retrievable; no score until verified N/W coverage. Sources: SRC-011.
### TECH-008 — Pure Water San Diego Phase 1 infrastructure
- **Bucket:** WAT; **status:** under construction / not scored; **T=1, A=0, c=.15, g=0**; scope P.
- Coverage evidence: City plans 30 million gallons/day Phase 1 capacity, not yet verified produced.
- Human authority / actuation: Conventional treatment control; no verified independent operation of completed Phase 1. 
- Basis and limitations: Future planned capacity has no operating score. Sources: SRC-010.

## Why not a higher classification
Type 3 requires three distinct material T3 service domains and a score≥30; not demonstrated. Level D requires three independent goal-directed adaptive domains and score≥30; not demonstrated.
this city has confirmed candidate autonomous mobility but no second distinct service domain satisfying the full test.

## Sensitivity, limitations, editorial check
If the newly launched restricted-access Waymo network fails the N substantial operating service test, the Type 2 breadth gate fails (only SAF proves T≥2), and the working class falls to Type 1/B; numeric MOB contribution would be removed. Police AI contract renewal also requires verification.
Confirm whether newly launched robotaxis provide sufficient regular ridership and route density to qualify for N; independently confirm SDPD call-agent continuation after its June 2026 renewal date.

## Source provenance
- SRC-001 [Welcoming our first riders in Denver, San Diego, and Tampa](https://waymo.com/blog/2026/09/ride-in-denver-san-diego-tampa/) — accepted. Driverless public service started September 2026; initial access invite-based.
- SRC-002 [Waymo officially launches driverless rides in San Diego](https://www.axios.com/local/san-diego/2026/09/01/san-diego-robotaxi-public-rides-service-area-airport-highways) — accepted. Journalist reported initial approximately 50 square mile operating area; no airport or highways then.
- SRC-003 [AI is helping answer San Diego police calls](https://www.axios.com/local/san-diego/2026/05/04/ai-san-diego-911-calls) — accepted. Contract examined by reporter; AI handles NONEMERGENCY intake, not autonomous emergency dispatch; renewal after June uncertain.
- SRC-004 [District 6 Smart Stoplight System](https://www.sandiego.gov/citycouncil/cd6/smart-stoplight-system) — accepted. 2016-2019 corridor project; not citywide or current system status confirmed.
- SRC-005 [Traffic Signals](https://www.sandiego.gov/street-div/services/electrical/trflight) — accepted. >1,600 controlled intersections; much is conventional coordination and timers.
- SRC-006 [Ten Years of Getting It Done](https://www.insidesandiego.org/ten-years-getting-it-done-city-san-diego) — accepted. >1,000 requests/day; >65 services; 3.5m reports cumulative.
- SRC-007 [Get It Done current service system](https://www.sandiego.gov/panda/projects/get-it-done) — accepted. Digital public-service intake and routing; human/ordinary workflow, not independently optimizing.
- SRC-008 [2024 surveillance annual report revised March 2026](https://www.sandiego.gov/sites/default/files/2026-03/sdpd-annual-surveillance-report-2024-revised-260306.pdf) — accepted. Reports installed ALPR and camera systems; does not imply automated decision authority.
- SRC-009 [2024 surveillance cameras investigative use](https://www.sandiego.gov/mayor/smart-streetlight-license-plate-reader-helping-solve-crimes) — accepted. Operational cameras assist investigators, not autopilot for police actions.
- SRC-010 [Pure Water Phase 1 projects](https://www.sandiego.gov/public-utilities/sustainability/pure-water-sd/phase-1-projects) — accepted. Construction project schedule and targets; do not claim completed water plant operation.
- SRC-011 [FY2026 budget: Smart Metering Infrastructure project](https://www.sandiego.gov/sites/default/files/2025-08/fy26ab_full.pdf) — inaccessible. Web search excerpt mentions continuing rollout to ~280k meters but PDF read failed; not accepted as examined.
- SRC-012 [Waymo public service footprint](https://www.nbcsandiego.com/news/local/waymo-officially-launches-to-the-public-in-san-diego/4068069/) — inaccessible. Original page retrieval failed; independent reporting available via Axios.

## Scope and import rules
This is a research edition. Match existing canonical SCD city records, retain the source/technology/evidence IDs with edition-specific namespacing, preserve earlier versions, and recalculate deterministic scores before publishing. Do not treat search snippets or inaccessible PDFs as examined source material. Do not treat a score of 0 in an unsupported domain as proof of traditional/manual infrastructure.
21 capability tags describe technologies; they do not alter eight independent 0.125 scoring buckets. No inferred duplicate credit across systems.