Week 4 Facilitator Hand-Outs

FRONTIER MAP — [Your section]
Tool tested:  [GenAI.mil / CamoGPT / other — note one]
Date / Initials:  [DDMMMYY] / [Initials]

Rules of the road
- Each cell = one specific task somebody on your team did this month.
- "Inside"  = AI handled it well.   "Outside" = AI failed (you saw it).
- "Moving"  = re-test next quarter; mark a date.
- If "Outside" is empty, you are overestimating AI. Fix that before the share-out.

| # | Category                       | Inside frontier (AI handles) | Outside frontier (AI fails) | Moving frontier (re-test by) |
|---|--------------------------------|------------------------------|-----------------------------|------------------------------|
| 1 | [e.g. Document generation]     |                              |                             |                              |
| 2 | [e.g. Data analysis]           |                              |                             |                              |
| 3 | [e.g. Process automation]      |                              |                             |                              |
| 4 | [e.g. Reference lookup]        |                              |                             |                              |
| 5 | [e.g. Training development]    |                              |                             |                              |

Share-out (90 sec each):
  1) One INSIDE-frontier task that surprised you.
  2) One OUTSIDE-frontier task you have personally seen fail.
  3) One MOVING-frontier item to re-check next quarter.

QA DRILL — Find the 5 issues. Time yourself. Typical: 5–10 minutes.
Apply the five protocols: Source • Data • Logic • Format • Domain.

----------------------------------------------------------------
STANDARD OPERATING PROCEDURE
Marine Corps Detachment, 99th Training Group

Subject:   Unit Check-In / Check-Out Procedure
Reference: (a) MCO 1000.6B, Individual Records Administration
           (b) NAVMC 11800/4 (Rev 03-2025), Check-In/Check-Out Sheet

1. Purpose. To establish standardized procedures for all personnel
checking in to and checking out of Marine Corps Detachment, 99th
Training Group. All personnel shall complete check-in within 72 hours
of reporting aboard.

2. Scope. This SOP applies to all Marines, Sailors, and civilian
personnel assigned to or transferring from the Detachment.

3. Procedure — Check-In. Personnel reporting aboard shall complete
the following steps in order:

  Step 1: Report to the Officer of the Day (OOD) with original orders
          and ten copies of PCS orders.
  Step 2: Obtain a check-in sheet per reference (b).
  Step 3: Receive unit orientation brief from S-1 covering unit
          organization, key personnel, and local policies.
  Step 4: Report to assigned section SNCOIC/OIC for introduction and
          initial task assignment.
  5.      Report to S-1 for initial in-processing, including service
          record book review and page 11 entry.
  6.      Complete remaining check-in sheet signatures (S-3, S-4,
          Medical, Dental, IPAC) within 48 hours of reporting.

4. Procedure — Check-Out. Personnel transferring from the unit shall
initiate check-out procedures no later than 10 working days prior to
the date of detachment.
----------------------------------------------------------------

Drop your findings in chat at the timer. We will reveal the five
errors one at a time in the debrief.

TEACH-BACK PREPARATION TEMPLATE — fill this in 5 minutes, then teach in 3.

Pick ONE concept from EDD:
  centaur vs. cyborg • frontier mapping • context-building •
  iterative refinement • verification protocols • the jagged frontier

Concept:                  [Which concept are you teaching?]
One-sentence definition:  [Define the concept in one clear sentence.]
Why it matters:           [One sentence on why this concept is important.]
Real example from your work:
                          [A specific example from your actual job where
                           this concept applied. Names, dates, the task.]
Common mistake:           [One mistake people make when applying it.]
Key takeaway:             [One sentence the audience should remember.]

Peers grade you on three things:
  1) Could they explain it back to someone else?
  2) Was your example concrete enough to be believable?
  3) Do they know what to do differently tomorrow because of you?

----------------------------------------------------------------
WORKED EXAMPLE — Centaur vs. Cyborg (read this verbatim if helpful)

Concept:                  Centaur vs. Cyborg modes.
One-sentence definition:  Centaur mode means human does some tasks and
                          AI does others separately; Cyborg mode means
                          human and AI work together iteratively on the
                          same task.
Why it matters:           Using the wrong mode causes either wasted time
                          or quality failures.
Real example from my work:
                          When I built a training schedule, I used Cyborg
                          mode for the draft but switched to Centaur mode
                          for the final verification because accuracy was
                          critical.
Common mistake:           People stay in Cyborg mode for accuracy-critical
                          work and don't slow down to verify.
Key takeaway:             Match the mode to the risk level of the task.
----------------------------------------------------------------

Pick your concept now. 5 minutes silent. Breakouts open at the timer.

WORKFLOW PLAYBOOK — one page, one workflow

Author:    [Name / Section]
Date:      [DDMMMYY]

| Field                  | Content                                                       |
|------------------------|---------------------------------------------------------------|
| Task                   | [A specific, recurring task from your job]                    |
| Frequency              | [How often you perform this task]                             |
| Mode                   | [Centaur / Cyborg — pick one and say why]                     |
| Step 1                 | [H or AI:]  [Concrete action]                                 |
| Step 2                 | [H or AI:]  [Concrete action]                                 |
| Step 3                 | [H or AI:]  [Concrete action]                                 |
| Step 4                 | [H or AI:]  [Concrete action]                                 |
| Step 5 (optional)      | [H or AI:]  [Concrete action]                                 |
| Step 6 (optional)      | [H or AI:]  [Concrete action]                                 |
| Verification checklist | [3–5 items that MUST be checked before output is final]       |
| Known frontier issues  | [Where AI has failed on this task before — your real data]    |
| Time savings estimate  | [Without AI: ~__ hrs   →   With AI: ~__ hrs]                  |
| Junior development     | [How this preserves skill-building for junior personnel]      |

Completion bar
- 4+ steps, each labeled H or AI.
- Verification checklist with 3+ items.
- At least one real frontier issue you have personally hit.
- A time savings estimate from your own data, not a guess.
- A junior development note that is actionable.

If your playbook has no verification checklist, it is not done.
Submit your playbook in this chat at the 20-minute mark.