Make your technical concept explainer.

Help me create my technical concept explainer as a static HTML page, using relevant authorized context already in this conversation. Example (complete fictional sample): https://shareartifacts.dev/examples/technical-concept-explainer 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: - Verified concept references and the relevant product or protocol version when applicable. - The reader's background and the specific why or how question to answer. - A checked example, required definitions and known exceptions. - Permission to reuse any source material; prefer original diagrams and short attributed excerpts. Creation task: Create a technical concept explainer for [audience] answering [question] from only supplied or authorized verified references. Ask for missing audience or version context. Define essential terms, follow one checked example and include a small original static diagram only if it clarifies the relationship. Label analogies and simplified models, and explain their limits beside the relevant claims. Do not invent product behavior, citations, operational instructions or universal guarantees. Do not copy restricted source figures. Use accessible static HTML with no scripts or forms and my saved style if available; the page is not a simulation. Show the draft and claims to verify. 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. If share/artifacts is connected, call get_recipe with recipeId "infographic-explainer" and get_artifact_style with format "explainer". 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: - Does the explanation answer one bounded question? - Are claims verified for the relevant context or version? - Are model assumptions and exceptions visible? - Does the original static diagram remain understandable without color or interactivity? 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.