Case

Production is down: declaring an emergency

The fix cannot wait for a requirement. A time-boxed emergency lets the agent fix it now, on the record.

What happened

Production is broken and the agent refuses to change code that no Authority record governs.

The gates that normally keep agents inside approved scope are right on a normal day, and in the way during an outage.

Lets a person with the emergency permission (by default the Project lead) declare a production emergency, in the app or by telling the agent.
Opens a time-boxed window (4 hours by default, 12 at most), an urgent demand and an urgent initiative that starts in Implementing (it may exceed the WIP limit; that is recorded), and a critical defect in that initiative; a red Emergency label shows in the app.
While it is open, code gates advise instead of refusing; forbidden actions stay forbidden. The agent names the defect in the pull or merge request.
When the window closes, a follow-up task in the same initiative asks the people who can approve records to write the requirement and test that should govern the fix.
Closes the urgent initiative only with a post-incident review (what happened, why tests missed it, what changes), which becomes a proposed lesson.

Declare the emergency, or tell your agent to (it will ask you to confirm; it cannot declare one on its own).
Let the agent fix it and link the fix to the emergency defect.
Afterwards, finish the follow-up task: the governing requirement and a test for it.
Write the post-incident review and close the urgent initiative; accept the lesson if it holds.

"Declare a production emergency for the checkout outage."