Make your architecture decision record.

Help me create my architecture decision record 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/architecture-decision-record 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 specific architectural question, affected scope, and verified functional or operational constraints. - Alternatives actually considered, supporting evidence, and uncertainties—not invented benchmark results. - The exact proposed, accepted, rejected, or superseded state with its owner, date, and source record when supplied. - Positive and negative consequences, implementation status, and the established review or supersession process. Creation task: Create an architecture decision record companion from only the authorized requirements, alternatives, evidence, and decision records I provide. Ask for missing essentials: scope, constraints, actual alternatives, decision state, owner, source date, and consequences. Separate requirements from assumptions, proposed from accepted decisions, and acceptance from implementation. Preserve negative consequences and unresolved evidence. Do not invent benchmarks, security guarantees, consensus, requirements, or approval. Explain why the chosen tradeoff fits this scope, not why a technology is universally best. Keep sensitive infrastructure and credentials out of the shared version. State the authoritative record and supersession process without silently rewriting history. Create static HTML with no scripts, forms, or live system claims. Apply my saved artifact style if available. Show the draft and unresolved questions. Do not publish or change access without separate explicit approval. Do not edit the architecture, deploy changes, or mark a record accepted as part of drafting. 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 specific scope and governing constraint understandable before the solution? - Are alternatives and consequences grounded in the actual evidence? - Are proposed, accepted, superseded, and implemented states distinguished? - Does the record retain negative tradeoffs and unmeasured claims honestly? - Is the authoritative history preserved, with sensitive engineering details appropriately limited? 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.