Make your project proposal.

Help me create my project proposal 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/project-proposal 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 problem and supporting evidence, with dates and permission to share. - The work being proposed, explicit exclusions, and deliverables with acceptance criteria. - Estimated effort or cost, units and exclusions, who supplied each estimate, and unresolved resource availability. - Dependencies, proposed timing, risks, and the person authorized to decide. - The existing approval process and any mandatory submission format. Creation task: Using only materials I provide or have authorized you to access, create a project proposal for [decision owner] about [proposed work]. Ask only for missing essentials: the decision requested, scope and exclusions, deliverables and review criteria, resource estimates, dependencies, and approval process. Lead with exactly what I am asking them to authorize. Distinguish proposed work from approved work, estimates from commitments, and deliverables from expected outcomes. Preserve estimate units, sources, exclusions, and uncertainty. Do not invent available staff, savings, return on investment, approvals, dates, or acceptance criteria. If criteria are missing, list them as unresolved rather than making them binding. Explain what must happen before work starts and what would require a separate decision. Create readable static HTML with no scripts, forms, signature fields, or live-data claims. Use my saved artifact style if available. Keep sensitive evidence in my existing authorized tools; include only audience-safe details and links. Show me the draft and unresolved questions for review. Do not publish or change access without separate explicit approval. Keep the approval record in our existing email or project workflow. For a business-case version, state the supplied benefit hypothesis, baseline, evidence gaps and proposed checkpoint before a larger commitment. Keep benefits hypothetical until measured. Do not invent ROI, monetize staff hours without approved assumptions or convert a proposed checkpoint into an agreed approval condition. 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: - Is the exact phase and resource commitment being requested visible near the top? - Are exclusions as clear as included deliverables? - Are estimated cost, effort, and timing labeled accurately with their dependencies? - Are acceptance criteria supplied facts or clearly unresolved—not invented commitments? - Are expected benefits separate from measured outcomes? - Does the page explain how to respond without pretending to collect approval? 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.