{"found":true,"collection":"patterns","library_url":"https://www.grokbotdb.com/library/pat.give-every-routine-a-ceiling","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.give-every-routine-a-ceiling","name":"Write a ceiling into every scheduled instruction","category":"safety","problem":"The realistic failure is not a Bot doing something forbidden. It is a Bot doing something permitted four hundred times because an upstream page changed shape overnight and every item now matches the filter.","technique":"Cap volume, cap spend, and state what to do when the world looks strange, in the instruction itself.","why_it_works":"A boundary constrains category; a ceiling constrains quantity, and quantity is what actually goes wrong.","when_to_use":"Every routine and every trigger.","manual_ref":"3.9","evidence":"documented","related":["pat.narrow-event-triggers","pat.report-your-inputs","pat.measure-cost-after-not-before"],"confidence":"high","first_seen":"2026-09-03","last_verified":"2026-09-03"}}