Prep deck for the 1:30 sitting at Pedro's office · minted by Cartographer 5, 2026-09-19, minutes before · glance-register: read card 0–2 before you arrive, run 3–4 during, card 6 is the goodbye · notes save-as-you-type · this shelf is temporary, never archival.
0 · WHO Pedro, inventoried (from your chat, distilled — his words stay local, not in this repo)
Uses VS Code. Compose with what exists — nothing needs replacing.
CS teacher at the edge: "I'm sort of done with teaching… I don't think my job will exist in a year" — but still teaching because he cares about his students. The onboarding is partly an answer to that sentence.
Philosophically pre-onboarded: the universities/epistemic-control thread — he's already inside the worldview ("you can't fight reality"; "credentials, not education"). You don't need to sell the WHY. Skip the manifesto pitch; he lived it.
He's bringing ideas: "I have a few ideas of different kinds" (today, 11:56 AM) — you asked for a small project as case study. The ideas are the onboarding.
Your own frame, from the chat: "There are Pedros and Jérémies out there… the failure is that we are not finding each other." Today is the counterexample. Let the session feel like that.
1 · DECIDE Session shape — tour or build?
A — Build-first: start from ONE of his ideas; the methodology arrives as the way you build it. Components appear only when the work summons them.
B — Tour-first: walk the estate (site, extension, crews) then pick a project.
A — build-first, strongly.Rationale: he told you his blocker himself — "too much material, doesn't know how to get started"; a tour ADDS material, a build gives one thread to pull. And your own doctrine says it: the epistemic use begins in aporia — a question that is genuinely his. His idea = his aporia. The estate is more impressive glimpsed from inside a working session than presented as an exhibit. Confidence: 0.9. If wrong: he arrives wanting the show — then give the 10-minute tour and land back on his idea; card 4 works in either order.
2 · MAP The components — one honest line each (say these, don't install these)
The template — "Use this template" on GitHub → a repo that already knows how to hold thinking (ADRs, seeds, questions). The only must-install today.
The VS Code extension — "ADRs for AI" on the Marketplace: tree of open questions, catches malformed questions as you type. Second must-install; 60 seconds.
Claude Code — the AI seat that reads/writes the record with you. Install if he has access; otherwise YOUR laptop is the demo of it.
ORRCF — every question ships Options, Recommendation, Rationale, Confidence, Falsifier → answering degrades to accept-or-override. Teach by encounter, not lecture: he'll meet it in his first QST.
The iOS client — the record in his pocket; Accept/Override from anywhere. Show on YOUR phone.
pneumatic / kintsugi / docket / crews / peacock+terminals — the estate's deeper machinery (wake infra, template-repair, the CLI porcelain, multi-seat culture, per-seat colors). NAME them so curiosity has addresses; defer them — card 5.
adrs.systems — the front door, for afterwards.
3 · PRE-FLIGHT On Pedro's machine (compose with what he has; ~10 min, you drive the weird parts)
VS Code present ✓ (he has it) — just confirm it opens.
git present? (git --version — macOS prompts Xcode CLT if missing; that download is the one possible wait, start it FIRST if needed.)
GitHub account signed in in the browser; gh CLI optional — skip unless smooth.
Extension: Marketplace → search "ADRs for AI" → Install. (Let HIM do this one — first-run trust dialog included; it's real first-use experience.)
Template: github.com/ADRs4AI/human-ai-collaboration-template-A → Use this template → his repo, named after HIS idea → clone → open in VS Code.
Claude access: if he has Claude Code/Pro, install+login (npm i -g @anthropic-ai/claude-code or the installer); if not, don't stall — pair on your machine, his repo.
Rule for the hour: you type nothing on his machine that he could type — the failure modes he hits ARE the lesson (and your teaching data: same thing you loved watching across your students' laptops).
4 · THE SITTING First real session (60–90 min, from his idea)
1. Seed — he dictates/types his idea messily into docs/adr/seed-2026-09-19-<his-idea>.md. Teach the law by doing it: capture first, no structure needed.
2. Chunk — the AI (his Claude or yours) chunks the seed into an ADR with real QSTs, each carrying ORRCF. He watches his own idea become an answerable decision surface.
3. Answer — he answers 2–3 QSTs, any shape; sees accept-or-override work; sees his reasoning LAND in the record.
4. The tree — open the extension's question view: his project, legible. ("One grep — or the tree, or the phone.")
5. If the energy is high — one glimpse of the estate from YOUR laptop: the crew registry, a wake, the iOS client with a live QST. Fifteen minutes max; it's dessert, not dinner.
The win condition isn't coverage — it's that he leaves with a repo that contains his own thinking, structured, with open questions waiting for him. That's the hook that brings people back.
5 · DEFER Deliberately NOT today (say why once, warmly)
Crews/seats on HIS machine · pneumatic wake infrastructure · kintsugi fleet adoption · docket CLI · deliberations/ballots · the iOS client on his phone. One sentence covers it: "All of this exists and composes later — today is one thread, pulled well." Overload is the failure mode that loses a Pedro; the map (card 2) already gave curiosity its addresses.
6 · LEAVE-WITH The goodbye (2 min)
His repo, pushed — his thinking, structured, questions open.
adrs.systems · the template · Marketplace "ADRs for AI" · App Store "ADRs for AI".
One explicit invitation with a date-shape ("next Saturday, same office?") — momentum dies without a next node.
Optional, if the day earned it: the SIGCSE-v co-facilitation ask, once, lightly.
PLAYBACK After the sitting
Export the JSON below (or just tell me how it went in any shape) — I fold it: pre-flight breakages become onboarding fixes, his questions become the FAQ the launch materials are missing, and the sitting becomes the first field-test record of onboarding a stranger-who-is-a-friend. Nothing typed here is lost; state lives in this browser (key pshelf0001-v1).