A municipal permitting office finished building a new agent. What should it do before staff rely on it in production?

Before staff rely on a new agent in production, the municipal permitting office should route the agent through the municipal approval workflow. Built is not the same as approved: production reliance requires the governance checkpoint that validates access, grounding, instructions, and risk. Completing approval before dependence protects permitting operations from an unreviewed agent giving wrong status guidance to clerks or residents.

Sharing the new agent with staff makers for collaborative editing before production reliance fails by concept—collaborative editing enables further co-authoring, not governance approval, and staff should not depend on an unreviewed agent that has only been shared for editing. Saving the new agent to the municipal library for team reuse before production reliance fails on governance and process: library placement promotes broader reuse without the approval checkpoint that validates access, grounding, instructions, and risk. Publishing the new agent to the staff showcase channel for discovery before production reliance fails because discovery is not approval; making an unreviewed agent discoverable still leaves staff relying on an agent that reviewers have not validated first.

Exam caveat: AB-900 Domain 3 includes agent approval before production reliance. Prefer the approval-workflow action over any choice that shares with staff makers for collaborative editing, saves to the municipal library for team reuse, or publishes to the staff showcase channel for discovery before approval. Do not equate "finished building" with "safe for production."

Operational check: Submit the permitting agent to the municipal approval workflow with owners, knowledge sources, and access groups listed; complete reviewer sign-off; retain logging/audit evidence; only then designate the agent for production staff use and monitor early invocations for unexpected answers.