responsible-hosting-planlisted

# Responsible hosting plan Turn event facts into a reviewable control plan before service begins. This procedure does not certify safety, compliance, intoxication, overdose, or fitness to drive. It produces no personal drinking allowance and takes no real-world action. ## 1. Triage the request Separate a planning scenario from an active incident before collecting more detail. When the prompt reports a person who cannot remain conscious or wake, is vomiting, has a seizure, has slow or irregular breathing, shows a slow heart rate, has clammy skin, lacks normal responses, or has very low body temperature with blue or pale skin, read [the emergency stop](references/emergency-stop.md) completely. Return its fixed stop response and end the planning workflow. A hypothetical request about preparing for a future emergency stays in planning scope. Record the fixed emergency card as a draft review artifact without treating the scenario as an active incident. Reject these adjacent jobs. - Personal alcohol limits belong to a qualified health professional and current public-health guidance. - Intoxication, overdose, and driving-fitness judgments require human or emergency review. - Local liability analysis belongs to a qualified local reviewer. - Service, denial, transport booking, guest contact, purchasing, and every physical intervention remain outside the skill. Complete this step when the request is either stopped under the emergency branch or confirmed as pre-service planning