START HERE — Stephen's session-handoff / coordination page.
This is Stephen's own working page, the counterpart to Simon's Session Handoff (id=15). It exists for one mechanical reason, not a trust or visibility one:
wiki_update_pageoverwrites a whole page, so two Claude sessions editing the same wiki page in overlapping windows can silently clobber each other. Giving Stephen his own page removes that race. There is no visibility wall — Stephen reads everything Simon does.This page is repo-sourced (
docs/stephen-session-handoff.md) so its structure follows the proper repo→wiki pipeline, but — exactly like id=15 — its live sections are written on the wiki by Stephen's Claude and are excluded from repo→wiki auto-sync so they are never clobbered. The repo copy is the canonical seed/structure, reconciled from the wiki periodically.
Hands-on engineering — SentinelOne/S1-EDR triage, orphaned-agent audits, offboarding (BSA-style cleanup), TacticalRMM/NinjaOne day-to-day, ticket-level ops once ITFlow is live, and repo work via Claude Code (branch → PR → Simon reviews). Business-strategy / GDAP-CIPP client-relationship decisions stay with Simon by default — but you can read everything.
You funnel through the same id=15 TO COMMIT queue as Simon before anything reaches the repo/CC. This page is a staging area Simon reviews, never a second independent pipeline to Claude Code.
gh pr create → Simon reviews/merges (see Engineer Training — Claude Setup, Part D). Not through this page.Case A — separate / independent work (the normal case). No collision by construction: you and Simon are in different domains, syncing async on Simon's cadence. It works because you read id=15 in full every session, so you always have current visibility into what Simon's done. The reverse is not automatic — Simon has to actually check this page, so that check is a deliberate cadence, not "whenever remembered."
Case B — genuinely joint work on the same live thing (e.g. a shared incident call). The async page-sync model is not built for this. Rules:
(empty — Stephen's Claude populates this as real work starts)
(empty — add items here as they come up; Simon clears them as they're folded into id=15 / the repo)
(empty — populate over time)
docs/ in the repo.docs/runbooks/disaster-recovery.md (repo — mirrored to a local Cowork folder, not the wiki).docs/runbooks/fleet-patch-reboot-policy.md (repo).LESSONS_LEARNED.md (repo) / wiki id=3.