Make your static page or app decision brief.

Help me create my static page or app decision brief as a static HTML page, using relevant authorized context already in this conversation. Example (complete fictional sample): https://shareartifacts.dev/examples/static-artifact-vs-web-app 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 recipient's actual task, including every required action after reading. - Whether inputs must be submitted, stored, calculated or shared between users. - Data freshness, identity, permissions and operational requirements. - The approved snapshot and source definitions if a reading artifact fits. Creation task: Create a static HTML decision brief that qualifies whether my reader task fits a static artifact or needs a web application. Use my authorized requirements and existing context. Separate reading and explanation from submitted inputs, saved state, live queries, calculations, accounts and background work. Recommend a real application workflow when active behavior is essential; suggest a reading-plus-approved-link split only when appropriate. Ask only for missing essentials. Use my saved artifact style if available. This task creates a communication brief only, not an app or a prototype with misleading controls. No scripts, forms, fake login, save buttons or live-data claims. Show the draft for review. Do not publish, deploy an application 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: - Is every required reader action classified, not just the page's appearance? - Does the page avoid controls that imply unsupported submission or saved state? - Are snapshot freshness and external-app responsibilities explicit? - If the primary job needs an app, does the recommendation clearly say so? 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.