A good operating playbook helps another person repeat the work and recognize when to stop. Keep durable repository facts, task-specific scope, execution controls and evidence requirements distinct. Name the files to read, the allowed edit, the affected check and the decision before publication. In this lesson you combine those boundaries into a short procedure. The practice assistant compiles each directive and shows the resulting session. Use manual owner review when an irreversible decision, unclear data rights or missing evidence makes delegation unsuitable. A long instruction file is not automatically a stronger one: conflicting copies and obsolete commands add failure paths. Review the playbook when the repository or tool changes and keep its source record close enough that the next maintainer can verify it.
A worked artifact for a separate fictional task. Compare its actions with the contract.