{"found":true,"collection":"patterns","library_url":"https://www.grokbotdb.com/library/pat.no-commit-rule","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.no-commit-rule","name":"The Bot that touches code never ships","category":"safety","problem":"An agent with repository access will merge or deploy something at the first ambiguous moment.","technique":"Standing rule in the description: it does not commit, push, merge or deploy, ever. It gathers context, stages the prompt, hands the job to the build system, verifies, and reports with evidence.","why_it_works":"Merges and deploys are the irreversible actions in a development workflow, so they are exactly where the boundary belongs.","when_to_use":"Every Bot with repository or infrastructure access.","manual_ref":"1.9","evidence":"reported","attributed_to":"Paul Klay","related":["pat.outer-loop","pat.green-amber-red","pat.scoped-permissions-over-written-boundaries"],"confidence":"high","first_seen":"2026-09-03","last_verified":"2026-09-03"}}