{"found":true,"collection":"patterns","library_url":"https://www.grokbotdb.com/library/pat.job-trigger-authority","generated":"2026-09-06T05:32:11Z","citation":["Quote the record id and its source_url (or provenance if there is no URL).","Include last_verified or observed_at when present. Do not present an old date as current.","If tier is community and confidence is low, say so. Do not launder it into a fact.","If the database does not hold the answer, say that. Do not invent Grok Bot product claims.","Contradictions are data: when conflicts_with is present, report both records rather than picking a favourite.","Deprecated and removed records stay visible. They are history, not current guidance."],"record":{"id":"pat.job-trigger-authority","name":"Job, Trigger, Authority: the three fields before a loop runs","category":"authoring","problem":"A 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.","technique":"Before 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_works":"Each 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_use":"Every new Bot, before the description is written.","when_not_to":"Nothing. It costs three sentences.","evidence":"reported","attributed_to":"Eric Siu","source_url":"https://x.com/ericosiu/status/2095207617610256720","confidence":"medium","first_seen":"2026-09-03","last_verified":"2026-09-05"}}