← Qiki · all runs · 📊 leaderboard

r-1787906335387-xe3oe
Write the SOP for onboarding a new engineer in week one — accounts and access, first commit, buddy assignment, and a day-5 checkpoint
model /nix/store/w8fajwih8isx2rl94rb8ggc1knmnf8x9-Qwen3.6-35B-A3B-MTP-GGUF upstream http://127.0.0.1:8080 harness 127.0.0.1 score 0 / 10
2026-08-28 08:38:55 UTC · total 41s · 1 step
ops-doc · done · 41s
Engineer Onboarding SOP
0 / 10
model /nix/store/w8fajwih8isx2rl94rb8ggc1knmnf8x9-Qwen3.6-35B-A3B-MTP-GGUF harness 127.0.0.1:8080
validity 0/2 fidelity 0/2 structure 0/2 depth 0/2 cleanliness 0/2
why (1 notes)
  • unknown kind
1 LLM call on this step
ok · 41296 ms · prompt 2188c → resp 3268c · t=0.35 max=2800 ·
→ /nix/store/w8fajwih8isx2rl94rb8ggc1knmnf8x9-Qwen3.6-35B-A3B-MTP-GGUF @ http://127.0.0.1:8080
raw JSON
{
  "id": "r-1787906335387-xe3oe",
  "prompt": "Write the SOP for onboarding a new engineer in week one — accounts and access, first commit, buddy assignment, and a day-5 checkpoint",
  "project": {
    "name": "EngineerOnboard",
    "tagline": "Streamlined week-one SOP for new engineer integration, access, and first commit.",
    "theme": "clean, structured, and supportive onboarding workflow with clear milestones and accountability checkpoints",
    "brandColors": [
      "#2563EB",
      "#10B981",
      "#F3F4F6"
    ],
    "audience": "engineering managers, team leads, and HR onboarding specialists",
    "vibe": "organized, efficient, welcoming, professional"
  },
  "steps": [
    {
      "id": "s1-jr8uz",
      "kind": "ops-doc",
      "params": {
        "brief": "Write a comprehensive Standard Operating Procedure (SOP) for onboarding a new software engineer during their first week. The document must cover: 1) Accounts and Access (provisioning GitHub, Slack, Jira, cloud consoles, hardware setup), 2) First Commit (guidance on finding a good first issue, code review etiquette, and deployment pipeline basics), 3) Buddy Assignment (criteria for selecting a buddy, initial introduction meeting agenda, and ongoing support expectations), and 4) Day-5 Checkpoint (structured feedback session, goal setting for week two, and addressing blockers). Use a clear, professional, and supportive tone suitable for engineering managers and team leads.",
        "variant": "sop",
        "project": {
          "name": "EngineerOnboard",
          "tagline": "Streamlined week-one SOP for new engineer integration, access, and first commit.",
          "theme": "clean, structured, and supportive onboarding workflow with clear milestones and accountability checkpoints",
          "brandColors": [
            "#2563EB",
            "#10B981",
            "#F3F4F6"
          ],
          "audience": "engineering managers, team leads, and HR onboarding specialists",
          "vibe": "organized, efficient, welcoming, professional"
        },
        "heroPlanned": false
      },
      "label": "Engineer Onboarding SOP"
    }
  ],
  "results": {
    "s1-jr8uz": {
      "status": "done",
      "startedAt": 1787906335388,
      "attempt": 1,
      "output": {
        "html": "<!doctype html><html lang=\"en\"><head><meta charset=\"utf-8\">\n<meta name=\"viewport\" content=\"width=device-width,initial-scale=1\">\n<title>New Software Engineer First-Week Onboarding</title>\n<style>\n:root{\n  --bg:#faf7f2;--surface:#ffffff;--elevated:#f2ede4;\n  --text:#171410;--muted:#5d574e;--border:rgba(23,20,16,.14);\n  --accent:#10B981;--accent-btn:#10B981;--accent-text:#0b7955;--ink:#0a0a0a;--glow:rgba(16,185,129,0.20);--soft:rgba(16,185,129,0.13);\n  /* Foreground for anything painted on --soft. See the derivation above: a token\n     computed against --bg is not valid on a tinted surface. */\n  --soft-ink:#0b7955;\n  /* Minimum comfortable hit area. Referenced by every interactive rule so a\n     tap target can never regress below the 44px WCAG/iOS floor. */\n  --tap:44px;\n  /* Translucent chrome derived from the direction's own background. Hardcoding\n     rgba(10,10,11,.62) here put dark text on a dark nav (1.08:1) the moment a\n     light direction shipped. */\n  --nav-bg:rgba(250,247,242,0.72);--hairline:rgba(0,0,0,.14);\n  --font:ui-sans-serif,system-ui,-apple-system,'Segoe UI',Roboto,Helvetica,Arial,sans-serif;\n  --font-display:'Iowan Old Style','Palatino Linotype',Palatino,'Book Antiqua',Georgia,serif;\n  --w-display:400;--w-body:400;\n  --track-display:-.01em;\n  --texture:radial-gradient(1200px 500px at 80% -10%, rgba(138,51,36,.06), transparent 60%);\n  --maxw:1200px;--r:3px;--r-lg:5px;--ease:cubic-bezier(.4,0,.2,1);\n  color-scheme:light;\n}\n\n*{box-sizing:border-box}\nbody{background:var(--bg);background-image:var(--texture);color:var(--text);font-family:var(--font);\nfont-weight:var(--w-body);font-size:16px;line-height:1.6;margin:0;padding:clamp(24px,4vw,64px);-webkit-font-smoothing:antialiased}\n.doc{max-width:50rem;margin:0 auto}\nh1{font-family:var(--font-display);font-weight:var(--w-display);letter-spacing:var(--track-display);\nfont-size:clamp(1.8rem,4vw,2.7rem);line-height:1.15;margin:0}\n.doctype{font-size:.8rem;text-transform:uppercase;letter-spacing:.1em;color:var(--accent-text);font-weight:700;margin:0 0 10px}\n.sub{color:var(--muted);font-size:1.02rem;margin:8px 0 0;max-width:62ch}\nh2{font-family:var(--font-display);font-weight:var(--w-display);font-size:1.18rem;letter-spacing:-.01em;\nmargin:34px 0 12px;display:flex;align-items:center;gap:10px}\n.count{font-size:.8rem;font-weight:600;color:var(--soft-ink);background:var(--soft);border-radius:99px;padding:2px 10px}\np{margin:0 0 14px;max-width:68ch}\n.lede{color:var(--muted);font-size:1.02rem;margin:22px 0 0;max-width:66ch}\n.eyebrow{display:block;font-size:.8rem;text-transform:uppercase;letter-spacing:.09em;color:var(--muted);font-weight:700;margin-bottom:6px}\n.meta{display:flex;flex-wrap:wrap;gap:8px 24px;margin:26px 0 0;font-size:.9rem;color:var(--muted);\npadding-bottom:20px;border-bottom:1px solid var(--border)}\n.meta b{color:var(--text);font-weight:700;margin-right:6px}\n.sub-line{color:var(--muted);font-size:.9rem;margin-top:4px}\n.act{font-weight:700;font-size:1rem;line-height:1.4}\n.chip{display:inline-flex;align-items:center;background:var(--soft);color:var(--soft-ink);\npadding:4px 12px;border-radius:99px;font-size:.82rem;font-weight:700}\n.chip.alt{background:transparent;border:1px solid var(--border);color:var(--muted)}\n.tags{display:flex;flex-wrap:wrap;gap:8px;margin-top:10px}\nol.steps{list-style:none;margin:0;padding:0;counter-reset:none}\n.step{display:grid;grid-template-columns:2.6rem 1fr;gap:14px;background:var(--surface);border:1px solid var(--border);\nborder-radius:var(--r);padding:16px 18px;margin-bottom:10px}\n.num{font-family:var(--font-display);font-weight:var(--w-display);font-size:1.25rem;color:var(--accent-text);line-height:1.25}\n.done{margin-top:12px;font-size:.92rem;color:var(--muted);border-left:2px solid var(--accent-text);padding-left:12px}\n.done b{color:var(--text)}\nul.plain{margin:0;padding-left:20px}ul.plain li{margin-bottom:8px}\nol.plain{margin:0;padding-left:22px}ol.plain li{margin-bottom:8px}\n/* Printable checklist: a drawn box, not an <input>. A real checkbox is a ~20px\n   hit target inside a document nobody submits, and it would trip the 44px\n   interactive floor. The ROW carries --tap so it stays comfortable either way. */\nul.check{list-style:none;margin:0;padding:0}\nul.check li{display:flex;align-items:flex-start;gap:14px;min-height:var(--tap);padding:11px 0;border-bottom:1px solid var(--border)}\n.box{flex:none;width:20px;height:20px;margin-top:3px;border:2px solid var(--accent-text);border-radius:5px}\nul.cards{list-style:none;margin:0;padding:0}\nul.cards li{background:var(--surface);border:1px solid var(--border);border-left:3px solid var(--accent-text);\nborder-radius:var(--r);padding:14px 16px;margin-bottom:10px}\n.kv{display:grid;grid-template-columns:repeat(auto-fit,minmax(200px,1fr));gap:22px;margin:26px 0 8px}\n.salary{margin:26px 0 0}\ntable{width:100%;border-collapse:collapse;font-size:.95rem;margin-top:8px}\nth{text-align:left;font-size:.8rem;text-transform:uppercase;letter-spacing:.08em;color:var(--muted);\nfont-weight:700;padding:0 10px 10px 0;border-bottom:1px solid var(--border)}\ntd{padding:12px 10px 12px 0;border-bottom:1px solid var(--border);vertical-align:top}\nth.n,td.n{text-align:right;padding-right:0;font-variant-numeric:tabular-nums;white-space:nowrap}\ntfoot td{border-bottom:0;padding:6px 10px 6px 0;color:var(--muted)}\ntfoot tr.total td{color:var(--text);font-weight:700;font-size:1.12rem;border-top:2px solid var(--accent-text);padding-top:14px}\n.org ul{list-style:none;margin:0;padding-left:28px;border-left:1px solid var(--border)}\n.org>ul{padding-left:0;border-left:0}\n.node{display:inline-flex;flex-direction:column;justify-content:center;min-height:var(--tap);\nbackground:var(--surface);border:1px solid var(--border);border-left:3px solid var(--accent-text);\nborder-radius:var(--r);padding:10px 16px;margin:7px 0}\n.node b{font-size:1rem;line-height:1.35}\n.node span{color:var(--muted);font-size:.88rem}\n.obj{display:grid;grid-template-columns:3rem 1fr;gap:14px;margin-bottom:26px}\n.obj h2{margin:0}\nul.krs{list-style:none;margin:14px 0 0;padding:0}\nul.krs li{border-left:2px solid var(--border);padding:0 0 0 14px;margin-bottom:14px}\n.notice{border:1px solid var(--accent-text);background:var(--soft);border-radius:var(--r);\npadding:14px 18px;margin:28px 0 0;font-size:.92rem;color:var(--text);max-width:none}\n.notice b{display:block;color:var(--accent-text);margin-bottom:4px;font-size:.82rem;\ntext-transform:uppercase;letter-spacing:.08em}\n.todo{display:inline-block;background:var(--soft);color:var(--soft-ink);border:1px dashed var(--accent-text);\nborder-radius:6px;padding:2px 9px;font-size:.88rem;font-weight:700}\n.signoff{margin-top:38px;color:var(--muted);font-size:.92rem}\n.rule{display:inline-block;width:220px;border-bottom:1px solid var(--border);margin-top:26px}\n@media print{body{padding:0}.doc{max-width:none}}\n</style></head><body><main class=\"doc\">\n<p class=\"doctype\">Standard operating procedure</p><h1>New Software Engineer First-Week Onboarding</h1><p class=\"sub\">Following this procedure guarantees that a new engineer has secure access, contributes their first code, receives mentorship, and has aligned expectations by the end of week one.</p><div class=\"meta\"><span><b>Owner</b> Engineering Manager</span><span><b>Trigger</b> Offer acceptance and confirmed start date</span><span><b>Review</b> Reviewed quarterly by the Engineering Leadership Team</span></div>\n<p class=\"lede\">Applies to all new full-time software engineers from Day 1 to Day 5. Does not apply to contractors, interns, or non-engineering roles.</p>\n<h2>Procedure</h2>\n<ol class=\"steps\"><li class=\"step\">\n  <div class=\"num\">1</div>\n  <div>\n    <div class=\"act\">Provision GitHub, Slack, Jira, and cloud console access</div>\n    <div class=\"tags\"><span class=\"chip\">IT Ops Lead</span><span class=\"chip alt\">IT Service Desk Portal</span></div>\n    <div class=\"done\"><b>Done when</b> The new engineer receives login credentials and can successfully log into all four systems</div>\n  </div>\n</li><li class=\"step\">\n  <div class=\"num\">2</div>\n  <div>\n    <div class=\"act\">Configure and ship hardware (laptop, monitor, peripherals)</div>\n    <div class=\"tags\"><span class=\"chip\">IT Ops Lead</span><span class=\"chip alt\">Shipping Carrier</span></div>\n    <div class=\"done\"><b>Done when</b> The engineer confirms receipt of the package and the device boots to the desktop</div>\n  </div>\n</li><li class=\"step\">\n  <div class=\"num\">3</div>\n  <div>\n    <div class=\"act\">Assign a buddy based on team rotation and expertise</div>\n    <div class=\"tags\"><span class=\"chip\">Engineering Manager</span><span class=\"chip alt\">HRIS System</span></div>\n    <div class=\"done\"><b>Done when</b> The buddy is notified via Slack and the assignment is recorded in the onboarding tracker</div>\n  </div>\n</li><li class=\"step\">\n  <div class=\"num\">4</div>\n  <div>\n    <div class=\"act\">Conduct the initial buddy introduction meeting</div>\n    <div class=\"tags\"><span class=\"chip\">Buddy</span><span class=\"chip alt\">Video Conferencing Tool</span></div>\n    <div class=\"done\"><b>Done when</b> The agenda (tools, team intro, first week goals) is reviewed and the new engineer has the buddy's contact info</div>\n  </div>\n</li><li class=\"step\">\n  <div class=\"num\">5</div>\n  <div>\n    <div class=\"act\">Guide the engineer to a 'good first issue' in Jira</div>\n    <div class=\"tags\"><span class=\"chip\">Buddy</span><span class=\"chip alt\">Jira</span></div>\n    <div class=\"done\"><b>Done when</b> The engineer has claimed a ticket labeled 'good-first-issue' and added it to their local board</div>\n  </div>\n</li><li class=\"step\">\n  <div class=\"num\">6</div>\n  <div>\n    <div class=\"act\">Walk through the local development environment setup</div>\n    <div class=\"tags\"><span class=\"chip\">Buddy</span><span class=\"chip alt\">Local Development Environment</span></div>\n    <div class=\"done\"><b>Done when</b> The engineer runs the application locally without errors</div>\n  </div>\n</li><li class=\"step\">\n  <div class=\"num\">7</div>\n  <div>\n    <div class=\"act\">Submit the first pull request</div>\n    <div class=\"tags\"><span class=\"chip\">New Engineer</span><span class=\"chip alt\">GitHub</span></div>\n    <div class=\"done\"><b>Done when</b> The pull request is created and linked to the Jira ticket</div>\n  </div>\n</li><li class=\"step\">\n  <div class=\"num\">8</div>\n  <div>\n    <div class=\"act\">Perform the first code review</div>\n    <div class=\"tags\"><span class=\"chip\">Buddy</span><span class=\"chip alt\">GitHub</span></div>\n    <div class=\"done\"><b>Done when</b> The pull request has at least one approving comment or requested changes</div>\n  </div>\n</li><li class=\"step\">\n  <div class=\"num\">9</div>\n  <div>\n    <div class=\"act\">Merge the first pull request to the main branch</div>\n    <div class=\"tags\"><span class=\"chip\">Buddy</span><span class=\"chip alt\">GitHub</span></div>\n    <div class=\"done\"><b>Done when</b> The PR is merged and the CI pipeline passes</div>\n  </div>\n</li><li class=\"step\">\n  <div class=\"num\">10</div>\n  <div>\n    <div class=\"act\">Conduct the Day-5 checkpoint meeting</div>\n    <div class=\"tags\"><span class=\"chip\">Engineering Manager</span><span class=\"chip alt\">Video Conferencing Tool</span></div>\n    <div class=\"done\"><b>Done when</b> The meeting notes are saved and the new engineer confirms their goals for week two</div>\n  </div>\n</li></ol>\n<h2>If something goes wrong</h2><ul class=\"plain\"><li>I</li><li>If</li></ul>\n\n</main></body></html>",
        "variant": "sop",
        "label": "Standard operating procedure",
        "title": "New Software Engineer First-Week Onboarding",
        "doc": {
          "title": "New Software Engineer First-Week Onboarding",
          "purpose": "Following this procedure guarantees that a new engineer has secure access, contributes their first code, receives mentorship, and has aligned expectations by the end of week one.",
          "scope": "Applies to all new full-time software engineers from Day 1 to Day 5. Does not apply to contractors, interns, or non-engineering roles.",
          "owner": "Engineering Manager",
          "trigger": "Offer acceptance and confirmed start date",
          "steps": [
            {
              "action": "Provision GitHub, Slack, Jira, and cloud console access",
              "owner": "IT Ops Lead",
              "doneWhen": "The new engineer receives login credentials and can successfully log into all four systems",
              "tool": "IT Service Desk Portal"
            },
            {
              "action": "Configure and ship hardware (laptop, monitor, peripherals)",
              "owner": "IT Ops Lead",
              "doneWhen": "The engineer confirms receipt of the package and the device boots to the desktop",
              "tool": "Shipping Carrier"
            },
            {
              "action": "Assign a buddy based on team rotation and expertise",
              "owner": "Engineering Manager",
              "doneWhen": "The buddy is notified via Slack and the assignment is recorded in the onboarding tracker",
              "tool": "HRIS System"
            },
            {
              "action": "Conduct the initial buddy introduction meeting",
              "owner": "Buddy",
              "doneWhen": "The agenda (tools, team intro, first week goals) is reviewed and the new engineer has the buddy's contact info",
              "tool": "Video Conferencing Tool"
            },
            {
              "action": "Guide the engineer to a 'good first issue' in Jira",
              "owner": "Buddy",
              "doneWhen": "The engineer has claimed a ticket labeled 'good-first-issue' and added it to their local board",
              "tool": "Jira"
            },
            {
              "action": "Walk through the local development environment setup",
              "owner": "Buddy",
              "doneWhen": "The engineer runs the application locally without errors",
              "tool": "Local Development Environment"
            },
            {
              "action": "Submit the first pull request",
              "owner": "New Engineer",
              "doneWhen": "The pull request is created and linked to the Jira ticket",
              "tool": "GitHub"
            },
            {
              "action": "Perform the first code review",
              "owner": "Buddy",
              "doneWhen": "The pull request has at least one approving comment or requested changes",
              "tool": "GitHub"
            },
            {
              "action": "Merge the first pull request to the main branch",
              "owner": "Buddy",
              "doneWhen": "The PR is merged and the CI pipeline passes",
              "tool": "GitHub"
            },
            {
              "action": "Conduct the Day-5 checkpoint meeting",
              "owner": "Engineering Manager",
              "doneWhen": "The meeting notes are saved and the new engineer confirms their goals for week two",
              "tool": "Video Conferencing Tool"
            }
          ],
          "exceptions": [
            "If access is not granted by Day 1 morning, escalate to IT Ops Lead immediately",
            "If no 'good first issue' is available, the Engineering Manager must create or assign a small task manually",
            "If the buddy is unavailable, the Engineering Manager acts as the interim buddy"
          ],
          "review": "Reviewed quarterly by the Engineering Leadership Team"
        },
        "accent": "#10B981",
        "direction": "editorial",
        "needsLegalReview": false,
        "warnings": []
      },
      "produces": {
        "siteHtml": "<!doctype html><html lang=\"en\"><head><meta charset=\"utf-8\">\n<meta name=\"viewport\" content=\"width=device-width,initial-scale=1\">\n<title>New Software Engineer First-Week Onboarding</title>\n<style>\n:root{\n  --bg:#faf7f2;--surface:#ffffff;--elevated:#f2ede4;\n  --text:#171410;--muted:#5d574e;--border:rgba(23,20,16,.14);\n  --accent:#10B981;--accent-btn:#10B981;--accent-text:#0b7955;--ink:#0a0a0a;--glow:rgba(16,185,129,0.20);--soft:rgba(16,185,129,0.13);\n  /* Foreground for anything painted on --soft. See the derivation above: a token\n     computed against --bg is not valid on a tinted surface. */\n  --soft-ink:#0b7955;\n  /* Minimum comfortable hit area. Referenced by every interactive rule so a\n     tap target can never regress below the 44px WCAG/iOS floor. */\n  --tap:44px;\n  /* Translucent chrome derived from the direction's own background. Hardcoding\n     rgba(10,10,11,.62) here put dark text on a dark nav (1.08:1) the moment a\n     light direction shipped. */\n  --nav-bg:rgba(250,247,242,0.72);--hairline:rgba(0,0,0,.14);\n  --font:ui-sans-serif,system-ui,-apple-system,'Segoe UI',Roboto,Helvetica,Arial,sans-serif;\n  --font-display:'Iowan Old Style','Palatino Linotype',Palatino,'Book Antiqua',Georgia,serif;\n  --w-display:400;--w-body:400;\n  --track-display:-.01em;\n  --texture:radial-gradient(1200px 500px at 80% -10%, rgba(138,51,36,.06), transparent 60%);\n  --maxw:1200px;--r:3px;--r-lg:5px;--ease:cubic-bezier(.4,0,.2,1);\n  color-scheme:light;\n}\n\n*{box-sizing:border-box}\nbody{background:var(--bg);background-image:var(--texture);color:var(--text);font-family:var(--font);\nfont-weight:var(--w-body);font-size:16px;line-height:1.6;margin:0;padding:clamp(24px,4vw,64px);-webkit-font-smoothing:antialiased}\n.doc{max-width:50rem;margin:0 auto}\nh1{font-family:var(--font-display);font-weight:var(--w-display);letter-spacing:var(--track-display);\nfont-size:clamp(1.8rem,4vw,2.7rem);line-height:1.15;margin:0}\n.doctype{font-size:.8rem;text-transform:uppercase;letter-spacing:.1em;color:var(--accent-text);font-weight:700;margin:0 0 10px}\n.sub{color:var(--muted);font-size:1.02rem;margin:8px 0 0;max-width:62ch}\nh2{font-family:var(--font-display);font-weight:var(--w-display);font-size:1.18rem;letter-spacing:-.01em;\nmargin:34px 0 12px;display:flex;align-items:center;gap:10px}\n.count{font-size:.8rem;font-weight:600;color:var(--soft-ink);background:var(--soft);border-radius:99px;padding:2px 10px}\np{margin:0 0 14px;max-width:68ch}\n.lede{color:var(--muted);font-size:1.02rem;margin:22px 0 0;max-width:66ch}\n.eyebrow{display:block;font-size:.8rem;text-transform:uppercase;letter-spacing:.09em;color:var(--muted);font-weight:700;margin-bottom:6px}\n.meta{display:flex;flex-wrap:wrap;gap:8px 24px;margin:26px 0 0;font-size:.9rem;color:var(--muted);\npadding-bottom:20px;border-bottom:1px solid var(--border)}\n.meta b{color:var(--text);font-weight:700;margin-right:6px}\n.sub-line{color:var(--muted);font-size:.9rem;margin-top:4px}\n.act{font-weight:700;font-size:1rem;line-height:1.4}\n.chip{display:inline-flex;align-items:center;background:var(--soft);color:var(--soft-ink);\npadding:4px 12px;border-radius:99px;font-size:.82rem;font-weight:700}\n.chip.alt{background:transparent;border:1px solid var(--border);color:var(--muted)}\n.tags{display:flex;flex-wrap:wrap;gap:8px;margin-top:10px}\nol.steps{list-style:none;margin:0;padding:0;counter-reset:none}\n.step{display:grid;grid-template-columns:2.6rem 1fr;gap:14px;background:var(--surface);border:1px solid var(--border);\nborder-radius:var(--r);padding:16px 18px;margin-bottom:10px}\n.num{font-family:var(--font-display);font-weight:var(--w-display);font-size:1.25rem;color:var(--accent-text);line-height:1.25}\n.done{margin-top:12px;font-size:.92rem;color:var(--muted);border-left:2px solid var(--accent-text);padding-left:12px}\n.done b{color:var(--text)}\nul.plain{margin:0;padding-left:20px}ul.plain li{margin-bottom:8px}\nol.plain{margin:0;padding-left:22px}ol.plain li{margin-bottom:8px}\n/* Printable checklist: a drawn box, not an <input>. A real checkbox is a ~20px\n   hit target inside a document nobody submits, and it would trip the 44px\n   interactive floor. The ROW carries --tap so it stays comfortable either way. */\nul.check{list-style:none;margin:0;padding:0}\nul.check li{display:flex;align-items:flex-start;gap:14px;min-height:var(--tap);padding:11px 0;border-bottom:1px solid var(--border)}\n.box{flex:none;width:20px;height:20px;margin-top:3px;border:2px solid var(--accent-text);border-radius:5px}\nul.cards{list-style:none;margin:0;padding:0}\nul.cards li{background:var(--surface);border:1px solid var(--border);border-left:3px solid var(--accent-text);\nborder-radius:var(--r);padding:14px 16px;margin-bottom:10px}\n.kv{display:grid;grid-template-columns:repeat(auto-fit,minmax(200px,1fr));gap:22px;margin:26px 0 8px}\n.salary{margin:26px 0 0}\ntable{width:100%;border-collapse:collapse;font-size:.95rem;margin-top:8px}\nth{text-align:left;font-size:.8rem;text-transform:uppercase;letter-spacing:.08em;color:var(--muted);\nfont-weight:700;padding:0 10px 10px 0;border-bottom:1px solid var(--border)}\ntd{padding:12px 10px 12px 0;border-bottom:1px solid var(--border);vertical-align:top}\nth.n,td.n{text-align:right;padding-right:0;font-variant-numeric:tabular-nums;white-space:nowrap}\ntfoot td{border-bottom:0;padding:6px 10px 6px 0;color:var(--muted)}\ntfoot tr.total td{color:var(--text);font-weight:700;font-size:1.12rem;border-top:2px solid var(--accent-text);padding-top:14px}\n.org ul{list-style:none;margin:0;padding-left:28px;border-left:1px solid var(--border)}\n.org>ul{padding-left:0;border-left:0}\n.node{display:inline-flex;flex-direction:column;justify-content:center;min-height:var(--tap);\nbackground:var(--surface);border:1px solid var(--border);border-left:3px solid var(--accent-text);\nborder-radius:var(--r);padding:10px 16px;margin:7px 0}\n.node b{font-size:1rem;line-height:1.35}\n.node span{color:var(--muted);font-size:.88rem}\n.obj{display:grid;grid-template-columns:3rem 1fr;gap:14px;margin-bottom:26px}\n.obj h2{margin:0}\nul.krs{list-style:none;margin:14px 0 0;padding:0}\nul.krs li{border-left:2px solid var(--border);padding:0 0 0 14px;margin-bottom:14px}\n.notice{border:1px solid var(--accent-text);background:var(--soft);border-radius:var(--r);\npadding:14px 18px;margin:28px 0 0;font-size:.92rem;color:var(--text);max-width:none}\n.notice b{display:block;color:var(--accent-text);margin-bottom:4px;font-size:.82rem;\ntext-transform:uppercase;letter-spacing:.08em}\n.todo{display:inline-block;background:var(--soft);color:var(--soft-ink);border:1px dashed var(--accent-text);\nborder-radius:6px;padding:2px 9px;font-size:.88rem;font-weight:700}\n.signoff{margin-top:38px;color:var(--muted);font-size:.92rem}\n.rule{display:inline-block;width:220px;border-bottom:1px solid var(--border);margin-top:26px}\n@media print{body{padding:0}.doc{max-width:none}}\n</style></head><body><main class=\"doc\">\n<p class=\"doctype\">Standard operating procedure</p><h1>New Software Engineer First-Week Onboarding</h1><p class=\"sub\">Following this procedure guarantees that a new engineer has secure access, contributes their first code, receives mentorship, and has aligned expectations by the end of week one.</p><div class=\"meta\"><span><b>Owner</b> Engineering Manager</span><span><b>Trigger</b> Offer acceptance and confirmed start date</span><span><b>Review</b> Reviewed quarterly by the Engineering Leadership Team</span></div>\n<p class=\"lede\">Applies to all new full-time software engineers from Day 1 to Day 5. Does not apply to contractors, interns, or non-engineering roles.</p>\n<h2>Procedure</h2>\n<ol class=\"steps\"><li class=\"step\">\n  <div class=\"num\">1</div>\n  <div>\n    <div class=\"act\">Provision GitHub, Slack, Jira, and cloud console access</div>\n    <div class=\"tags\"><span class=\"chip\">IT Ops Lead</span><span class=\"chip alt\">IT Service Desk Portal</span></div>\n    <div class=\"done\"><b>Done when</b> The new engineer receives login credentials and can successfully log into all four systems</div>\n  </div>\n</li><li class=\"step\">\n  <div class=\"num\">2</div>\n  <div>\n    <div class=\"act\">Configure and ship hardware (laptop, monitor, peripherals)</div>\n    <div class=\"tags\"><span class=\"chip\">IT Ops Lead</span><span class=\"chip alt\">Shipping Carrier</span></div>\n    <div class=\"done\"><b>Done when</b> The engineer confirms receipt of the package and the device boots to the desktop</div>\n  </div>\n</li><li class=\"step\">\n  <div class=\"num\">3</div>\n  <div>\n    <div class=\"act\">Assign a buddy based on team rotation and expertise</div>\n    <div class=\"tags\"><span class=\"chip\">Engineering Manager</span><span class=\"chip alt\">HRIS System</span></div>\n    <div class=\"done\"><b>Done when</b> The buddy is notified via Slack and the assignment is recorded in the onboarding tracker</div>\n  </div>\n</li><li class=\"step\">\n  <div class=\"num\">4</div>\n  <div>\n    <div class=\"act\">Conduct the initial buddy introduction meeting</div>\n    <div class=\"tags\"><span class=\"chip\">Buddy</span><span class=\"chip alt\">Video Conferencing Tool</span></div>\n    <div class=\"done\"><b>Done when</b> The agenda (tools, team intro, first week goals) is reviewed and the new engineer has the buddy's contact info</div>\n  </div>\n</li><li class=\"step\">\n  <div class=\"num\">5</div>\n  <div>\n    <div class=\"act\">Guide the engineer to a 'good first issue' in Jira</div>\n    <div class=\"tags\"><span class=\"chip\">Buddy</span><span class=\"chip alt\">Jira</span></div>\n    <div class=\"done\"><b>Done when</b> The engineer has claimed a ticket labeled 'good-first-issue' and added it to their local board</div>\n  </div>\n</li><li class=\"step\">\n  <div class=\"num\">6</div>\n  <div>\n    <div class=\"act\">Walk through the local development environment setup</div>\n    <div class=\"tags\"><span class=\"chip\">Buddy</span><span class=\"chip alt\">Local Development Environment</span></div>\n    <div class=\"done\"><b>Done when</b> The engineer runs the application locally without errors</div>\n  </div>\n</li><li class=\"step\">\n  <div class=\"num\">7</div>\n  <div>\n    <div class=\"act\">Submit the first pull request</div>\n    <div class=\"tags\"><span class=\"chip\">New Engineer</span><span class=\"chip alt\">GitHub</span></div>\n    <div class=\"done\"><b>Done when</b> The pull request is created and linked to the Jira ticket</div>\n  </div>\n</li><li class=\"step\">\n  <div class=\"num\">8</div>\n  <div>\n    <div class=\"act\">Perform the first code review</div>\n    <div class=\"tags\"><span class=\"chip\">Buddy</span><span class=\"chip alt\">GitHub</span></div>\n    <div class=\"done\"><b>Done when</b> The pull request has at least one approving comment or requested changes</div>\n  </div>\n</li><li class=\"step\">\n  <div class=\"num\">9</div>\n  <div>\n    <div class=\"act\">Merge the first pull request to the main branch</div>\n    <div class=\"tags\"><span class=\"chip\">Buddy</span><span class=\"chip alt\">GitHub</span></div>\n    <div class=\"done\"><b>Done when</b> The PR is merged and the CI pipeline passes</div>\n  </div>\n</li><li class=\"step\">\n  <div class=\"num\">10</div>\n  <div>\n    <div class=\"act\">Conduct the Day-5 checkpoint meeting</div>\n    <div class=\"tags\"><span class=\"chip\">Engineering Manager</span><span class=\"chip alt\">Video Conferencing Tool</span></div>\n    <div class=\"done\"><b>Done when</b> The meeting notes are saved and the new engineer confirms their goals for week two</div>\n  </div>\n</li></ol>\n<h2>If something goes wrong</h2><ul class=\"plain\"><li>I</li><li>If</li></ul>\n\n</main></body></html>",
        "opsDoc": {
          "title": "New Software Engineer First-Week Onboarding",
          "purpose": "Following this procedure guarantees that a new engineer has secure access, contributes their first code, receives mentorship, and has aligned expectations by the end of week one.",
          "scope": "Applies to all new full-time software engineers from Day 1 to Day 5. Does not apply to contractors, interns, or non-engineering roles.",
          "owner": "Engineering Manager",
          "trigger": "Offer acceptance and confirmed start date",
          "steps": [
            {
              "action": "Provision GitHub, Slack, Jira, and cloud console access",
              "owner": "IT Ops Lead",
              "doneWhen": "The new engineer receives login credentials and can successfully log into all four systems",
              "tool": "IT Service Desk Portal"
            },
            {
              "action": "Configure and ship hardware (laptop, monitor, peripherals)",
              "owner": "IT Ops Lead",
              "doneWhen": "The engineer confirms receipt of the package and the device boots to the desktop",
              "tool": "Shipping Carrier"
            },
            {
              "action": "Assign a buddy based on team rotation and expertise",
              "owner": "Engineering Manager",
              "doneWhen": "The buddy is notified via Slack and the assignment is recorded in the onboarding tracker",
              "tool": "HRIS System"
            },
            {
              "action": "Conduct the initial buddy introduction meeting",
              "owner": "Buddy",
              "doneWhen": "The agenda (tools, team intro, first week goals) is reviewed and the new engineer has the buddy's contact info",
              "tool": "Video Conferencing Tool"
            },
            {
              "action": "Guide the engineer to a 'good first issue' in Jira",
              "owner": "Buddy",
              "doneWhen": "The engineer has claimed a ticket labeled 'good-first-issue' and added it to their local board",
              "tool": "Jira"
            },
            {
              "action": "Walk through the local development environment setup",
              "owner": "Buddy",
              "doneWhen": "The engineer runs the application locally without errors",
              "tool": "Local Development Environment"
            },
            {
              "action": "Submit the first pull request",
              "owner": "New Engineer",
              "doneWhen": "The pull request is created and linked to the Jira ticket",
              "tool": "GitHub"
            },
            {
              "action": "Perform the first code review",
              "owner": "Buddy",
              "doneWhen": "The pull request has at least one approving comment or requested changes",
              "tool": "GitHub"
            },
            {
              "action": "Merge the first pull request to the main branch",
              "owner": "Buddy",
              "doneWhen": "The PR is merged and the CI pipeline passes",
              "tool": "GitHub"
            },
            {
              "action": "Conduct the Day-5 checkpoint meeting",
              "owner": "Engineering Manager",
              "doneWhen": "The meeting notes are saved and the new engineer confirms their goals for week two",
              "tool": "Video Conferencing Tool"
            }
          ],
          "exceptions": [
            "If access is not granted by Day 1 morning, escalate to IT Ops Lead immediately",
            "If no 'good first issue' is available, the Engineering Manager must create or assign a small task manually",
            "If the buddy is unavailable, the Engineering Manager acts as the interim buddy"
          ],
          "review": "Reviewed quarterly by the Engineering Leadership Team"
        },
        "opsDocVariant": "sop",
        "opsDocTitle": "New Software Engineer First-Week Onboarding"
      },
      "finishedAt": 1787906376685,
      "llmCalls": [
        {
          "upstream": "http://127.0.0.1:8080",
          "modelRequested": "txt2txt",
          "temperature": 0.35,
          "maxTokens": 2800,
          "timeoutMs": 240000,
          "startedAt": 1787906335388,
          "finishedAt": 1787906376684,
          "ok": true,
          "promptChars": 2188,
          "responseChars": 3268,
          "modelServed": "/nix/store/w8fajwih8isx2rl94rb8ggc1knmnf8x9-Qwen3.6-35B-A3B-MTP-GGUF"
        }
      ]
    }
  },
  "startedAt": 1787906335387,
  "fingerprint": {
    "ownAiUrl": "http://127.0.0.1:8080",
    "harnessHost": "127.0.0.1",
    "modelServed": "qwen-image",
    "nodeVersion": "v24.18.1",
    "capturedAt": 1787906335387
  },
  "finishedAt": 1787906376687,
  "scores": {
    "perStep": {
      "s1-jr8uz": {
        "validity": 0,
        "fidelity": 0,
        "structure": 0,
        "depth": 0,
        "cleanliness": 0,
        "total": 0,
        "notes": [
          "unknown kind"
        ]
      }
    },
    "total": 0,
    "perKind": {
      "ops-doc": 0
    },
    "axes": [
      "validity",
      "fidelity",
      "structure",
      "depth",
      "cleanliness"
    ]
  }
}