Make a show-stop decision

On the event page (/event), open the ShowStop section and set two things:

• The authority matrix — who is allowed to declare a show-stop and who must witness or countersign it. This encodes your chain of command so a decision can't be made (or can't be finalized) by the wrong person.
• The trigger rulesets — the conditions that should surface a recommendation to the desk (severe weather, crowd, airspace, and so on).

During the event, ShowStop surfaces live recommendations on the Live Monitor when a trigger's conditions are met. A recommendation is advisory — it tells the desk "this warrants a decision" and points at the signals behind it. It never stops the show on its own; a human with authority makes the call.

An authorized operator declares the decision — stop, delay, abandon, or postpone — with the rationale. Each decision is hash-chained to the one before it: the record is tamper-evident, so anyone reviewing it later can verify the sequence wasn't altered. Where the authority matrix requires it, a second named person countersigns before the decision is final.

Every declaration for an event lands in its Decision Ledger (/decisions) — the immutable, ordered chain of what was recommended, decided, by whom, and when. This is the per-event system of record. From here you can seal a binder using the built-in templates (insurer, Martyn's Law, board report) to produce the external-facing document.

The Decisions portfolio — the Stop tab in your dashboard switcher (/decisions-portfolio) — rolls every event's decisions up across your org tree. It's the view for a director asking "what calls did we make across the season, and where?" without opening each event one at a time.