Week 3.5 Instructor Cheat Sheet

A two-page printable reference card for the Course 3.5 Platform Training (Locked Tenant Reality) deck. Designed to sit next to the deck during the four-hour Teams session so you never have to scrub back through 35 slides for a build spec, a switch cue, or the next failure share.

Print: Ctrl+P → Layout Portrait, Margins Default, Background graphics on. Two US Letter pages. Site chrome and this preview note are hidden in print.

Use: page 1 is the live-delivery card. Pacing strip, the three build specs to drop in chat, the failure share script, the centaur and cyborg posture switches. Page 2 is anchors you repeat all afternoon, recovery cues for when hosting or genai.mil misbehaves, and the homework that gates Week 4.

3.5Course 3.5 · Platform Training
(Locked Tenant Reality)
Instructor cheat sheet

Platform Training (Locked Tenant Reality)

Three deployed static-HTML tools in four hours. Build #1 Centaur (Watch Bill), Build #2 Cyborg (TEEP), Build #3 your own. Plus the Capability Gap Map artifact for HQMC.

4 hr · 6 modules + Capability Gap Map wrap
35 slides · 2 breaks · 3 editor switches
Companion to week-3-5-platform-reality.html
0:00M1 Setup + Hosting
0:15Build #1 Centaur
1:20Brk + Share 10′
1:30Build #2 Cyborg
2:30Break 10′
2:40Build #3 Your Own
3:30Frontier + Gap Map
115 min
Setup, Hosting, Review 0:00,0:15 Framing + GitHub Pages walkthrough
  1. Three Layers anchor (Slide 5): Spec (genai.mil), Prototype (static HTML on public host), Production (the wishlist). Today we work two, document the wall on three.
  2. Hosting walk (Slide 8): walk every Marine through a placeholder repo + GitHub Pages toggle. If they can't reach github.io by minute 14, switch them to local file:// for the day and add a Capability Gap Map row.
  3. Tabs check (audible): deck, this cheat sheet, genai.mil, github.com (signed in), a text editor. Confirm clipboard copies from browser into Outlook on this workstation.
Outcome · calibration Every Marine has a live github.io URL Anyone blocked is paired and on file:// fallback. Nobody discovers a hosting issue during Build #1.
B165 min
Build #1, Watch Bill Builder 0:15,1:20 Centaur · you know the answer
  1. Phase 1 (0:15,0:35): whiteboard only. No AI. Define inputs, rules, outputs, edge cases, out-of-scope (those become Capability Gap rows).
  2. Phase 2 spec (paste verbatim): see Build #1 full-plan handoff block in the chat-paste handouts pack. Single file, inline CSS and JS, no external dependencies, mobile responsive, prints clean, copies clean.
  3. Posture brief (read aloud): "Centaur mode means you design the logic; AI writes the code. No exploration. You know the answer before you prompt."
  4. Phase 3 verification: six edge cases out loud. Empty roster, all on leave, days=0, days=400, single Marine over 14 days, copy-to-Outlook test.
  5. Coach in chat. Phase 4 fix prompts are targeted, not "redo the file."
Deliverable · build #1 Watch Bill on a public URL A 14-day bill prints clean, the email body pastes into Outlook with the monospace table intact. URL openable on phone.
BRK10 min
Break + failure share. Be back at H+1:30. Run the failure share slide on return. Surface 2,3 Marines' Build #1 errors. Do not solve. Pattern-match into prompt / edge case / CSS specificity / clipboard variance. 1:20,1:30
B260 min
Build #2, TEEP Builder 1:30,2:30 Cyborg · you don't know the answer
  1. Hand-off (1:30): deck → editor. Switch posture audibly: "Now it's exploratory. You drive, AI rides shotgun."
  2. Iteration 1 spec: bare CRUD with localStorage. See chat-paste block.
  3. Iteration 3 deliberate failure: the conditional-styling prompt. Do not warn students. Let AI hand back broken inline-style or specificity-losing code. When hands go up, ask the four questions: what did the AI tell you, what result did you expect, what did you get, what would you ask it to clarify.
  4. Iteration 4 fix: students re-prompt for class-based styling. They learn the lesson by experiencing the failure.
  5. Roam in chat. Students who lock in too early get "What's the path you didn't try?"
Deliverable · build #2 TEEP + S-3 brief paragraph Plus one restructured approach documented in chat. That's the cyborg artifact, not just the tool.
BRK10 min
Break. Be back at H+2:40. Reset your screen-share to a fresh genai.mil conversation. Have the Build #3 declarations slide queued. 2:30,2:40
B350 min
Build #3, Your Problem 2:40,3:30 Choose mode · deploy
  1. Declarations (2:40): each Marine states one sentence (tool + user), one mode + why, two specific frontier risks. If they can't name two specific risks, revise before they start.
  2. Brief (read verbatim): "Pick one tool from your unit's real backlog. State in chat which mode and why. CUI is OK in your genai.mil prompts. No CUI in the file you publish. Deploy by 3:25 and post the URL."
  3. Coach, do not solve. When stuck: "What would you tell the AI about what is going wrong?"
Deliverable · build #3 Deployed URL in chat If they didn't finish, they owe the URL by EOW. The Week 4 gate hangs on it.
F20 min
Frontier Map + Capability Gap Map 3:30,3:50 Two artifacts
  1. Frontier sync (Slide 29): "Across all three builds, where did AI land inside the frontier? Where did it fall outside? Add at least two specific rows to your unit's map."
  2. Capability Gap Map (Slide 30): "For each build, name the production-layer capability that would 10x the tool. Then name the specific connector, license, or admin grant that blocks it. Specifics, not generalities."
  3. Worktime (Slide 31, 10 min): set a literal timer. Walk the room. Push back on generic entries.
  4. Issue the Week-4 gate: at least one deployed URL plus two Capability Gap rows due 72 h before Week 4. No URL, no seat.
