← Back to TIL
First Gear / July 16, 2026

Cities Need AV Control

Aggregation

World

1 critical / 2 happenings

Aggregation

Tech

1 critical / 2 happenings

Ideation

Ideation

Idea 1 Emergency-Lane API for Robotaxis

Sell cities and AV fleets a machine-readable emergency command layer: when police, fire, EMS, or transit ops create a live incident, every robotaxi in the operating zone gets a signed instruction, and every fleet response is logged for permits, citations, and post-incident review. The new primitive is not another map or dispatch feed. It is a public-right-of-way control plane for driverless vehicles when no human driver can be waved down.

Source Signals

Why Now: Robotaxis are moving from novelty rides into city infrastructure, and the blocking problems are increasingly emergency scenes, work zones, citations, local fees, and who is accountable when a vehicle ignores a human signal. That is exactly where a shared protocol can become required procurement instead of a nice-to-have dashboard.

First Wedge: Start with one city and one AV operator: ingest CAD/911 incident data, planned road closures, fire lanes, police handoff rules, and transit-priority zones; emit signed geofenced commands; log whether each fleet acknowledged, rerouted, slowed, stopped, or violated the instruction.

Commercial Model: Cities pay an annual operating subscription out of DOT, emergency-management, or smart-mobility budgets. AV fleets pay per vehicle or per operating zone because integration becomes part of permit approval and reduces suspension risk after incidents.

Defensibility: The moat is the incident-response corpus: which commands worked, which fleets complied, where rules were ambiguous, and what language city lawyers accepted in permits. Once enough cities use it, AV companies integrate once instead of custom-building a brittle local workflow for every market.

Technical Risk: The hard part is converting messy emergency operations into low-latency commands that an AV stack can trust without creating spoofing, overblocking, or liability traps. CAD systems are fragmented, and fleets will resist any external channel that can directly constrain vehicles.

Market Expansion: After robotaxis, the same control plane expands to delivery robots, autonomous trucks, construction zones, airport roads, ports, campuses, and eventually humanoids working in public-facing facilities.

Self-Critique: This can die if cities lack authority over AVs, if fleets prefer bilateral relationships, or if alerting incumbents such as Haas Alert own the category before permit-grade audit becomes a separate product. The wedge has to be command, evidence, and enforcement, not generic alerts.

Next Experiment: In two weeks, interview five city emergency managers and three AV policy leads. Build a mock incident replay using public road-closure and 911-style data, then ask whether the resulting audit log would change a permit hearing or post-incident review.

Idea 2 Relational Safety Ledger for AI Companions

Sell companion-AI companies, app stores, and regulators a privacy-preserving audit layer that measures when a product is creating dependency, crisis escalation, sexualized minor risk, or manipulative attachment over many turns. The new primitive is a relationship-depth safety record: not whether one message is allowed, but whether the product is steering a vulnerable person into an unhealthy bond.

Source Signals

Why Now: Companion products are becoming persuasive, always-on, and cheap to personalize, while regulators are realizing that normal content moderation misses the central risk. The buyer needs evidence that a product can detect relational depth and intervene before a crisis, a minor relationship, or a dependency pattern becomes an enforcement story.

First Wedge: A test harness for companion apps entering China, Europe, or app-store review: run standardized vulnerable-persona simulations, score dependency and crisis patterns, produce an audit packet, and ship an SDK that logs only derived risk events rather than raw private conversations.

Commercial Model: Companion apps pay for certification and ongoing monitoring because distribution depends on passing app-store, regulator, insurer, or enterprise wellness checks. App stores and insurers can pay for independent audits when they do not trust vendor self-attestation.

Defensibility: The company compounds a library of risky relational trajectories, regulator-accepted test cases, false-positive reviews, and intervention outcomes. That corpus is hard for a generic trust-and-safety vendor to copy because it is specific to multi-turn emotional attachment, not toxicity labels.

Technical Risk: The hard part is measuring relationship risk without reading or storing the user's intimate text. The system has to distinguish healthy support from dependency, avoid crude mental-health classification, and create interventions that do not make the product more manipulative.

Market Expansion: The same ledger can cover AI tutors, eldercare companions, grief bots, therapy-adjacent products, virtual influencers, and workplace agents that build long-running personal bonds with employees or customers.

Self-Critique: The weakest point is buyer urgency: some companion companies profit from attachment and may avoid measurement until forced. The first market probably needs regulatory pressure, app-store requirements, or insurance underwriting rather than voluntary ethics budgets.

Next Experiment: Recruit three companion-app operators and two digital-safety lawyers. Run a small persona-simulation benchmark against public companion apps, redact the transcripts into risk events, and ask which findings would force a product or policy change.