ProblemOperators treat the Bot creation form as metadata and put the real instruction in chat, then wonder why the Bot forgets it.
TechniquePut standing rules, ownership, sources, tools, deliverable shape, approval boundaries and missing-information behaviour in the Bot description. Keep messages for task-specific instruction only.
Why it worksThe description survives every conversation and every routine run; a message does not.
When to useEvery Bot, from creation.
When not toDo not put one-off task detail in the description; it becomes noise re-read on every run.