# Three-minute adoption recipes — 6.2

Two invented office exercises prepare an evidence checklist or an unsent lessons-review reminder. Two separately labelled platform handoffs cover Power Automate and Copilot in Word. The 30/90/60-second guide is a suggested timebox; elapsed seconds are explicitly self-reported. There is no connected tenant or external automation execution.

**Set recipe and prerequisites** records simulated account/license access, permission and synthetic-only data. Unknown or failed prerequisites stop preparation. **Prepare local exercise output** mechanically selects non-current AR records while preserving their text/status. **Load recorded AI reminder** uses an actual assistant-authored 2026-10-03 response only for the unchanged original reminder case. A source/context edit makes output stale. **Verify exercise output** requires the exact unresolved IDs, draft interpretation and an explicit record comparison. The default answer is AR2 and AR3. Click-through is insufficient. **Undo local exercise output** removes the exercise result while retaining inputs; the handoff JSON is released only after result checks pass.

The guide distinguishes documentation verification from a tenant-tested recipe. Platform instructions were checked on 2026-10-03 against these official sources:

- [Microsoft data operations](https://learn.microsoft.com/en-us/power-automate/data-operations): Compose, Filter array and CSV output.
- [Microsoft test/run guide](https://learn.microsoft.com/en-us/power-automate/get-started-with-cloud-flows): manual test and run history.
- [Microsoft turn-off/delete guide](https://learn.microsoft.com/en-us/power-automate/disable-flow): verify off status; pending runs can continue.
- [Microsoft Copilot in Word drafting](https://support.microsoft.com/en-gb/word/copilot/draft-and-add-content-with-copilot-in-word): eligible access, document drafting and review before keeping/discarding.

Only the local exercise was implemented/tested here. The external handoff requires authorised environment/document access and its own actual verification. No notification is sent and no credentials are requested. Compared with generic adoption advice, the recipe has known expected records and an undo path. Live contextual AI coaching and external execution remain separate work. Tests cover stops, substantive output checks, staleness, undo, immutable recorded provenance, explicit unknowns and reopen.