Locking a site

The person says: “Lock the venue site through the launch; nobody changes anything.”

A locked site keeps serving visitors; every change to it, from every door (agents, chat, the CLI), is refused with the reason until it is unlocked. Locking and unlocking need an Admin.

The loop

1. Empress:site_status — what is open on the site: a staged release or an open change set will not go live while it is locked. Say so before locking.
2. Empress:site_call — tool: "empress.site_lock", args: { reason } in the person’s words.
3. Empress:site_status — the site reads as locked, with who locked it and why.
4. Empress:site_call — tool: "empress.site_unlock", when the person says the freeze is over.

Judgment

• Lock with a reason. The reason is what the next person (or agent) reads when a change is refused.
• Locked is not down. Visitors and reads keep working; only changes stop.
• A refusal for a locked site is not an error to route around. Tell the person, and who can unlock.