Outcome · both artifacts Frontier + Gap Map filed Each Marine logs at least one row in each map. Instructor consolidates and forwards through the unit AI POC to HQMC.
EDD · Week 3.5 cheat sheet · page 1 of 2 · pacing, build specs, deliverables Print landscape off · portrait, default margins, background graphics on
3.5Course 3.5 · Cheat sheet
page 2

Anchors, recovery, homework

The phrases you repeat all afternoon, the failure modes to watch for when hosting or genai.mil misbehaves, and the homework that gates Week 4 attendance.

Use during: 1:20 failure share
Use during: any hosting glitch
Companion to week-3-5-platform-reality.html

Pre-flight + hand-off cuesDone 48 h before; verified at T-30 min · three editor switches today

  • Hosting reachability test. From the actual classroom or duty workstation, open the reference build URL. Loads? Tier 1 is good. Blocked? Try Tier 2 from the cheat sheet. All blocked? Plan for file:// fallback and put it on the Gap Map.
  • Tabs and portals. Deck (Week 3.5), this cheat sheet, genai.mil, github.com (signed in), a text editor, the two reference builds in pinned tabs.
  • GitHub account sweep. Send the sign-up link to anyone without an account 24 h out. Two-factor takes 10 min the first time; resolve before class.
  • Sample roster ready. Have a stand-in roster of 8,9 fictional Marines (the reference build's seed roster works) on a sticky in case a Marine forgets one.
  • Course 2 failures collected. Pull homework failure cases from the Week 2 chat into a one-screen list for the 1:20 failure share.
  • 0:15. Deck → editor + genai.mil side-by-side. Drop Build #1 full-plan prompt into chat.
  • 1:20. Return to deck. Failure share. Pattern-match, do not solve.
  • 1:30. Deck → editor for Build #2. Switch posture audibly.
  • 2:40. Deck → each Marine's editor. Declarations in chat.
  • 3:30. All laptops up. Capability Gap Map worktime begins.

Anchor phrasesPlant in M1; cite by name when you need them

  • 1. "Centaur when you know the answer. Cyborg when you don't. Pick on purpose." Open with it; cite at every build hand-off.
  • 2. "Power Apps skills die when you turn in your CAC. HTML skills don't." The thesis. Cite when a Marine questions why we are not using Power Platform.
  • 3. "We work every layer we can reach. We document the wall where the work stops." The Three Layers framing.
  • 4. We pattern-match, we don't solve. The failure share is diagnosis, not group debugging.
  • 5. CSS class names beat inline styles. Iteration 3 of Build #2 is where this lands. If a Marine has lost specificity, the answer is almost always a class.
  • 6. Try one path you discard. Cyborg without exploration is just slow centaur. The discarded path is the artifact.
  • 7. Map the world as it is. Tenant gaps are Capability Gap rows, not complaints. Specifics. Beneficiary counts. Time savings.
  • 8. Deployed beats demoed. A URL in chat is the only acceptable Build #3 artifact.

Recovery + pacing cuesWhen hosting or genai.mil misbehaves, this is the order of operations

  • github.io blocked from this network. Try GitLab Pages or Cloudflare Pages from the cheat sheet. If all blocked, switch to file:// for the day and add "Public static hosting reach blocked" as a Capability Gap row.
  • GitHub account not set up. Walk the Marine through sign-up at the projector while everyone else is on Phase 1 whiteboarding. Two-factor takes 10 min.
  • genai.mil session reset mid-build. Start a new conversation. Paste the current state of the file plus a one-line "I'm at Phase 4 fixing X." Specificity beats restart.
  • Clipboard refuses to copy from browser. Some DoD workstations block it. Use right-click → Copy on the textarea. If that's also blocked, dictate the email or screenshot it. Gap row.
  • AI returns the wrong thing on first pass. Expected. Coach: "What did the AI tell you, what result did you get, what would you ask it to clarify?" Do not paste the fix.
  • Marine finishes Build #1 in 30 min. Stretch: add localStorage to the watch bill so the roster persists. Or pair as navigator with a stuck Marine.
  • Whole room is behind at 2:30. Compress Build #3 to spec-only, no deploy. Protect the Capability Gap Map worktime. That artifact is the Week 4 hand-off.
  • Pacing valve. If behind at 1:20, cut the failure share to one Marine and the Build #2 framing to two sentences. Never cut the Capability Gap Map worktime.

Homework to issue before logoffSlide 33, Week 4 attendance gate hangs on these

  • Polish Build #3. Keep the URL live. If you didn't finish, ship the smallest defensible version by EOW. Post the URL in the Week 3.5 chat thread.
  • Run one build through the EDD SOP QA process. Don't skip the verification checkpoints.
  • Document three failure cases. Log on the shared frontier-map doc.
  • Add at least two Capability Gap Map rows. Real, specific, named. Instructor consolidates quarterly to HQMC AI working group.
  • Identify one capability surprise. Somewhere AI performed better than you expected.
  • Week 4 gate. To attend Advanced Workshop, post evidence (deployed URL or screenshot) plus two Gap Map rows by 72 h before Week 4. No evidence, no seat.
EDD · Week 3.5 cheat sheet · page 2 of 2 · anchors, recovery, homework Pair with the Week 3.5 Facilitator Pack for prep / hand-off / homework detail