Make your product launch brief.

Help me create my product launch brief as a static HTML page, using relevant authorized context already in this conversation. Example (complete fictional sample): https://shareartifacts.dev/examples/product-launch-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: - Approved release scope, exclusions, audience and launch objective. - Readiness evidence from product, support and communications, with dates. - Required launch conditions, decision owner and recorded approval status. - Dependencies, remaining tasks and dates marked as targets or commitments. Creation task: Using my authorized launch materials, create a static HTML launch brief for the stated audience and release scope. Lead with the exact decision and current approval state. Distinguish required conditions, evidence, remaining actions, confirmed owners and dates. Keep pilot scope, exclusions and dependencies visible. Separate proposed dates from commitments and completed work from launch approval. Do not invent readiness percentages, customer outcomes, owners or approvals. Ask only for missing essentials using existing authorized context. Apply my saved artifact style if available. No scripts, forms, live tracking or automatic announcements. Show the draft and contradictions for review. Do not publish, send announcements 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. 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: - Are the release audience and exclusions accurate? - Does each required condition have source-backed evidence and an honest status? - Are targets clearly different from approved dates throughout the page? - Are approval and announcement decisions still controlled by their established owners? 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.