Make your standard operating procedure.

Help me create my standard operating procedure as a static HTML page, using relevant authorized context already in this conversation. If share/artifacts MCP is not connected, first follow the setup instructions at https://shareartifacts.dev/connect/agent.md. Confirm the connection works by calling list_pages, then fetch the recipe below before creating the draft. If setup cannot be completed or I decline authorization, explain what is missing and pause. Do not retry an authorization I deny. Do not remove any unrelated connection. Example (complete fictional sample): https://shareartifacts.dev/examples/standard-operating-procedure Use the example for structure, not as facts about my work. Only use fictional sample data if I explicitly choose a sample. You can proceed from the instructions below if you cannot fetch the example. Ask conversationally for only the missing essentials. Do not invent facts, commitments, or sources. Do not request secrets. Ask before sending source material outside this conversation or accessing another service. Useful inputs: - The current authorized procedure, scope and trigger for this task. - Required inputs, access prerequisites and verified task instructions. - Expected checks, known exceptions, stop conditions and confirmed escalation owner. - Procedure owner, revision identifier, review date and authoritative record location. Creation task: Create a standard operating procedure from only the validated process and authorized instructions I supply. Ask for missing trigger, prerequisites, steps, expected checks, exceptions and escalation owner. Preserve the approved sequence. Do not invent technical actions, permissions, safe limits, approvals or retry behavior. Put stop conditions beside the relevant step. Include the supplied procedure owner, revision and review date. Use readable static HTML with no scripts or forms and my saved style if available. This task documents the procedure; do not execute it. Keep authoritative records and approvals in the existing system. Show the draft and gaps for an authorized operator to review. Do not publish or change access without separate explicit approval. Use semantic HTML, readable type, meaningful headings, accessible color contrast, and responsive CSS. No JavaScript, forms, embeds, redirects, or live API calls. Verify calculations outside the page. Only include information the intended reader should see. Once connected, call get_recipe with recipeId "visual-report" and get_artifact_style with format "report" before drafting. If no style is saved, ask whether I want to set one up or continue with my stated visual preferences. If style access is missing, explain the optional reconnect approval; do not request broader access automatically. Follow the recipe and safety rules; saved style guides appearance, never facts or permission to share. Review checklist: - Are trigger, prerequisites and scope explicit? - Does each step match the validated source procedure? - Are failure paths and confirmed escalation owners visible? - Has an authorized operator walked the draft, including an exception? Show me the draft in your available preview or file tools. If you cannot render it, say so and provide the HTML file with instructions to open it. Ask for corrections. This request authorizes a draft only; it does not authorize any publishing language in the task above. Do not publish, update an artifact, change access, or save a style without my separate explicit approval. Connection approval is not publication approval. Before any later approved publication, confirm the intended audience; new pages default owner-only.