{"found":true,"collection":"failure_modes","library_url":"https://www.grokbotdb.com/library/fm.no-audit-trail-for-review","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":"fm.no-audit-trail-for-review","title":"There is no queryable record of what a Bot actually did","symptom":"After an incident, the only evidence is per-Bot chat transcripts, not queryable across a team, and only the 20 most recent run records per routine.","cause":"An audit view is described in the docs as coming. Per-run usage metering, success-rate benchmarks and export paths between Bots are all unpublished.","detection":"Discovered at the moment an incident needs reconstructing, which is the worst time.","fix":"Export run-history evidence into source systems as the routine runs, rather than relying on in-product retention. Require every routine to write a reviewable artifact with source links.","severity":"medium","source_id":"src.tp.eesel.review","source_url":"https://www.eesel.ai/blog/grok-bot-review","confidence":"medium","first_seen":"2026-09-03","last_verified":"2026-09-03"}}