Teaching loop design
One loop design covering action, feedback, failure, and the learning check
Live Playbook outputs appear as definitions when a recipe already names a target artifact. The cash-flow loop is a worked example of definition, instance, workflow, and history. This site does not post to a ledger or auto-reconcile.
Search first (⌘K / Ctrl+K, or /). Filters stay progressive: domain up front, four more in the panel. Health on cash-flow rows is example-only.
Definition mapped from a published Playbook recipe that already names this output. There is no live instance ledger on this site.
Read
This page is the definition. No instance is published on this site.
Change
Publish and merge stay with Wik. Controls below name review and approval; this site does not edit live ledgers.
- Purpose / beneficiary
- One loop design covering action, feedback, failure, and the learning check For The learner the loop is meant to teach, and the owner who accepts the design.
- Decision supported
- Design one teaching game loop and stop before shipping it.
- Owner / authority
- Named design owner accepts the loop and controls build, release, and spend · Agent-assisted
- Current status
- Proposed
- Latest instance
- None on this site.
- Next event
- No instance due on this site
Update policy
- Cadence
- Event-driven
- Freshness / next event
- No instance due on this site
- Reviewer
- Named design owner accepts the loop and controls build, release, and spend
- Approver
- Same as owner unless named
- Event triggers
- A learning outcome and owner are accepted
- Publish rule
- Agent-assisted draft; human judgment still gates publish.