Scenarios
A scenario page starts from the situation as the buyer describes it, names the articles and the role that apply, and ends with three things: the sequence of work in the order the protocols run it, the evidence the situation ends with, and the consequence of inaction with its article reference. Every date on a scenario renders from the regulation data In force. The pages are grouped by the role hub they belong to; each hub on /for/ lists its own.
Scenario pages by role
How a scenario is written
Each page rests on the obligation records behind /obligations/, the versioned protocols on /methodology/ and the deliverable specifications on /deliverables/. It names the service that runs the work within the limits at what we cannot do, the guides that give the procedure, and the tools that prefill the obligation set. No scenario describes an engagement or an outcome; it describes what the Act asks for in that situation and what evidence answers it.