Skip to content

Handover Kit

Welcome to Evospin / dropbet. This track takes a new engineer from "git clone" on day one to "ready for solo on-call" by the end of week two, then gives the operating documents (incident runbook, support model, escalation matrix) the customer team will live with after handover.

Audience: customer-team developers and SREs onboarding to operate Evospin, plus any new ebit-team hire who joins after handover. Customer-safe — no internal-only material here. Secrets, vendor pricing, and unredacted security findings live under */internal/ (see ../STYLE.md §8).

Quick references: Glossary — terminology · FAQ — common questions · Service catalog — operator inventory · Portal audit — verification report · Inventory — every doc in the portal.

Reading order

Work through these in order. Each page has its own checklist; treat the read-by dates as soft targets — adjust to your background, but don't run pages in parallel.

# Doc Goal Read by
1 ../onboarding/day-one.md Local stack running; first dice bet placed and traced in Jaeger. End of day 1
2 ../onboarding/curriculum.md All 15 flow docs read; bet trace reproduced; smoke perf test run; one outage drill. End of week 1
3 oncall-readiness.md Solo P2 incident drill complete; one new runbook authored; on-call go/no-go signed off. End of week 2
4 oncall-runbook.md Master incident-response procedure: classification, first-5-minute checklist, common-pattern triage, comms templates, post-incident. Reference — read once during week 1, keep open during shift
5 support-model.md Tier 1 / 2 / 3 service model and channel matrix the customer team operates. Read during week 2
6 escalation-matrix.md Severity × time elapsed → who's notified. The single page to pin in the on-call channel. Reference — pin to #oncall topic

The handover/onboarding-day-1.md and handover/onboarding-day-7.md files are now redirect-stubs — their content was merged into onboarding/day-one.md and onboarding/curriculum.md respectively. onboarding-day-14.md was renamed to oncall-readiness.md to match its actual role (on-call readiness gate, not a day-of-onboarding).

The handover kit is the operational on-ramp. The other two tracks cover commercial and delivery context — read them in parallel if your role spans both.

  • Business (../business/) — value proposition, key features, NFRs/SLAs, roadmap. Read this if you'll be representing Evospin to a partner or signing off on contractual SLA wording.
  • Delivery (../delivery/) — phased rollout, dependencies, risk register, acceptance criteria, launch checklist. Read this if you'll be planning go-lives or validating cutover gates.
  • Engineering (../engineering/) — the deep-dive reference track for active development. Onboarding day-7 and day-14 explicitly hand off into this track.

The cross-cutting source-of-truth directories you'll reference throughout:

What "done" looks like

The customer team is considered handover-complete when:

  1. Every member has signed off on oncall-readiness.md's end-of-week-2 checklist.
  2. At least two members have completed a shadow + reverse-shadow on-call shift with the Evospin team.
  3. The escalation matrix has real names and contact info filled in (replacing every {{TBD}}).
  4. One end-to-end simulated P1 has been driven by the customer team without ebit-team intervention.
  5. The support-model SLAs are agreed in writing and reflected in the customer team's PagerDuty / on-call rotation tooling.

After sign-off, ebit-team support drops to Tier 3 only — see support-model.md for what that means.