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. 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/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 exact choice, decision maker, requested timing and reason for it, and what approval would authorize. Mark missing authority or dates as unresolved. - Client-approved outcomes, preferences, and hard constraints. Include disputed priorities rather than letting the agent choose them silently. - Dated notes, measurements, and quotes, with source links and sharing permission. Include currency, cost period, scope, exclusions, and client effort where known. - Credible alternatives and the consequences of continuing current arrangements. Include existing recommendations, counterarguments, and unknowns that could change the choice. Creation task: Create a client decision brief for [audience] answering [specific decision], using my authorized materials. Establish who decides, what approval would authorize, and any supplied timing. Use the client's stated outcomes and hard constraints. Analyse credible alternatives, including continuing current arrangements when relevant, before writing the recommendation. Compare the same currency, time horizon, scope, and cost inclusions; show ongoing costs and client effort where known. Keep unknowns distinct from zero and preserve conflicting estimates with their sources. Recalculate material totals and check feasibility against hard constraints. Distinguish evidence, assumptions, professional judgment, and unknowns. Explain the main tradeoff, strongest counterargument, and what would change the recommendation. If evidence cannot support a choice, ask for the next evidence-gathering step. Do not invent approval, an owner, a deadline, or scoring weights. Lead with the requested decision, proposed answer, and critical caveat; follow with the comparison and dated supporting evidence. Make the next action explicit and keep approval replies in the existing email or project workflow. Build readable static HTML in my saved style if available, without scripts or forms. Check source accuracy, calculations, and whether a fresh reader can explain the choice and its limits. Show me the draft and flag confidential content for recipient-access review. Do not publish or change access without separate explicit approval. 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. Once connected, call get_recipe with recipeId "client-decision-brief" 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: - Is the requested choice within the client's authority, with selection, budget approval, and contract commitment kept distinct? - Recalculate material totals and check decisive facts against original inputs. Does the proposed option satisfy the hard constraints, and does the conclusion follow? - Are costs compared on matching terms, with exclusions, ongoing costs, conflicting estimates, and material unknowns visible? - Can a fresh reader explain the choice, tradeoff, uncertainty, change condition, and next action without agreeing with the recommendation? - Are proposed and approved work distinct, and do you have permission to share the findings, quotes, and linked evidence with 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.