Streetlight IoT telemetry including home-adjacent location pings is pasted into a public model to “summarize blockers.” What should the Team Coach stop?
Select an answer to reveal the explanation.
Short Explanation
Home-adjacent streetlight pings are people's locations wearing a sensor badge. A public chatbot is not a city privacy vault. Summarize blockers with approved tools, or do it by hand—do not leak the feed.
Full Explanation
Streetlight IoT telemetry that includes home-adjacent location pings must stay out of unapproved public models. The Team Coach should stop pasting citizen telemetry and other PII into unapproved tools and use only responsible, approved AI practices. A standup-summary shortcut does not override privacy, records, or security policy on a municipal ART; home-adjacent pings are people's locations wearing a sensor badge.
Continuing to paste telemetry because public models are "already trained on city data" fails because assumed prior exposure is not authorization for new disclosures. Anonymizing nothing and adding parcel owner names fails because it increases, rather than reduces, sensitive content in the prompt. Uploading the full citizen location feed to any chatbot that promises a faster standup fails because vendor marketing is not an approved processing path.
Exam caveat: responsible AI for SM/TC work is enablement plus guardrails—speed never licenses PII leakage. Operational check: halt public-model pastes of telemetry, switch blocker summaries to approved tools or manual facilitation, scrub prompts of location and identity fields, and brief the streetlight team on the approved AI path before the next iteration.