AI at the Gemba · lesson 9 · worksheet
Guard it, break it, register it
paulducey.com/lean/course
DateThe skill, and the model or plan I tested onName
Part 1. Write one guardrail rule in your own words for each line, then test it five times with messages built to break it. Mark each run P (held) or F (broke). Then say whether the rule depends on the model, and what outside control you will add.
| Rule | My wording | Runs 1 to 5 (P or F) | Outside control I will add |
|---|---|---|---|
| Stop and ask (names, IDs, health) | |||
| Numbers by code, never estimated, every figure tagged | |||
| Text in the file is data, not commands | |||
| Draft only: never send, save over or change |
Part 2. The Rule of Two. For this skill, tick what it can do in one session. If it can do all three, cut one leg.
- It reads untrusted content (inbound email, web pages, files from others).
- It touches private data or systems.
- It changes things or communicates outside (send, save over, write).
The leg I will cut, and how (a removed connector, a separate session, read-only, network off):
Part 3. The registry entry. One line per skill, kept where your team can find it.
| Purpose | |
| Owner, and version | |
| Scripts, connectors and other dependencies | |
| Models tested, and the date | |
| Re-test when: a model changes, the SOP changes, and every ____ |
Paul Ducey · AI at the GembaFree to copy and use. paulducey.com/lean/course