AI Fluency Fundamentals
The six 201 skills, the Red Pen Review, centaur vs cyborg, your first frontier sticky.
How to use a handout
- Print the handout for your week before the session, or save it as a PDF on your laptop.
- Print landscape, single-sided, A4 or US Letter. Use Chrome or Edge for best fidelity (Ctrl+P → Layout Landscape → Margins Default → Background graphics on).
- Bring it to the session. Mark up the exercises as you work, and circle the homework before you log off.
- The handout is the student companion to the slide deck. Instructors carry the matching Facilitator Pack.
The six handouts
Builder Orientation
From user to builder. Whiteboard decomposition, your first prototype, peer review.
Platform Training
Three deployed Power Platform builds — centaur, cyborg, your own problem.
Platform Training (Locked Tenant Reality)
Three deployed static-HTML builds on free public hosting. Same arc as Week 3, for tenants where Power Platform is restricted.
Advanced Workshop
Frontier mapping, complex build, debugging clinic, QA drill, teach-back, workflow playbook.
Advanced Workshop (Locked Tenant Reality)
Static-HTML Readiness Dashboard build, five-scenario debugging clinic, two-tool cross-check (genai.mil + Ask Sage), workflow playbook with Which Tool column.
Supervisor Orientation
Permission culture, the four supervisor questions, the apprentice problem.
Full-Stack Capstone
Eight build cycles. Light four architecture layers. Ship one container by 1700.
Download all six handout PDFs
Each handout ships as a one-page Letter-landscape PDF rendered from the same HTML source. Use these on shared / kiosk laptops where the print dialog is locked down, or to email a handout to a Marine before class — no print-dialog dance required.
- Download Week 1 PDF — AI Fluency Fundamentals
- Download Week 2 PDF — Builder Orientation
- Download Week 3 PDF — Platform Training
- Download Week 4 PDF — Advanced Workshop
- Download Week 5 PDF — Supervisor Orientation
- Download Week 6 PDF — Full-Stack Capstone
Regenerating the PDFs
The PDFs are produced by a headless-Chromium build script that loads each handout from the local dev server and prints to PDF with the same margins the in-browser print preview targets. To rebuild after editing a handout:
- Make sure the dev server is running:
python3 serve.py(the Start application workflow). - From the project root:
npm run build:handout-pdfs. - The script discovers Chromium and the Liberation / Noto fallback automatically; commit the regenerated files in
docs/handouts/pdf/.
Source: scripts/build-handout-pdfs.js. System
deps: chromium and (recommended)
noto-fonts via Nix; npm dep:
puppeteer-core.
What each handout contains
- Header strip — course name, week, duration, audience, prerequisites at a glance.
- Module strip — every module with start time and posture (talk / build / break) so you know where you are.
- Bring with you — accounts, tools, reading, and the artefacts (notes, prototype, frontier map) you owe before walking in.
- Key terms — the vocabulary you’ll hear in the room, defined in one line each.
- Exercises in class — the live activities, the prompts, and what “done” looks like for each.
- What you’ll be able to do — the concrete capabilities you walk out with.
- Homework — the assignment that gates the next session, with a realistic time budget.
Out of scope
These handouts are student-facing only — no facilitator hand-off cues, no recovery scripts, no speaker notes. If you are teaching a session, use the matching Facilitator Pack. The full slide decks live under Decks, and the live course pages are under Courses.