Make your sponsor prospectus.

Help me create my sponsor prospectus 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/sponsor-prospectus 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: - Confirmed event details and the scope of any tentative arrangements. - Verified historical audience figures, definitions and dates; forecasts separately labeled. - Approved package prices, units, inclusions, exclusions and inventory as of a supplied date. - The confirmed enquiry, application and agreement process; no attendee contact data. Creation task: Create a sponsor prospectus using only my authorized event facts, audience evidence, package benefits, prices and dated inventory. Ask for missing essentials and pricing conditions. Separate historical attendance, registrations and forecasts. Compare exact inclusions and exclusions; retain dates and units. Do not invent audience demographics, available slots, scarcity, tax treatment, leads or return guarantees. Do not expose attendee contact data. State that availability and agreement require confirmation through the supplied process. Create static HTML with no scripts or forms and my saved style if available. Show me the draft for evidence and commercial 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 attendance figures dated and correctly defined? - Can sponsors compare exact package inclusions? - Are inventory, prices and unresolved conditions explicit? - Does the page avoid reservation, lead or return guarantees? 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.