# No-Go Dates

> Build and keep the standing risk register for a technical event, with a go/no-go date before every cancellation-fee
> step-up, then write the printable emergency plan. Enter the event, what is signed and non-recoverable, the venue's
> fee schedule and the risks you see. Not legal or insurance advice. Built on the SkillSafe skill
> @samber/event-risk-management (samber/dev-event-organizer-skills, MIT).

https://no-go-dates.skillsafe.ai/

## What is free
- Each row mapped to a fifteen-row taxonomy drawn from documented cancellations, with the missing rows named (organizer financial capability, structural defection and organizer discretion are the forgotten three); a row deleted only with a reason.
- 5x5 likelihood x impact, impact raised by outdoor parts, alcohol, minors, rigging, pyrotechnics, hands-on hardware, overnight duration or a single-source dependency; green, yellow (needs a trigger), orange (needs a written contingency), red (immediate escalation); owner and review-date coverage; the register depth.
- The coverage ladder as categories to ask a licensed broker about - venue-required liability, cancellation (promoted past about a quarter of the budget committed, self-set), cyber, participant accident, non-appearance, parametric weather - with the communicable-disease buy-back as a recorded decision; the community pole with nothing committed deletes all but liability.
- A go/no-go date seven days before every fee step-up (self-set) with the cost of cancelling after it; thresholds fixed in advance and a polled call by condition; re-score dates.
- The unranked emergency scenarios, plus weather, alcohol, minors and hardware where they apply, and the overnight rota.
- Register CSV, Markdown and JSON exports, and the go/no-go dates as a calendar (.ics) file with a reminder the day before each.

## The metered lanes
Two tasks on gpt-terra, metered per run, routed by `task`. Input string fields: `task` (register or emergency), `event`, `register` and `facts`.
- `register` replies with `summary`, `disclaimer`, `depth`, `rows`, `missing`, `coverage`, `buyback`, `calendar`, `signals` and `caveats`; the page holds every score, band, status, date and cost to its own and refuses any statement that a policy covers a loss.
- `emergency` replies with `title`, `scenarios`, `contacts`, `distribution`, `advance`, `rota` and `note`; the page requires every scenario in order, the named contacts and the non-emergency line, no invented phone number, and a printed copy.

## Links
- API tutorial: https://no-go-dates.skillsafe.ai/api.html
- Source skill: https://skillsafe.ai/skill/@samber/event-risk-management