Ops staff update prompts and knowledge content for a city assistant frequently. How should those changes be controlled?
Select an answer to reveal the explanation.
Short Explanation
City change control isn’t optional because the file is a prompt. Version model, prompt, and content updates the same way you version other official changes—so you can roll back and explain what shipped.
Full Explanation
When ops staff update prompts and knowledge content for a city assistant frequently, those changes should be versioned like other controlled city changes. Prompts and grounding content are production configuration that shape resident-facing advice; uncontrolled edits create untraceable regressions and weak audit response after incidents. Versioning enables review, rollback, and explanation of what changed when a wrong answer appears. Allowing undocumented hotfixes in production with no history fails basic change control and makes root-cause analysis guesswork. Banning all updates after go-live to avoid governance overhead fails because civic knowledge and policies change; freeze policies trade governance theater for stale harmful answers. Letting each clerk edit production prompts independently without review fails by multiplying inconsistency and unauthorized policy interpretation. Exam caveat: generative systems tempt teams to treat text tweaks as informal; exam answers insist they are controlled changes. Operational check: store prompts/content in version control or a change system, require peer/policy review for production pushes, tag releases, and practice rollback during drills.