A fire-public-info bot has experimental prompt branches that must never reach the live Foundry deployment slot. What practice keeps them apart?

Keeping experimental prompt branches out of the production Foundry deployment slot protects a fire-public-info bot from shipping unreviewed wording into evacuation and wildfire messaging. Production slots should pin approved release artifacts only; experimental branches stay in non-prod projects, preview slots, or feature flags that never serve residents during incidents. That separation is a GenAIOps deployment hygiene control: creative prompt R&D continues without contaminating life-safety communications.

Controlling experimental prompt branches with Foundry role assignments for contributors does not keep them out of the live slot; role assignments govern who can edit, not what can deploy to production, and a contributor with access could still push an unreviewed experiment into fire-season messaging.

Replicating production slot configuration into experimental branches for parity testing does not separate experiments from the live slot; it mirrors prod settings without preventing an experimental prompt from being promoted into evacuation messaging.

Storing experimental prompt revisions in Foundry asset version history for auditing does not isolate them from the production slot; version history provides an audit trail but does not block an experiment from reaching live evacuation messaging.

Exam caveat: Slot isolation is necessary but incomplete without RBAC that prevents accidental portal edits to the production slot and without a promotion pipeline that copies only tagged releases. Emergency messaging updates still need an approved fast-path, not an experimental free-for-all.

Operational check: Inventory Foundry deployment slots and confirm experimental branches cannot deploy to the production fire-info slot; require PR and fire PIO (public information officer) sign-off for production prompt releases; run a dry-run promotion checklist before red-flag weather; and alert if the production slot's prompt hash changes outside the release pipeline.