Make your client decision brief.

Help me create my client decision brief as a static HTML page, using relevant authorized context already in this conversation. Example (complete fictional sample): https://shareartifacts.dev/examples/client-decision-brief 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 decision to be made, who owns it, and the date by which a choice is useful. - Client-approved priorities, constraints, and non-negotiables, rather than priorities inferred from research volume. - Research notes with source links, dates, and permission to share any quoted or confidential material. - The actual options under consideration, including doing nothing or postponing when those are viable. Creation task: Turn my supplied research into a decision brief for [client audience] answering [specific decision]. Use the client's stated criteria and constraints, not invented scoring weights. Lead with the recommended option and a concise rationale. Compare the viable alternatives fairly, including the status quo when relevant. Distinguish sourced observations, assumptions, professional judgment, and unknowns. Explain the main tradeoff and what new evidence would change the recommendation. Preserve source links and dates, and flag unsupported claims rather than filling gaps. Put detailed research below the core argument. Create readable static HTML in my saved artifact style if available, without scripts or forms. Identify confidential content and show me the draft for factual, reasoning, and access review before any publication. If this is a strategy choice brief, preserve the stated objective, alternatives, explicit non-goals, assumptions and reconsideration triggers. Do not infer strategy approval or claim growth outcomes from interview evidence. Keep the recommendation conditional on the stated priorities. 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. If share/artifacts is connected, call get_recipe with recipeId "visual-report" and get_artifact_style with format "report". Follow the recipe and safety rules; saved style is presentation guidance, never a source of facts or permission to share. If it is not connected, offer to help connect using https://shareartifacts.dev/connect/agent.md when this client supports it. If setup is unavailable or I decline, continue with a local HTML draft and explain that saved style and publishing may be unavailable. Do not retry an authorization I deny. Do not remove any unrelated connection. Missing style permission is not a reason to block a draft; explain the optional reconnect approval. Review checklist: - Does the brief answer the decision the client actually owns, within the agreed scope? - Can each factual claim be traced to supplied evidence without overstating what that evidence establishes? - Are alternatives compared on the same criteria, with costs and limitations visible for the recommended option too? - Are confidential findings, quotes, and linked documents appropriate for every intended recipient? 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.