Handover & life events — FAQ
Death, will, McDonald's Sunbury, utilities, who gets what. Start First 24 hours.
LIF-001 — Saxon died — first thing to do?
Stack context: Will · Ryan · McDonald's · utilities Integrated runbooks: Symptom finder — life · will
Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
- Safety, support, call 000 if emergency — First 24 hours. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: First 24 hours
LIF-002 — Read the will where?
Stack context: Will · Ryan · McDonald's · utilities Integrated runbooks: Symptom finder — life · will
Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
- will.md + paper copy at home — Read the will. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: First 24 hours
LIF-003 — Who gets the PC and server?
Stack context: Will · Ryan · McDonald's · utilities Integrated runbooks: Symptom finder — life · will
Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
- Ryan — all technology — Who gets what. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: First 24 hours
LIF-004 — Can Ryan sell the PC?
Stack context: Will · Ryan · McDonald's · utilities Integrated runbooks: Symptom finder — life · will
Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
- No — will forbids selling inherited tech. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: First 24 hours
LIF-005 — Who gets the money?
Stack context: Will · Ryan · McDonald's · utilities Integrated runbooks: Symptom finder — life · will
Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
- Children at 20 or charity — not other family members per will. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: First 24 hours
LIF-006 — No children — money goes where?
Stack context: Will · Ryan · McDonald's · utilities Integrated runbooks: Symptom finder — life · will
Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
- Charity chosen by spouse, or if none, immediate family chooses. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: First 24 hours
LIF-007 — Belongings after tech and money?
Stack context: Will · Ryan · McDonald's · utilities Integrated runbooks: Symptom finder — life · will
Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
- Relatives with ancestor Glenda or Lynette may claim — rest donated/recycled. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: First 24 hours
LIF-008 — Photos warning?
Stack context: Will · Ryan · McDonald's · utilities Integrated runbooks: Symptom finder — life · will
Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
- Whoever sorts photos may see upsetting content — go slowly. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: First 24 hours
LIF-009 — Contact McDonald's?
Stack context: Will · Ryan · McDonald's · utilities Integrated runbooks: Symptom finder — life · will
Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
- Sunbury store — Product Quality Manager — Contact McDonald's. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: First 24 hours
LIF-010 — McDonald's role title?
Stack context: Will · Ryan · McDonald's · utilities Integrated runbooks: Symptom finder — life · will
Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
- Product Quality Manager since Nov 2024 — Career. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: First 24 hours
LIF-011 — Notify banks?
Stack context: Will · Ryan · McDonald's · utilities Integrated runbooks: Symptom finder — life · will
Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
- Contact banks with death certificate when ready. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: First 24 hours
LIF-012 — Notify insurance?
Stack context: Will · Ryan · McDonald's · utilities Integrated runbooks: Symptom finder — life · will
Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
- Notify insurance and utilities. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: First 24 hours
LIF-013 — Cancel subscriptions when?
Stack context: Will · Ryan · McDonald's · utilities Integrated runbooks: Symptom finder — life · will
Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
- Not day one — Cancel overview. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: First 24 hours
LIF-014 — Wipe phone or PC day one?
Stack context: Will · Ryan · McDonald's · utilities Integrated runbooks: Symptom finder — life · will
Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
- No — evidence and passwords may be needed. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: First 24 hours
LIF-015 — Factory reset NAS?
Stack context: Will · Ryan · McDonald's · utilities Integrated runbooks: Symptom finder — life · will
Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
- Never without Ryan — destroys photos, vault, media. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: First 24 hours
LIF-016 — Delete Cloudflare/GitHub?
Stack context: Will · Ryan · McDonald's · utilities Integrated runbooks: Symptom finder — life · will
Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
- No — keeps docs and domains alive. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: First 24 hours
LIF-017 — Find YubiKeys?
Stack context: Will · Ryan · McDonald's · utilities Integrated runbooks: Symptom finder — life · will
Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
- Desk PC + keychain — Yubikey doc. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: First 24 hours
LIF-018 — Find vault master password?
Stack context: Will · Ryan · McDonald's · utilities Integrated runbooks: Symptom finder — life · will
Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
- Physical handover, safe — not SaxDocs. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: First 24 hours
LIF-019 — Ryan doesn't want tech?
Stack context: Will · Ryan · McDonald's · utilities Integrated runbooks: Symptom finder — life · will
Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
- Will still assigns — must hold unused until he learns or accepts per will wording. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: First 24 hours
LIF-020 — Solicitor needed?
Stack context: Will · Ryan · McDonald's · utilities Integrated runbooks: Symptom finder — life · will
Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
- Recommended for probate/estate — will is Saxon's intent not legal advice. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: First 24 hours
LIF-021 — Death certificate?
Stack context: Will · Ryan · McDonald's · utilities Integrated runbooks: Symptom finder — life · will
Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
- Funeral director helps obtain — needed for banks and McDonald's HR. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: First 24 hours
LIF-022 — Leave server powered on?
Stack context: Will · Ryan · McDonald's · utilities Integrated runbooks: Symptom finder — life · will
Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
- Yes if safe — helps tunnel services; see turn everything on. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: First 24 hours
LIF-023 — Power outage at home?
Stack context: Will · Ryan · McDonald's · utilities Integrated runbooks: Symptom finder — life · will
Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
- Power outage recovery. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: First 24 hours
LIF-024 — UniFi router location?
Stack context: Will · Ryan · McDonald's · utilities Integrated runbooks: Symptom finder — life · will
Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
- Near internet entry — equipment map. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: First 24 hours
LIF-025 — TrueNAS location?
Stack context: Will · Ryan · McDonald's · utilities Integrated runbooks: Symptom finder — life · will
Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
- Ugreen DXP 8800 where Saxon kept server. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: First 24 hours
LIF-026 — GitHub if Saxon dies?
Stack context: Will · Ryan · McDonald's · utilities Integrated runbooks: Symptom finder — life · will
Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
- GitHub if Saxon dies — Ryan access. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: First 24 hours
LIF-027 — Docs site stay online?
Stack context: Will · Ryan · McDonald's · utilities Integrated runbooks: Symptom finder — life · will
Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
- Yes on Cloudflare Pages — even if home offline temporarily. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: First 24 hours
LIF-028 — Emergency contacts list?
Stack context: Will · Ryan · McDonald's · utilities Integrated runbooks: Symptom finder — life · will
Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
- Family + McDonald's manager + solicitor — build from phone contacts with Ryan. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: First 24 hours
LIF-029 — Children and money at 20?
Stack context: Will · Ryan · McDonald's · utilities Integrated runbooks: Symptom finder — life · will
Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
- Must be familiar with finance docs or equivalent per will. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: First 24 hours
LIF-030 — Charity choice?
Stack context: Will · Ryan · McDonald's · utilities Integrated runbooks: Symptom finder — life · will
Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
- Spouse chooses; document choice for executor. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: First 24 hours
LIF-031 — Car ownership?
Stack context: Will · Ryan · McDonald's · utilities Integrated runbooks: Symptom finder — life · will
Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
- Check rego and will — not separately listed in will excerpt. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: First 24 hours
LIF-032 — House title?
Stack context: Will · Ryan · McDonald's · utilities Integrated runbooks: Symptom finder — life · will
Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
- MyState mortgage — legal title with settlement docs in vault. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: First 24 hours
LIF-033 — Spouse living in house?
Stack context: Will · Ryan · McDonald's · utilities Integrated runbooks: Symptom finder — life · will
Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
- Separate legal/housing question — banks and solicitor. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: First 24 hours
LIF-034 — Social media accounts?
Stack context: Will · Ryan · McDonald's · utilities Integrated runbooks: Symptom finder — life · will
Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
- Online presence — memorial or close with care. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: First 24 hours
LIF-035 — Work keys or uniform?
Stack context: Will · Ryan · McDonald's · utilities Integrated runbooks: Symptom finder — life · will
Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
- Return to McDonald's Sunbury with HR. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: First 24 hours
LIF-036 — Superannuation?
Stack context: Will · Ryan · McDonald's · utilities Integrated runbooks: Symptom finder — life · will
Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
- Contact fund with death cert — not detailed in SaxDocs. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: First 24 hours
LIF-037 — Life insurance?
Stack context: Will · Ryan · McDonald's · utilities Integrated runbooks: Symptom finder — life · will
Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
- Check vault and mail for policy — notify insurer. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: First 24 hours
LIF-038 — Pet care?
Stack context: Will · Ryan · McDonald's · utilities Integrated runbooks: Symptom finder — life · will
Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
- Not in will excerpt — family decision. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: First 24 hours
LIF-039 — Fire for unclaimed items?
Stack context: Will · Ryan · McDonald's · utilities Integrated runbooks: Symptom finder — life · will
Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
- Will allows burn at family gathering for unrecyclable items. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: First 24 hours
LIF-040 — Will updates after 2024 commit?
Stack context: Will · Ryan · McDonald's · utilities Integrated runbooks: Symptom finder — life · will
Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
- Valid unless contradict core bec5c06 rules — see will page. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: First 24 hours
LIF-041 — Overwhelmed — skip tech?
Stack context: Will · Ryan · McDonald's · utilities Integrated runbooks: Symptom finder — life · will
Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
- OK — First 24 hours says go slowly. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: First 24 hours
LIF-042 — Handover guide index?
Stack context: Will · Ryan · McDonald's · utilities Integrated runbooks: Symptom finder — life · will
Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
- Handover guides. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: First 24 hours