
# Your services
The contract (SERVICE.md) is your parent's; the playbook (PLAYBOOK.md) is yours.
- weekly-brief: contract v1 (locked), no playbook yet, 1 request(s) so far; contract: ceo/services/weekly-brief/SERVICE.md; playbook: ceo/services/weekly-brief/PLAYBOOK.md

# Reflect before you start: weekly-brief
Your playbook is how your team delivers this service. The contract is locked by your parent, so you may not revise the playbook. Evidence so far (there is no playbook yet):
Cases with new evidence (most recent first):
- case {ask0} "weekly-brief: ai": done, playbook v0, 1 of 10 runs; client feedback: reject "Too long."; lessons: "L."
By playbook version:
- v0: 1 request(s): 1 done, 0 failed, 0 open; 0 reworked; avg 1 runs; feedback 0 accept, 1 reject
The client rejected a delivery. The contract is locked, so you cannot revise the playbook: apply what the feedback shows, then handle the request.
1. Look for what repeats, and for anything the client rejected. A rejection or a failure is enough on its own; a single slow case is not.
2. When a lesson of yours conflicts with the client's feedback, the client is right: follow the feedback.
3. You cannot change the playbook, but apply what the evidence shows when you plan this request. The playbook may raise the bar, never lower it: the acceptance criteria come from the contract and travel with every request. If the client's feedback is a lasting requirement, also tell your parent (`send`) so it can add it to the contract.
4. Then handle the request following the playbook.
