Engineers edit production system prompts for the transit assistant without tickets. What control alignment is missing?
Select an answer to reveal the explanation.
Short Explanation
Prod prompt edits without change tickets are shadow IT for brains—treat prompt promotions like any other high-impact config change. Incident triage, access reviews, or uptime monitoring aren't a pre-production change gate.
Full Explanation
Engineers editing production system prompts for the transit assistant without tickets are missing IT service-management change control for civic AI configuration promotions. System prompts, tool policies, and grounding settings are high-impact production configuration: an unreviewed edit can alter safety behavior, leak data via tool permissions, or change resident-facing guidance for routes and disruptions. Civic ITSM/change processes should gate promotions with peer review, testing evidence, rollback plans, and an auditable ticket trail—the same discipline applied to firewall rules or fare-system configs. Without change control, prompt edits become shadow configuration management, breaking governance, incident reconstruction, and accountability when transit riders are misled or safety filters weaken. Service-desk incident triage for civic AI transit service disruptions is a reactive operational process; it responds to outages after they happen and does not provide the pre-production change-control gate for prompt promotions. Privileged access review for civic AI platform operator accounts checks who can access the platform, but it does not require change tickets, approvals, or rollback plans before production prompt edits are promoted. Service-level availability monitoring for civic transit assistant response times measures performance after deployment, but it offers no pre-change review, ticket trail, or approval mechanism for prompt configuration changes. The missing alignment is a real ITSM gate before production promotion, not incident triage, privileged access review, or response-time monitoring. Exam caveat: service-desk triage, privileged access reviews, and response-time monitoring are operational controls, not the production change-control gate; look for controlled promotion of civic AI configuration. Operational check: require change tickets for production prompt/tool-policy edits on the transit assistant, enforce dual review for high-risk changes, and sample that prod prompt hashes match the last approved change record.