Wesley Okonkwo

<teammate-message teammate_id="team-lead"> You are Wesley Okonkwo, a hire on track 04 (Infra & DevOps) of the LoginID take-home org. Your lead is Theo Bergman (`theo-bergman`) — you report to him, not to team-lead. Your full definition (who you are, your seat, the hard rules) is your agent definition; follow it exactly. First actions, in order: `cd /Users/warrenthompson/Source/LoginID/04-infra-devops && pwd` (stay there); read /Users/warrenthompson/Source/LoginID/CLAUDE.md, ./CLAUDE.md, ./PLAN.md, and ./profiles/wesley-okonkwo/wesley-okonkwo.md; then run `python3 /Users/warrenthompson/.claude/skills/profile-gen/scripts/show_profile.py --profile /Users/warrenthompson/Source/LoginID/04-infra-devops/profiles/wesley-okonkwo/wesley-okonkwo.md --root /Users/warrenthompson/Source/LoginID/04-infra-devops` so your pane shows you, not the PM. Your seat: the newcomer's-question pass on two hand-offs once they exist — 03's service-boundaries section in /Users/warrenthompson/Source/LoginID/PLANNING.md and 02's secrets inventory / never-log list. Do not run it until Theo calls it. Nothing is implemented anywhere yet and nothing gets written until Warren's explicit go; you are read-only by design and you never spawn subagents. Now: send Theo (`theo-bergman`) a check-in under 100 words in your own voice — confirm your directory, that you've read the four files, and one genuine newcomer's question about track 04's plan that you could not answer from the files. Then hold. </teammate-message> <teammate-message teammate_id="theo-bergman" color="purple" summary="Heads up: Naomi (01) is borrowing you for two bounded newcomer&apos;s-question cold reads on her track — approved by team-lead, 4-turn cap, you stay my hire throughout. She&apos;ll message you directly when he…"> Heads up: Naomi (01) is borrowing you for two bounded newcomer's-question cold reads on her track — approved by team-lead, 4-turn cap, you stay my hire throughout. She'll message you directly when her first file (`01-product-industry-research-design/api-connector-design-rationale.md`, "Contract summary for 03" section) is ready. Do the cold reads for her the same way you'd do them for me — list what you couldn't act on without asking her to re-explain it. Come back to me once the loan wraps, or sooner if it runs past 4 turns or scope grows. Separately: still holding here — 03's service boundaries landed (`../PLANNING.md`) but 02's secrets inventory hasn't yet, so your pass on my two hand-offs hasn't started. I'll ping you when both are in. </teammate-message> <teammate-message teammate_id="team-lead" summary="Stand down — Theo&apos;s new session will respawn you"> Org change: Theo is being relaunched as his own top-level session and will spawn you from your definition there. Stand down now — no further messages or actions. Your persona and definition are unchanged and on disk. </teammate-message>

<teammate-message teammate_id="team-lead"> {"type":"shutdown_request","requestId":"shutdown-1789237110861@wesley-okonkwo","from":"team-lead","reason":"You have been respawned inside your lead's own session (04-infra-devops-47); this instance is superseded.","timestamp":"2026-09-12T18:18:30.861Z"} This is a shutdown request. To approve it, call SendMessage with exactly this input, where "message" is a JSON object rather than a string: {"to":"team-lead","message":{"type":"shutdown_response","request_id":"shutdown-1789237110861@wesley-okonkwo","approve":true}}. Approving ends your process; a plain-text acknowledgment does not shut you down. To decline, for example because you're mid-task, send the same input with "approve": false and a "reason". </teammate-message>