纠错日志：每周把「不是这个意思」变成你批准的规则

（作者英文原文）Help me set up a correction log so my Bots get better at working the way I want.

Keep existing permissions for sending, buying and publishing unchanged.

1 - Create a shared correction log.

Choose a location the relevant Bots can read and update. Use an existing shared workspace where possible, and confirm access.

For each useful correction, record the date, Bot name, task, what it did, what I wanted instead, and a proposed rule that could prevent the same mistake.

Track each lesson as: new (captured), proposed (ready for my review), approved (I’ve agreed), applied (the Bot’s instructions have been updated), or rejected (not becoming a rule).

2 - Roll out correction logging across my Bot team.

Add this instruction to each Bot:

“When I correct your work, record any reusable lesson in the shared correction log. Include what you did, what I wanted instead, and a proposed rule that could prevent the same mistake.

Distinguish a lasting preference from a one-off request. If unsure, flag it for review. Link to the example where possible, then continue with the corrected work.

Don’t make a proposed lesson a permanent rule until I approve it.”

Confirm each Bot has the instruction and can write to the shared log.

3 - Review the patterns weekly.

Prepare a Monday 8am review in my timezone, owned by you as Chief of Staff.

Group similar corrections from the previous week. Propose a change when a correction repeats or I flag it as important.

For each proposal, show the examples, affected Bot, exact wording and where it belongs: instructions, a skill or memory. Check for conflicts with existing rules.

Send one short list I can approve or reject. Apply only approved changes through a supported method, and confirm which were actually saved.

4 - Keep examples of what good looks like.

When I identify an output I love, save it with a short explanation of why it worked. Reference it in relevant proposals so the Bot has a concrete standard.

5 - Check whether it helps.

Report corrections per Bot and repeat corrections after a change was applied. Include completed-task counts where available, so a quieter week isn’t mistaken for improvement.

Before creating the routine or changing instructions, show me a sample log entry and weekly review. Clearly label illustrative examples.

After approval, confirm the log location, participating Bots and saved schedule.