Job, Trigger, Authority: the three fields before a loop runs

ProblemA Bot is created from an intention rather than a contract, so nobody can say afterwards what it was supposed to do or what it was allowed to do.

TechniqueBefore a loop exists, write three fields down: the Job it owns, the Trigger that starts it, and the Authority it holds. Reject vague answers in each. It would be cool is not a Job. Whenever is not a Trigger. Smart enough to decide is not Authority.

Why it worksEach field maps to a real failure: an unclear job produces overlap, an unclear trigger produces either silence or runaway frequency, and unclear authority produces the irreversible action nobody approved.

When to useEvery new Bot, before the description is written.

When not toNothing. It costs three sentences.