Track 10 · Discovery & handoverLesson 10 of 12
Handover, run state and the next use case
A handover good enough that you're invited back.
- The FDE path · Stage 6 of 6
- 30 min read
- 60 min hands-on
- Pro
What you'll be able to do
01- You can define run-state for a specific system and test it with three questions: can the customer operate it, change it and improve it without you?
- You can assemble a handover package where every artefact has a customer owner and evidence, with no vendor-owned credentials left.
- You can plan knowledge transfer (pairing, shadow then reverse shadow, drills) and a hypercare period that ends on exit criteria.
- You can write an SLA that references its SLOs, stays inside what the dependencies can deliver, and has severity terms, credits and exclusions the run team can honour.
- You can compute an independence score from change and incident records and use it as a gate.
- You can build an expansion case from measured value and the parked register, and close the engagement without overselling.
Before you start
- Incidents, on-call and runbooks: the runbooks, severity matrix and L1/L2/L3 model this concept hands over.
- SLOs and latency budgets: SLIs, error budgets and composing dependency availability.
- Agent credentials, from issue to revoke: the NHI inventory you transfer.
- Registries for models, prompts and agents and Golden datasets and the metrics that matter.
- Baselines and ROI you can defend and Picking the wedge use case: the baseline and parked register the expansion case uses.
The short version
Handover is complete when the customer can operate, change and improve the system without you, and you can prove it with records. You build that state during delivery: named owners from day one, artefacts each with an owner and evidence, credentials re-issued under customer ownership, and knowledge transferred by doing. Hypercare ends on exit criteria, not a date. The SLA is the contract: on the same indicators as the SLOs, looser than them, and no stronger than the dependencies allow. Expansion is earned in a value review against the baseline, proposing the next use case from the parked register.
- Run-state is a capability the customer has, not a document you write.
- Every credential is re-issued in the customer's tenant with a customer owner, never handed over.
- Measure independence: changes shipped and incidents resolved without you.
- The second use case comes from evidence about the first, not from a pitch.
Pro lesson
The rest of this lesson is in Pro.
The mental model, worked example, field note, failure table, exercise and self-check, with the voice tutor.
Pro opens this stage
Stage 6 · Ship, run and hand over- 8 lessons, with the voice tutor
- Lab · Check a trace export before you trust the dashboard, graded here
- Halden week 7 · The champion moves
- Halden week 8 · The portal goes down before cut-off
- Halden week 9 · Prices up, and a new rule
- Halden week 10 · A second site, and handover
- The lab kit, to run Halden weeks on your machine
Also in Pro
- Every stage and specialisation, in full
- Every lab and every role project
- Halden weeks 2–10, on your record
- Every drill, live in the playground
- All solutions, plus the server judge
- Lab Assistant and every Teach with AI