Make your onboarding guide.

Help me create my onboarding guide as a static HTML page, using relevant authorized context already in this conversation. Example (illustrative structure): https://shareartifacts.dev/guides/onboarding-guide#example 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 role description and manager-approved first-week goals, with realistic expectations for what happens later. - Current access-request instructions and the approved support channel; never include credentials or recovery codes. - Authoritative team policies, process documents, and examples that the new hire is permitted to read. - Confirmed task owners, support contacts, and the date each important instruction was last checked. Creation task: Create a role-specific first-week onboarding field guide as static HTML using only the approved sources I provide. Start with the first useful outcome, then organize tasks in prerequisite order. For each task include why it matters, the relevant source link, what done looks like, and a confirmed help path. Separate essential steps from optional background. Keep policy summaries brief and link to their authoritative versions. Do not invent owners, access permissions, deadlines, or tool instructions. Exclude credentials, private employee information, and restricted material. Apply my saved artifact style if available. Use readable headings and no scripts or forms. Flag outdated or missing instructions for review. Do not publish or change access until I approve the draft. If this is a training field guide, use supplied learner objectives, a worked example, a practice task and confirmed human feedback criteria. Distinguish participation from competence; do not grade, certify or invent training requirements. Use authorized synthetic practice data where appropriate. If adapting this for volunteers, preserve organizer-approved arrival details, role boundaries, break arrangements and confirmed help contacts. Exclude personal rosters and medical information. Do not invent safeguarding, emergency or safety procedures; request the organizer's approved instructions. 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: - Can the new hire identify their first task and the prerequisites without opening every link? - Do links work for the intended recipient, not only for the author’s account? - Are help contacts confirmed and sensitive employee or access details excluded? - Does the guide name an owner and review date without claiming automatic updates? 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.