Make your report format decision brief.

Help me create my report format 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/html-report-vs-pdf 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 reader's device, connectivity, accessibility and delivery requirements. - Whether content must stay fixed or can change after sharing. - Print, file submission, archive or record-retention requirements confirmed by the owner. - The approved report source, intended audience and required editing or calculation tasks. Creation task: Create a static HTML format-decision brief from my recipient requirements and approved report context. Compare an HTML reading page with a PDF for browser reading, fixed layout, offline delivery, corrections, printing, accessibility and any stated archive requirements. Recommend by the actual job and state unknown requirements. Do not claim one format is universally better. Preserve source facts in any illustrative comparison. Ask only for missing essentials using existing authorized context. Use my saved artifact style if available. This task creates a reading decision brief only: do not generate or promise PDF export, archive certification, signatures, editable calculations or an application. No scripts or forms. Show the draft for 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 recipient format and offline requirements confirmed rather than assumed? - Does the choice distinguish a current editable edition from a preserved historical copy? - Have accessibility and layout been checked in the actual chosen output? - Are PDF production, archive standards, signatures and calculations assigned to appropriate separate workflows? 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.