{"found":true,"collection":"facts","library_url":"https://www.grokbotdb.com/library/fact.repos.adamanz-not-a-boundary","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":"fact.repos.adamanz-not-a-boundary","subject":"security","claim":"Separate Grok Bots share one cloud computer, so splitting work across Bots does not create a security boundary.","kind":"risk","status":"current","tier":"code","source_id":"src.repo.adamanz.grok-bot-skill","source_url":"https://raw.githubusercontent.com/adamanz/grok-bot-skill/main/README.md","quote":"separate bots share a single cloud computer environment, so they don't create security boundaries","observed_at":"2026-09-03","confidence":"high","notes":"Corroborated by the official docs overview (isolation is per user, not per Bot) and by a Cursor forum thread titled 'Bots are not a security boundary'.","first_seen":"2026-09-03","last_verified":"2026-09-03"}}