Make your meeting decision record.

Help me create my meeting decision record 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/meeting-decision-record 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: - Meeting notes or a transcript you are permitted to use, plus the date and purpose of the discussion. - The proposal, brief, or options considered, so the record can preserve relevant tradeoffs rather than invent rationale. - Explicitly agreed actions, owners, and dates; missing commitments should remain marked as unconfirmed. - Any authoritative decision or task system the team already uses, to avoid creating contradictory records. Creation task: Turn the supplied meeting notes into a concise decision record as static HTML. Lead with confirmed decisions and what changed. For each decision include its scope, recorded rationale, and important tradeoffs. Then list agreed actions with the exact owner and due date when supplied, followed by unresolved questions. Keep proposals separate from decisions. Do not infer agreement from silence, invent commitments, assign missing owners, or create deadlines. Mark ambiguous items for participant confirmation. Link to supplied authoritative task or decision records where appropriate. Remove confidential discussion and unnecessary personal details. Apply my saved artifact style if available, with readable headings and restrained emphasis. No scripts or forms. Return a review draft; wait for approval before publishing or changing access. 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: - Does each decision have clear evidence of agreement in the notes or participant confirmation? - Are proposals and unresolved questions visibly separate from confirmed decisions? - Have owners and dates been verified instead of inferred by the agent? - Does the record respect confidential discussion and point to the team’s authoritative records? 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.