Make your reader-first briefing.

Help me create my reader-first briefing 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/information-design-with-agent 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 approved source material, its date, and definitions for any figures. Keep private material in your own agent conversation. - The intended reader and the decision or action they need to take. If you have two audiences, describe both jobs. - Risks, uncertainties, deadlines, and approval boundaries that must stay visible—not disappear into an appendix. - Which details are safe for the audience, plus optional saved style preferences. A style is not permission to share source material. Creation task: Use only the source material I provide to create a clear static HTML briefing for [audience]. Their main task is [decision or action]. First propose the reading order in plain language. Put the most important supported answer first, keep evidence and material caveats beside the claims they qualify, and group background detail lower down without concealing it. Preserve names, dates, quantities, definitions, uncertainty, and approval status. Do not turn completion counts into readiness scores or invent a recommendation that the sources cannot support. Use restrained color with text labels, readable type and spacing, and a sensible mobile reading order. Use my saved artifact style if available without letting it override clarity. Ask for missing essentials and flag contradictions. Produce static HTML without scripts, forms, or live-data claims. Show me the draft and explain what you emphasized and why. Do not publish or change access without separate explicit approval. For a document-to-reading-page adaptation, first inspect the supplied text and tables, identify the reader's question and map each retained claim to its source. Preserve table definitions, caveats and approved links. Flag unreadable or missing content rather than guessing. Do not promise file-format fidelity or alter a required formal original. 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 "infographic-explainer" and get_artifact_style with format "explainer" 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: - Can the intended reader find the answer and next step without reading everything? - Are every number, date, owner, and approval status still supported by the source? - Are material caveats visible near their claims, rather than buried as background? - Do text labels preserve meaning without color, and do all text/background combinations have sufficient contrast? - Are supporting details still readable on a phone, with a logical heading order and keyboard-accessible links? - Have you approved the facts, wording, intended audience, and sharing settings separately from the design? 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.