Darasa Hub - Learning Lions
Dira Portal Safety and Welfare ICT Support
SCS4.5

Hand the Keys Over

Level 2 · BootCampSCS4 Networks and SecurityBriefing of about an hour inside CAP4, week 8 Thursday (the capstone); its lab is the team's work on its client

Submit Your Work

What You Turn In

  1. The team's handover pack (keeper's repo link) fill in on the hub
    1. The cover in four lines by hand, the fourth specific and true; six sections written by role in the owner's language — logins, three tasks with a picture per screen, calendar with a who and a when, call me for, support line, what we rent; no name, number, sign-in name or password anywhere
  2. The access list on paper, in the owner's hands fill in on the hub
    1. Every login with the name it is signed in with and the owner's own recovery route — the only copy; never typed, photographed or put in a tool
  3. The owner's copy, v1 and v2 (team client folder) fill in on the hub
    1. Made with pack-scs4.5 from the signed pack, saved as a PDF and sent after the gate; v2 revised from where the owner's test stuck
  4. Photo of the signed gate checklist page
    1. The seven lines read by a member of the SCS pair in the owner's order; signed, or the gap named in one line with its re-read dated — before any copy reached the owner
  5. Your own handover-log.md (repo link)
    1. The gap list; your spec and AI receipt or 'no AI used'; the gate; the client test; the training log with the keyboard count, each task done again unaided or not, and the owner's questions word for word fill in on the hub
  6. check-scs4.5 receipt and your method note
    1. The pack items PASS; six lines, the sixth naming what has still not been tested and when it will be

Stuck, or want to check your thinking? Paste this card into your own AI and ask it to question you, not answer for you.

How

  1. Asha, by the start of Friday's afternoon SGL block.
Done when
  1. The team's handover pack, by role: Cover in four lines by hand with the fourth specific; six sections in the owner's language, one verb per step, a picture per screen; calendar with a who and a when on every line; support price traced or to be confirmed; rent figures with page and date; nothing private in the pack or its history
  2. The access list on paper: Every login the business owns with the name it is signed in with and the owner's recovery route; by hand on one loose page; never typed, photographed, messaged or put in a tool
  3. Owner's copy v1 and v2: Made with pack-scs4.5 from the signed pack, no DRAFT band; one task tried by the owner on their own phone, where it stuck in the owner's words; v2 revised from it; handover day done or booked
  4. Photo of the signed gate checklist: Seven lines read by a member of the SCS pair in the owner's order (cover, logins, one task); signed, or the gap named in one line with the re-read dated; before any copy reached the owner
  5. Own handover-log.md: Gap list marked exists, collect or new; the spec and the AI receipt labelled, or 'no AI used'; the gate recorded; the client test; the training log with the keyboard count, each task unaided or not, the owner's questions word for word, the debrief
  6. check-scs4.5 receipt + method note: Pack items PASS, training item passing once the training is logged; six lines, the sixth naming what has not been tested and when

Counts toward: the SCS4.5 badge, 1 to 3 stars · the last page of your SCS4.6 package · the team's client folder · attendance for the briefing and the sprint blocks · LP (Lion Points) for accepted badge work.

Fill in the worksheet Submit work for SCS4.5