share-sansa-engine
Technical Handoff

Introduce yourself, fill in your name and today's date on slide 1 before the session. On slide 2, establish the snapshot rule clearly and firmly: "Everything we discuss today refers to commit 0ff1c8dbc00bb14b2… — if changes have been made since then, we are not talking about those today." This prevents the session derailing into half-finished work no one has context for.

Slide 3 is your commitment to the room — these exact deliverables will exist when you leave. Slide 4 is the adapted schedule (one hour, no working groups — just the walkthrough and handover). Slide 5 shows the commit SHA. Ask someone to screenshot it. Every document produced should contain that SHA.

This is the educational core. You're not expecting people to memorise it — you're giving them just enough to know where to look when they're working alone later. The single most important thing to land: UI change → /src. Logic change → /server. New endpoint → controller + service + route registration, then write the test. Trace a user action through the architecture diagram on slide 10 out loud — from browser click all the way to database and back.

Codebase tour (11–12): ask if anyone has the repo cloned and can read out their actual top-level directories. Correct the slide against what they see — that correction is itself useful documentation. Component skeleton (13–14): point out props at the top, render in the middle, widget registration at the bottom, and that tests mock the fetch call. Backend pseudocode (15): the most important line in the whole codebase is "no data access in controllers" — say that explicitly.

You're not doing working groups today, so skip the group task slides and jump to the deliverables. Show slide 21 (the full list) and confirm the room knows what's in the ZIP. Open slide 27 (quickstart template) and walk through it — point at every {{placeholder}} and explain exactly where to find the value. The most important substitution: {{node_version}} from package.json → engines. If someone in the room can do that live and verify the app starts, do it now.

This is the most important slide of the session. Go through each deliverable out loud and get a name against it before anyone stands up. "Who owns quickstart.md? …Great. Who opens the 8 GitHub issues? …Excellent." If you skip this, the ZIP ends up in someone's downloads folder and nothing ever gets committed. Write names on the slide live if you can.

Read the wrap-up checklist on slide 25 like a flight checklist — confirm each item is green before closing. Then: agree on a follow-up review date before people leave the room. Two weeks from today is the target — owners review the ZIP, commit what's approved, open the 8 starter issues. Slide 30 is the close — confirm the ZIP is being delivered to the SANSA contact today or within 24 hours.