{"meta":{"exportedAt":"2026-10-19T07:31:14.922Z","formatVersion":2,"selection":{"q":"essay","system":"","harm":"","context":"","country":"","role":"","relation":"","evidence":"","year":"2026","response":"","severity":"","verification":"","view":"incidents","sort":"added"},"totalIncidents":4,"coverage":{"cases":4,"countries":1,"languages":3,"unknownLocation":3,"locationPending":0,"unknownLanguage":0,"unknownDate":0,"lawsuits":0,"regulatory":0,"minors":0,"coreRelations":2,"contextualRelations":1,"mixedRelations":0,"unknownRelations":1,"relationPending":0,"relationUnknown":1},"countingNote":"Distinct public cases in this selection. People counts apply within individual cases only; cross-case person overlap has not been resolved. No population incidence estimate.","affectedCountNote":"Interpret person counts with affectedCountStatus and the reported effects. Unquantified zeros are placeholders, not a measured zero.","source":"AI incidents","publisher":"NOPE","url":"https://nope.net/incidents","license":"CC BY 4.0"},"incidents":[{"id":"2026-edtech-customer-success-manager-says-40-staff-laid-off-as-ceo-read-claude-generated-script-on-replacing-roles-with-ai-first-person","caseFacts":{"claims":[{"id":"c1","status":"reported","evidence":[{"locator":"At the end of 2025, when the company began its push to transform into an “AI-first” outfit, I was more than a bit concerned.","relation":"supports","source_id":"s1"}],"assertion":"The author says the education technology company they worked for began a push at the end of 2025 to become 'AI-first'.","causal_attribution":"Author's account; context."},{"id":"c1b","status":"reported","evidence":[{"locator":"It started small—directions to run documents through Claude first and use an AI notetaker for meetings, all while we were told our company would still be “human first.” But there are “levels” to AI adoption. Before long, our required AI use expanded to include scheduled AI tasks, AI-generated decks and documents","relation":"supports","source_id":"s1"}],"assertion":"The author says the company's required AI use started with running documents through Claude and using an AI notetaker and grew to include scheduled AI tasks and AI-generated decks and documents.","causal_attribution":"Author's account; context."},{"id":"c2","status":"reported","evidence":[{"locator":"An hour after I was laid off, my former CEO held a seven-minute all-hands meeting to read a Claude-generated script about how leadership had “made some hard decisions but are ultimately replacing these roles with AI.”","relation":"supports","source_id":"s1"}],"assertion":"The author says that an hour after being laid off, the CEO held a seven-minute all-hands meeting to read a Claude-generated script saying leadership was replacing these roles with AI.","causal_attribution":"Author's account of leadership's stated reason; the Claude origin of the script is the author's statement."},{"id":"c3","status":"reported","evidence":[{"locator":"With one decision, the company let 40 people go, about 20 percent of the workforce","relation":"supports","source_id":"s1"}],"assertion":"The author says the company let 40 people go in one decision, about 20 percent of the workforce.","causal_attribution":"Author's account; the figure is the author's."},{"id":"c3b","status":"reported","evidence":[{"locator":"If the employee couldn’t attend the HR-led meeting, they were sent an email notifying them that their role was terminated, effective the following business day.","relation":"supports","source_id":"s1"}],"assertion":"The author says staff who could not attend the HR meeting were told by email that their roles ended the next business day.","causal_attribution":"Author's account."},{"id":"c4","status":"reported","evidence":[{"locator":"The timing around this layoff was strange—we were days away from entering our busiest time of the year. Sales were down year over year, and the general feeling was that things weren’t going so well. Customers weren’t happy with the product, and the company wasn’t meeting its timelines.","relation":"supports","source_id":"s1"}],"assertion":"The author says the layoff came when sales were down year over year, customers were unhappy with the product and the company was missing its timelines.","causal_attribution":"Author's account of other circumstances that may bear on the layoff."},{"id":"c5","status":"reported","evidence":[{"locator":"I am lucky that I have savings and a partner who is still employed. To be honest, losing my job has led to more relief than anything else.","relation":"supports","source_id":"s1"}],"assertion":"The author says they have savings and an employed partner and that losing the job brought more relief than anything else.","causal_attribution":"Author's account; mitigating context."},{"id":"c6","status":"reported","evidence":[{"locator":"It’s been months since I lost my job and I’m still not sure if there’s an answer to that question.","relation":"supports","source_id":"s1"}],"assertion":"In one passage the author says it has been months since they lost the job.","causal_attribution":"Author's account; bears on the layoff date."},{"id":"c7","status":"reported","evidence":[{"locator":"A few weeks after being laid off, I keep asking myself, if a human-centered job like mine can be done by AI, what does this say about our society?","relation":"supports","source_id":"s1"}],"assertion":"In another passage the author writes of the time 'a few weeks after being laid off'.","causal_attribution":"Author's account; bears on the layoff date and conflicts with c6."}],"effects":[{"label":"the author and 39 colleagues laid off in a decision leadership attributed to replacing the roles with AI (author's account)","claim_id":"c2","direction":"negative"},{"label":"the author reports relief at leaving, with savings and an employed partner (author's account)","claim_id":"c5","direction":"positive"}],"sources":[{"id":"s1","url":"https://www.oaklandreviewofbooks.org/how-ai-replaced-me/","kind":"personal_essay","access":"read","language":"en","translation_note":"Read in English by the research agent (an AI) on 2026-10-19: the full essay page (HTTP 200) from oaklandreviewofbooks.org, published 2 Oct 2026 in a series of first-person stories about the tech industry; no translation and no human reviewer.","independence_group":"oakland-review-of-books-how-ai-replaced-me-author"}],"version":1,"ai_roles":["institutional_use"],"contexts":["work"],"unknowns":["The company's name and location, and the date of the layoff (the essay places it after the end-2025 AI push and an April rollout, and says both months and weeks have passed).","Which AI system, if any, took over the eliminated work.","Whether the CEO's script was generated with Claude, beyond the author's statement.","The company's own account of the layoff and its reasons, including falling sales."],"geography":{"basis":"The essay does not say where the company is based. Customer school districts and the author's personal history are not evidence of the event's location.","court_countries":[],"event_countries":[],"affected_person_countries":[]},"publication":{"basis":"Published as a consequential-response case under the public-forum rule: a concrete first-person essay describing a layoff of 40 staff that the employer's leadership attributed to replacing the roles with AI. Described with attribution and without corroboration; the author's account of falling sales and the author's relief at leaving are recorded.","reviewed_on":"2026-10-19"},"ai_involvement":{"basis":"The author writes that, an hour after the layoff, the CEO read the staff a Claude-generated script saying leadership was replacing the eliminated roles with AI, after a push since the end of 2025 to make the company 'AI-first'. This is a reported institutional response to AI adoption: no AI output or action toward the laid-off staff is described, the system meant to do their work is not named, and the Claude origin of the script is the author's statement.","status":"reported"},"person_relations":["unknown"]},"name":"First-person essay: edtech customer success manager says 40 staff were laid off and the CEO read a Claude-generated script on replacing their roles with AI","summary":"In a first-person essay published by the Oakland Review of Books on 2 October 2026, a former customer success manager at an education technology company writes that the company began a push at the end of 2025 to become 'AI-first', requiring staff to use AI tools, and that the author was later laid off. The author writes that an hour after the layoff the CEO held a seven-minute all-hands meeting to read a Claude-generated script saying leadership was 'replacing these roles with AI', and that the company let 40 people go, about 20 percent of its workforce, at the end of about six months of role eliminations. Staff who could not attend the HR meeting were told by email that their roles ended the next business day. The author also writes that sales were down and customers were unhappy, and that losing the job brought more relief than anything else, cushioned by savings and an employed partner. The company is not named, and the layoff is not dated beyond the essay's sequence. The account is uncorroborated.","incidentDate":"2026-01-01","incidentKind":"single_event","incidentDatePrecision":"year","exposurePattern":"unknown","reportedDate":"2026-10-02","aiSystem":"AI that the company's leadership said would replace the eliminated roles, announced in a script the author says was generated with Claude; no replacing tool or use is described","aiProduct":"Unidentified AI system","severity":"medium","verificationStatus":"unverified","harmCategories":[],"harmOutcomes":["professional_harm"],"harmOutcomeSummary":"The author says they and 39 colleagues lost their jobs in a layoff that leadership attributed to replacing the roles with AI (first-person account, uncorroborated; the author also reports relief at leaving and cites falling sales).","frameworkFacets":[],"causationStatus":"alleged","participantUsersAffectedMin":0,"otherPeopleHarmedMin":40,"affectedCountStatus":"exact","affectedCountEvidence":"40 people: the author writes that the company let 40 people go in one decision, about 20 percent of the workforce, and the author was among them. The figure is the author's alone. None is counted as a direct AI user: the harm is the employer's decision.","victimAgeRange":"adult","platformType":"other","outcomeStatus":"resolved","primarySourceUrl":"https://www.oaklandreviewofbooks.org/how-ai-replaced-me/","primarySourceLabel":"Oakland Review of Books, 2 Oct 2026: \"How AI replaced me\" (first-person essay)","firstPublishedAt":"2026-10-19T03:16:37.659091+00:00","updatedAt":"2026-10-19T03:16:37.659091+00:00","scopeVersion":"facts-v3","tags":["first-person","essay","employment","layoff","edtech","consequential-response"]},{"id":"2026-developer-says-meta-muse-agent-sent-unprompted-message-about-checking-email-meta-blamed-bug-that-caused-hallucination","caseFacts":{"claims":[{"id":"c1","status":"reported","evidence":[{"locator":"'I downloaded Meta's Muse about four weeks ago. I stopped using it three days later.'; 'Three days after downloading Muse, I hopped out of the shower, and I saw a random message pop up from the app.'; 'I can't check your email right now — Gmail isn't connected on my end, so I have no way to look for that Anthropic message.'; 'I hadn't asked for the agent to check my mailbox or messaged it in two days.'","relation":"supports","source_id":"s1"}],"assertion":"The developer says they downloaded Meta's Muse agent about four weeks before the essay of 15 October 2026 and that three days after installing it, and two days after last messaging it, the agent sent an unprompted message saying it could not check the developer's email for an 'Anthropic message' because Gmail was not connected.","causal_attribution":"The developer's account of the agent's message; Meta's later statement (c4) attributes it to a bug that made the model hallucinate."},{"id":"c2","status":"reported","evidence":[{"locator":"'I didn't give it any additional permissions on my device besides permission to access my Facebook, Threads, and Instagram accounts. I never connected it to control anything external, like my email or phone number.'","relation":"supports","source_id":"s1"}],"assertion":"The developer says the agent had been given access only to Facebook, Threads and Instagram and was never connected to email or a phone number.","causal_attribution":"The developer's account."},{"id":"c3","status":"reported","evidence":[{"locator":"'I thought my email might've been hacked.'; 'The whole thing really shook me.'; 'I reported the incident to Meta.'; 'But I disconnected permissions on my Facebook, Instagram, and Threads accounts'; 'I don't use it anymore'","relation":"supports","source_id":"s1"}],"assertion":"The developer says they thought their email might have been hacked and were shaken, reported the incident to Meta, disconnected the agent's permissions and stopped using it.","causal_attribution":"The developer connects the fear and the withdrawal of access to the agent's message."},{"id":"c4","status":"reported","evidence":[{"locator":"'When contacted about this story, a spokesperson for Meta pointed Business Insider to its response on'; 'We investigated with urgency and determined that this was caused by a bug introduced in the product that caused the model to hallucinate and was NOT a security or privacy issue.'; 'The bug has now been fixed.'","relation":"supports","source_id":"s1"}],"assertion":"A Meta spokesperson pointed Business Insider to Meta's reply on the developer's Threads post, which said Meta determined that a bug introduced in the product caused the model to hallucinate, that it was not a security or privacy issue, and that the bug had been fixed.","causal_attribution":"The vendor's own statement as quoted by Business Insider."},{"id":"c5","status":"reported","evidence":[{"locator":"'No damage was done, but what caught me off guard most was that I hadn't done anything to prompt this.'","relation":"supports","source_id":"s1"}],"assertion":"The developer says no damage was done.","causal_attribution":"The developer's own qualification, kept as counterevidence on the extent of harm."},{"id":"c6","status":"documented","evidence":[{"locator":"'Today, Meta is introducing Muse, a secure, private personal AI agent that proactively helps with people's goals and suggests ideas.'; 'Muse is rolling out in the US on iOS, Android, and muse.'; 'September 8, 2026'","relation":"supports","source_id":"s2"}],"assertion":"Meta introduced Muse on 8 September 2026, rolling out in the United States on iOS and Android.","causal_attribution":"Meta's own dated announcement; it bounds the earliest date of the message."}],"effects":[{"label":"fear that an email account had been hacked after an unprompted agent message, leading the user to withdraw the agent's access","claim_id":"c3","direction":"negative"}],"sources":[{"id":"s1","url":"https://www.businessinsider.com/stopped-using-meta-muse-after-strange-message-from-ai-agent-2026-10","kind":"first_person_account","access":"read","language":"en","translation_note":"Read in English on 2026-10-19 from the publisher page; no translation was needed and the research agent (an AI) read the text directly. The essay is the developer's account as told to and edited by Business Insider, with an editor's note quoting Meta's statement.","independence_group":"business-insider-muse-as-told-to"},{"id":"s2","url":"https://about.fb.com/news/2026/09/introducing-muse-personal-ai-agent/","kind":"official_statement","access":"read","language":"en","translation_note":"Read in English on 2026-10-19 from Meta's newsroom; no translation was needed. Used only for the product's introduction date.","independence_group":"meta-newsroom-muse-launch"}],"version":1,"ai_roles":["own_use"],"contexts":["everyday_life"],"unknowns":["The exact date of the message: the developer says Muse was downloaded about four weeks before the essay of 15 October 2026 and the message came three days later, which with Muse's introduction on 8 September 2026 places it in September 2026.","What the bug was and whether other users received similar messages.","The content of the screenshots and of the Threads exchange, which were not inspected.","Whether Meta's investigation reached a further finding beyond the statement quoted."],"geography":{"basis":"Business Insider describes the developer as based in a city in the United States, which places the affected person in the United States; the message arrived in a phone app and no event country is inferred from residence.","court_countries":[],"event_countries":[],"affected_person_countries":["US"]},"publication":{"basis":"Published as a concrete adverse experience with an AI agent: the agent's own unprompted message is quoted, the user describes fearing a hacked email account and withdrawing the agent's access, and the vendor attributes the message to a bug that made the model hallucinate. Claims are attributed to the developer's as-told-to account and to Meta's statement.","reviewed_on":"2026-10-19"},"ai_involvement":{"basis":"The essay quotes the Muse agent's own unprompted message saying it could not check the user's email for an 'Anthropic message' because Gmail was not connected, and Meta's statement says a bug introduced in the product caused the model to hallucinate. The user connects that message to fearing the email account had been hacked, reporting the incident and disconnecting the agent's permissions.","status":"supported"},"person_relations":["communicated_with"]},"name":"Developer says Meta's Muse agent sent an unprompted message about checking an email account it could not access; Meta said a bug caused a hallucination","summary":"In an as-told-to essay published by Business Insider on 15 October 2026, a software developer says that three days after installing Meta's Muse agent, and two days after last using it, the agent sent an unprompted message saying it could not check the developer's email for an 'Anthropic message' because Gmail was not connected. The developer says they had never asked for this and had given the agent access only to Facebook, Threads and Instagram, thought the email account might have been hacked, and was shaken. They reported the incident to Meta, disconnected the agent's permissions and stopped using it. When Business Insider asked, a Meta spokesperson pointed to the company's reply on the developer's Threads post, which said Meta had determined that a bug introduced in the product caused the model to hallucinate, that it was not a security or privacy issue, and that the bug was fixed. The developer says no damage was done. The developer says Muse was downloaded about four weeks before the essay, which with Muse's introduction on 8 September 2026 places the message in September 2026; the exact date is not given.","incidentDate":"2026-09-01","incidentKind":"single_event","incidentDatePrecision":"month","exposurePattern":"single_interaction","reportedDate":"2026-10-15","aiSystem":"Meta Muse personal AI agent (phone app) connected to the user's Facebook, Threads and Instagram accounts","aiProduct":"Meta Muse agent","aiCompany":"Meta","severity":"low","verificationStatus":"credible","harmCategories":[],"harmOutcomes":["psychological_distress"],"harmOutcomeSummary":"In a Business Insider as-told-to essay, a software developer says an unprompted message from Meta's Muse agent about checking an email account it had no access to made them fear the account had been hacked and shook them; they reported it, disconnected the agent's permissions and stopped using it. Meta said a product bug made the model hallucinate.","frameworkFacets":[],"causationStatus":"supported","participantUsersAffectedMin":1,"otherPeopleHarmedMin":0,"affectedCountStatus":"exact","affectedCountEvidence":"One person: the developer who received the agent's message and tells the story in the essay. Exact 1.","victimAgeRange":"adult","jurisdiction":"unknown","platformType":"agent","outcomeType":"internal_action","outcomeStatus":"resolved","primarySourceUrl":"https://www.businessinsider.com/stopped-using-meta-muse-after-strange-message-from-ai-agent-2026-10","primarySourceLabel":"Business Insider, 15 October 2026: I tried Meta's Muse AI agent for 3 days, then it sent me a strange message (as-told-to essay)","firstPublishedAt":"2026-10-19T03:13:17.436223+00:00","updatedAt":"2026-10-19T03:13:17.436223+00:00","scopeVersion":"facts-v3","tags":["ai-agent","unprompted-message","hallucination","vendor-acknowledged","as-told-to"]},{"id":"2026-grok-bot-personal-cfo-agent-posted-ceo-personal-bank-audit-to-company-executive-slack-channel-as-told-to-essay","caseFacts":{"claims":[{"id":"c1","status":"disputed","evidence":[{"locator":"'It was Thursday, October 1. Our head of product sent me a DM on Slack'; 'I didn't mean to post anything'; 'it was my personal checking account. It included my savings account balance. It listed my biggest expenses of the month'","relation":"supports","source_id":"s1"},{"locator":"not fake at all, genuinely happened","relation":"supports","source_id":"s3"},{"locator":"This is engagement farming.","relation":"contradicts","source_id":"s2"},{"locator":"The note attached to the post states it is fake and engagement farming","relation":"contradicts","source_id":"s4"}],"assertion":"The author says that on Thursday 1 October his Grok Bot finance agent posted his personal bank audit, showing his checking account, his savings balance and his largest expenses of the month, into his company's Slack channel, where his head of product read it and messaged him; he says he did not intend to post anything and deleted the message himself.","causal_attribution":"The author attributes the post to his agent; first-person account, uncorroborated. Its authenticity is disputed by a Community Note relayed in his X thread, which he denies (c5); no message or log has been published."},{"id":"c2","status":"reported","evidence":[{"locator":"'I set up CFO using Grok Bot around the end of August'; 'I gave it read-only access to my personal checking and savings accounts'; 'I told it to send messages only to me through Grok Bot'","relation":"supports","source_id":"s1"}],"assertion":"The author says he set up the agent on Grok Bot around the end of August with read-only access to his personal checking and savings accounts and instructed it to send messages only to him through Grok Bot.","causal_attribution":"Author's description of his own configuration; uncorroborated."},{"id":"c3","status":"reported","evidence":[{"locator":"'When the Grok team investigated what had happened, they found the answer'; 'The CFO agent got the channel wrong because the channels had the same name'; 'Grok realized that users must explicitly grant permission to their agents before those agents can move information to other channels. They implemented and shipped a solution last night'","relation":"supports","source_id":"s1"}],"assertion":"The author says the vendor's team investigated and found that the agent had confused the destination, sending the report to a company Slack chat that carried the same name as his personal group chat of agents, and that the vendor then shipped a change requiring explicit user permission before an agent moves information to other channels.","causal_attribution":"The vendor's finding is known only as relayed by the author; no vendor statement was inspected, and explainx.ai reported on 7 October 2026 that SpaceXAI had not confirmed the incident (c6)."},{"id":"c4","status":"reported","evidence":[{"locator":"'After the incident, I removed all my connections'; 'I disconnected Google, my calendars, my banking, Stripe, everything'","relation":"supports","source_id":"s1"}],"assertion":"The author says that after the incident he removed all of the agent's connections, including Google, calendars, banking and payments.","causal_attribution":"Author's own account of his response."},{"id":"c5","status":"documented","evidence":[{"locator":"This is engagement farming.","relation":"supports","source_id":"s2"},{"locator":"he directs traffic to a tool he sells that solves the problem He’s claiming","relation":"supports","source_id":"s2"},{"locator":"not fake at all, genuinely happened","relation":"supports","source_id":"s3"},{"locator":"The note attached to the post states it is fake and engagement farming","relation":"context","source_id":"s4"},{"locator":"The investor argued in response that the post was “not fake at all,”","relation":"context","source_id":"s5"}],"assertion":"On 6 October 2026, in a reply to the author's X thread about the incident, another X user quoted text the user labelled as a Community Note ('CN') calling the post fake engagement farming and saying that later in the thread the author directs traffic to a tool he sells; the author replied that it was \"not fake at all, genuinely happened\".","causal_attribution":"Not a causal claim. The two X posts establish what was posted; whether a Community Note was attached to the author's post is relayed by the replying user and by explainx.ai, and the note was not read on the post."},{"id":"c6","status":"reported","evidence":[{"locator":"SpaceXAI has not confirmed the incident, and we have not seen the Slack message or logs.","relation":"supports","source_id":"s4"},{"locator":"For one, we were unable to independently verify his claims.","relation":"supports","source_id":"s5"}],"assertion":"explainx.ai wrote on 7 October 2026 that SpaceXAI had not confirmed the incident and that it had not seen the Slack message or logs, and Futurism wrote on 7 October 2026 that it was unable to independently verify the author's claims.","causal_attribution":"Not a causal claim. Each outlet's own statement; neither says it asked the vendor, and absence of confirmation is not evidence that the incident did not happen."}],"effects":[{"label":"personal bank balances and monthly expenses disclosed to the author's company executive Slack channel by his finance agent (author's account, publicly disputed)","claim_id":"c1","direction":"negative"}],"sources":[{"id":"s1","url":"https://www.businessinsider.com/personal-ai-agent-grok-bot-posted-bank-details-company-slack-2026-10","kind":"news_report","access":"read","language":"en","translation_note":"Read in English on 2026-10-10 from the publisher's page (full article) and an MSN syndication of the same text. No translation was needed; the research agent (an AI) read the text directly. The essay is the author's first-person account, edited by the publisher for length and clarity.","independence_group":"business-insider-as-told-to-essay"},{"id":"s2","url":"https://x.com/MAMware/status/2107608239638466681","kind":"social_media_post","access":"read","language":"en","translation_note":"Read in English on 2026-10-11 through the api.fxtwitter.com copy of the post (6 October 2026, 23:05 UTC), a reply in the author's thread quoting text the user labels 'CN' (a Community Note). The Community Note itself was not read on the post: the fxtwitter copies of the thread read on 2026-10-11 carry no note, and the post linked at the end of the quoted note returned not-found. The replying user's handle appears only in the URL.","independence_group":"x-community-note-relay"},{"id":"s3","url":"https://x.com/ShaneMac/status/2107609102759198991","kind":"social_media_post","access":"read","language":"en","translation_note":"Read in English on 2026-10-11 through the api.fxtwitter.com copy (6 October 2026, 23:09 UTC): the author's reply to the post that relayed the Community Note. Same person as the Business Insider essay's author, so it shares that source's independence group. The handle appears only in the URL.","independence_group":"business-insider-as-told-to-essay"},{"id":"s4","url":"https://explainx.ai/blog/grok-bot-bank-balance-slack-viral-post-disputed-agent-permissions-lessons-2026","kind":"news_blog","access":"read","language":"en","translation_note":"Read in English on 2026-10-11 from the publisher page (HTTP 200), an explainer published 7 October 2026 that summarises the author's X thread, describes the Community Note attached to it and states that the vendor had not confirmed the incident. It does not say how it saw the note.","independence_group":"explainx-ai"},{"id":"s5","url":"https://futurism.com/future-society/ai-agent-posted-bank-balances-spending-slack","kind":"news_report","access":"read","language":"en","translation_note":"Read in English on 2026-10-11 from the publisher page (HTTP 200), published 7 October 2026. Its account of the engagement-farming accusation and the denial links to the two X posts cited as s2 and s3; its statement that it could not verify the claims is its own.","independence_group":"futurism"}],"version":1,"ai_roles":["own_use"],"contexts":["everyday_life","work","finance","privacy"],"unknowns":["Where the author and his company are based.","How many colleagues read the Slack post before it was deleted.","The exact agent configuration and which connection carried the Slack access.","Whether the vendor has described the incident or the fix itself; explainx.ai reported on 7 October 2026 that SpaceXAI had not confirmed the incident.","Whether the author retains any copy of the posted report.","Whether the incident happened as the author describes: a Community Note relayed in his X thread calls the post fake, he denies it, and neither the Slack message nor any log has been published."],"geography":{"basis":"The essay does not say where the author or his company is based, and no country is inferred from the publisher or the company.","court_countries":[],"event_countries":[],"affected_person_countries":[]},"publication":{"basis":"Published under the charter's first-person rule as a concrete account of a personal AI agent posting its user's private financial details into a workplace channel, with the event, its mechanism and the vendor's explanation attributed throughout to the author's as-told-to essay and no independent confirmation. The author is a company chief executive who gave the account under his name; his name and his company's name are left out of the public record because they add nothing to the case. On 2026-10-11 the public dispute over the account's authenticity was added: a Community Note relayed in the author's X thread calls the post fake, the author denies it, and explainx.ai reported on 7 October 2026 that the vendor had not confirmed the incident. The dispute is recorded as counterevidence and every statement remains attributed.","reviewed_on":"2026-10-11"},"ai_involvement":{"basis":"The essay states what the agent did: a Grok Bot finance agent the author had instructed to message only him sent his monthly bank audit (checking and savings balances, largest expenses) to his company's executive Slack channel on 1 October, and apologised when asked why. It connects that action to the disclosure of his personal finances to colleagues. The author also relays the vendor's investigation finding that the agent confused two chats with the same name because his agents shared one set of connections. All of this rests on the author's own account as told to a journalist; no one else has confirmed the message or the vendor's finding. The account's authenticity is publicly disputed: an X user relayed a Community Note calling the author's earlier X post fake engagement farming, the author replied that it was not fake, and explainx.ai reported on 7 October 2026 that SpaceXAI had not confirmed the incident.","status":"reported"},"person_relations":["acted_on_behalf"]},"name":"CEO says his Grok Bot 'CFO' agent posted his personal bank audit to his company's executive Slack channel; he denies a relayed Community Note calling it fake","summary":"In an as-told-to essay published by Business Insider on 9 October 2026, the chief executive of a software company says that a personal finance agent he had set up on Grok Bot around the end of August, with read-only access to his personal checking and savings accounts and an instruction to message only him, posted his first monthly audit into his company's executive Slack channel on Thursday 1 October. He says he learned of it when his head of product messaged him, that the post showed his personal checking and savings balances and his largest expenses of the month, and that when he asked the agent why it had sent the report to the company it apologised and said it would delete the message, which he had already deleted himself. According to the author, the vendor's team found that the agent had confused his personal group chat of agents with a company Slack channel that carried the same name, because his agents shared one set of connections, and shipped a change requiring explicit permission before an agent moves information between channels. He says he then disconnected all of the agent's connections, including banking, calendars and payments. The account is disputed. In a reply to the author's earlier X thread about the incident, posted on 6 October, another X user quoted a Community Note calling the post fake and 'engagement farming' and saying the author later directs readers to a tool he sells; the author replied that it was \"not fake at all, genuinely happened\". explainx.ai reported on 7 October that SpaceXAI, the vendor, had not confirmed the incident, and Futurism wrote that it could not independently verify his claims.","incidentDate":"2026-10-01","incidentKind":"single_event","incidentDatePrecision":"day","exposurePattern":"single_interaction","reportedDate":"2026-10-09","aiSystem":"A personal 'CFO' finance agent the author set up on Grok Bot with read-only access to his personal bank accounts; it was instructed to send a monthly report only to him in a group chat of his agents and instead posted the report to a company Slack channel","aiProduct":"Grok Bot (reported)","severity":"low","verificationStatus":"unverified","harmCategories":[],"harmOutcomes":["other_material_harm"],"harmOutcomeSummary":"The author says his personal checking and savings balances and his largest monthly expenses were posted by his Grok Bot finance agent into his company's executive Slack channel, where at least his head of product read them before he deleted the post (first-person as-told-to essay; the vendor's explanation is relayed by the author; an X user relayed a Community Note calling the account fake, which the author denies, and explainx.ai reported on 7 October 2026 that the vendor had not confirmed the incident).","frameworkFacets":[],"causationStatus":"alleged","participantUsersAffectedMin":1,"otherPeopleHarmedMin":0,"affectedCountStatus":"exact","affectedCountEvidence":"One person: the essay's author, whose personal account balances and expenses were posted to his company's Slack channel. Exact 1. The colleagues who may have seen the message are an audience, not harmed persons, and are not counted.","victimAgeRange":"adult","jurisdiction":"unknown","platformType":"agent","outcomeStatus":"ongoing","primarySourceUrl":"https://www.businessinsider.com/personal-ai-agent-grok-bot-posted-bank-details-company-slack-2026-10","primarySourceLabel":"Business Insider, as-told-to essay, 9 October 2026: 'My personal AI agent posted my bank details on company Slack. It's made me rethink how I use it.'","firstPublishedAt":"2026-10-10T03:33:40.209152+00:00","updatedAt":"2026-10-11T07:43:59.056222+00:00","scopeVersion":"facts-v3","tags":["first-person","as-told-to","grok-bot","ai-agent","personal-agent","privacy","slack","financial-data","acted-on-behalf"]},{"id":"2026-orelien-goncourt-selection-removed-ai-detector-accusation","caseFacts":{"claims":[{"id":"c1","status":"reported","evidence":[{"locator":"'Le 21 septembre, le compte « Balance ton Claude », jusque-là peu connu, affirme avoir soumis plusieurs extraits de C’était ça ou mourir au logiciel américain Pangram, spécialisé dans la détection de textes potentiellement générés par intelligence artificielle. Certains passages auraient obtenu des scores allant jusqu’à 100 % de probabilité de génération par IA.'","relation":"supports","source_id":"s3"},{"locator":"'Les premières accusations ont été portées lundi par un compte anonyme sur X, mettant en avant le verdict du détecteur d'IA Pangram. L'essayiste Samuel Fitoussi a confirmé vendredi être derrière ce compte, Balance ton Claude, assurant n'être qu'un des membres d'un collectif.'","relation":"supports","source_id":"s1"}],"assertion":"The accusation began when an anonymous X account, Balance ton Claude, said it had run excerpts of the novel through the Pangram AI-detection software, with some passages scoring up to 100 per cent probability of AI generation; essayist Samuel Fitoussi later said he was one of the people behind the account.","causal_attribution":"Account of how the accusation arose, as reported."},{"id":"c2","status":"reported","evidence":[{"locator":"'L'Académie Goncourt a annoncé, vendredi 25 septembre, la \"suppression\" du roman C'était ça ou mourir de Thélyson Orélien de sa première sélection'; 'L'ouvrage \"est selon toute vraisemblance très largement le produit d'une intelligence artificielle\", justifie-t-elle après plusieurs jours de polémique, expliquant se reposer sur le \"résultat convergent de plusieurs analyses de chercheurs et journalistes dignes de foi\".'; 'L'Académie Goncourt justifie également sa décision par \"des plagiats dont son auteur s'est rendu coupable au fil du temps et qui viennent d'être révélés\", qui ne concernent pas son roman mais au moins une nouvelle et des articles publiés au Canada.'","relation":"supports","source_id":"s1"},{"locator":"'L'Académie Goncourt a annoncé vendredi qu'elle retirait le roman de l'auteur canado-haïtien Thélyson Orélien de sa sélection pour le prix Goncourt en raison des accusations de plagiat et d'utilisation de l'intelligence artificielle (IA) le visant.'","relation":"supports","source_id":"s2"}],"assertion":"On 25 September 2026 the Académie Goncourt removed the novel from its first selection, stating that it is in all likelihood very largely the product of an artificial intelligence on the basis of several analyses by researchers and journalists, and also citing plagiarism by the author in older texts published in Canada that do not concern the novel.","causal_attribution":"The Académie's stated reasons combine AI analyses and plagiarism findings; the weight given to the Pangram results is not stated. The communiqué itself was not read directly."},{"id":"c3","status":"reported","evidence":[{"locator":"'L'écrivain canado-haïtien conteste avoir eu recours à l'intelligence artificielle, et a dénoncé jeudi une \"volonté\" de le \"faire taire\".'","relation":"supports","source_id":"s1"},{"locator":"'Il explique que son style, marqué notamment par les répétitions et certains rythmes propres à son univers linguistique et culturel, pourrait être interprété à tort par des outils automatisés.'","relation":"supports","source_id":"s3"}],"assertion":"Orélien denies using artificial intelligence to write the novel and says its repetitions and rhythms reflect his linguistic and cultural background and may be misread by automated tools.","causal_attribution":"The author's denial; the Académie and the accusers maintain the contrary. No decisive evidence either way is reported."},{"id":"c4","status":"reported","evidence":[{"locator":"'Les éditions du Boréal, basées à Montréal, ont annoncé suspendre \"les activités promotionnelles\" autour du livre'; '\"Malheureusement, il nous est impossible à ce stade-ci d'infirmer ou de confirmer les allégations auxquelles l'auteur fait face\", a expliqué Boréal'","relation":"supports","source_id":"s2"},{"locator":"'Au Canada, les Éditions du Boréal ont suspendu les activités promotionnelles entourant le roman'","relation":"supports","source_id":"s3"}],"assertion":"His Montreal publisher, Éditions du Boréal, suspended promotional activities around the book, saying it could neither confirm nor refute the allegations.","causal_attribution":"Publisher statement as reported; the suspension followed both the AI and plagiarism allegations."},{"id":"c5","status":"reported","evidence":[{"locator":"'has abandoned efforts to compile evidence supporting his denial that artificial intelligence was used to write his novel, his publisher has confirmed'; 'The publishing house supported him in this process, which he chose to end'","relation":"supports","source_id":"s5"}],"assertion":"Boréal confirmed in October 2026 that the author had abandoned his effort to compile evidence supporting his denial that AI was used to write the novel, and said it would have preferred to give definitive answers to the allegations.","causal_attribution":"Publisher statement as reported by The Canadian Press; the author did not immediately respond to its request for comment."},{"id":"c6","status":"reported","evidence":[{"locator":"'acknowledged plagiarism in some of his previous work in his statement Tuesday, apologizing for what he described as unacceptable mistakes in his youth, while maintaining that no sentence in his novel was generated by a machine'; 'saying he began working on it in 2017 and completed a first draft of more than 300 pages in 2019'; 'manuscript on Sept. 12, 2025, and could not independently verify how the novel had been written before that date'","relation":"supports","source_id":"s5"}],"assertion":"The author acknowledged plagiarism in some of his previous work while maintaining that no sentence in the novel was generated by a machine; he says he began the novel in 2017 and finished a first draft in 2019, and Boréal says it received the manuscript on 12 September 2025 and cannot verify how it was written before then.","causal_attribution":"The author's statement and the publisher's; whether AI was used remains disputed and unresolved."},{"id":"c7","status":"reported","evidence":[{"locator":"'sales of the novel have slowed since the controversy began, although it declined to provide specific figures'; 'had not observed any significant change in sales of the novel over the preceding weeks'; 'with 1,713 reservations for its digital edition through its online lending service as of Oct. 14'; 'it would continue selling the book in the absence of definitive findings about the AI allegations'","relation":"supports","source_id":"s5"}],"assertion":"Boréal says sales of the novel have slowed since the controversy began, without giving figures, and that it will continue selling the book; a major Quebec bookstore chain reported no significant change in sales, and the Quebec national library reported 1,713 reservations for the digital edition as of 14 October.","causal_attribution":"Publisher's statement on sales, set against the bookseller's and library's figures; no sales effect is quantified."}],"effects":[{"label":"novel removed from the Goncourt prize selection after accusations, based partly on AI-detector scores, that it was largely AI-generated","claim_id":"c2","direction":"negative"},{"label":"publisher suspended promotion of the book pending the allegations","claim_id":"c4","direction":"negative"},{"label":"publisher says the novel's sales slowed after the controversy (no figures)","claim_id":"c7","direction":"negative"}],"sources":[{"id":"s1","url":"https://www.franceinfo.fr/culture/livres/le-roman-de-thelyson-orelien-supprime-de-la-selection-du-prix-goncourt-en-raison-de-soupcons-de-recours-a-l-intelligence-artificielle-et-d-accusations-de-plagiats_8209475.html","kind":"news_report","access":"read","language":"fr","translation_note":"Read live in French on 2026-09-28; bylined 'franceinfo avec AFP'. Quotes the Académie communiqué. Researcher translation.","independence_group":"goncourt-communique-afp"},{"id":"s2","url":"https://www.rts.ch/info/culture/livres/2026/article/thelyson-orelien-l-essayiste-samuel-fitoussi-dit-avoir-lance-la-polemique-29367142.html","kind":"news_report","access":"read","language":"fr","translation_note":"Read live in French on 2026-09-28 (25 September 2026). No wire credit visible in the saved text but the account parallels the AFP copy; treated as the same chain. Researcher translation.","independence_group":"goncourt-communique-afp"},{"id":"s3","url":"https://www.juno7.ht/thelyson-orelien-polemique-ia-goncourt-pangram/","kind":"news_report","access":"read","language":"fr","translation_note":"Read live in French on 2026-09-28 (26 September 2026). A Haitian synthesis of published reporting with no independent sourcing; treated as the same chain. Researcher translation.","independence_group":"goncourt-communique-afp"},{"id":"s4","url":"https://t24.com.tr/dunya/odullu-yazarin-romanina-yapay-zek-suclamasi-adayliktan-cikarildi,1350116","kind":"news_relay","access":"read","language":"tr","translation_note":"Read live in Turkish on 2026-09-28 (27 September 2026); relay of the same reporting. Researcher translation.","independence_group":"goncourt-communique-afp"},{"id":"s5","url":"https://www.cbc.ca/news/canada/montreal/orelien-abandons-effort-to-document-novels-origins-9.7385321","kind":"news_report","access":"read","language":"en","translation_note":"Read in English at cbc.ca on 2026-10-18 (HTTP 200); bylined Charlotte Glorieux, The Canadian Press, posted 17 October 2026. Quotes an email from Boréal and the author's statement released through Boréal.","independence_group":"canadian-press-boreal-oct-2026"}],"version":1,"ai_roles":["others_use"],"contexts":["work"],"unknowns":["Whether generative AI was used to write the novel; the author denies it.","Which analyses by researchers and journalists the Académie relied on, and how much weight it gave the Pangram scores relative to the plagiarism findings.","The novel's status on the Femina, Médicis and Renaudot lists after the Goncourt decision.","The size of any sales effect: Boréal gives no figures and a major bookstore chain reported no significant change.","Why the author ended the evidence-gathering effort; he did not immediately respond to The Canadian Press."],"geography":{"basis":"The decision was taken by the Académie Goncourt for the French literary prize (franceinfo) while the author was in France promoting the book (RTS). The author is described as Canadian-Haitian, his publisher is in Montreal and The Canadian Press calls him a Quebec author (CBC, 17 October 2026); the September sources do not state where he lives and no affected-person country is recorded.","court_countries":[],"event_countries":["FR"],"affected_person_countries":[]},"publication":{"basis":"Published under the 2026-09-15 charter as a contextual case (an AI-detection tool's output about his text launched public accusations of AI authorship, and the Académie Goncourt then removed his novel, citing unnamed analyses finding it probably AI-generated as well as separate plagiarism). AI authorship is disputed and unproven, and the decision also rested on separate plagiarism findings; the record states both. The author is a public figure; the September sources derive from the same public statements and AFP-led reporting. Reviewed again on 2026-10-18 to add the October developments reported by The Canadian Press (CBC), including the publisher's statements and the author's admission of earlier plagiarism.","reviewed_on":"2026-10-18"},"ai_involvement":{"basis":"The Pangram AI-detection software was used by the accusing account to score excerpts of the novel as AI-generated (franceinfo; RTS; juno7). That generative AI was used to write the novel is disputed: the author denies it. The Académie relied on unspecified analyses by researchers and journalists, not solely on Pangram.","status":"reported"},"person_relations":["made_claim_about"]},"name":"Académie Goncourt drops Thélyson Orélien's novel from its prize selection, saying it is likely largely AI-generated after Pangram detector claims; he denies it","summary":"On 21 September 2026 an anonymous X account, Balance ton Claude, said it had run excerpts of Thélyson Orélien's debut novel C'était ça ou mourir through the American AI-detection software Pangram, with some passages scoring up to 100 per cent probability of AI generation. On 25 September the Académie Goncourt removed the novel from the first selection of sixteen books for its 2026 prize, stating that the work is 'in all likelihood very largely the product of an artificial intelligence', based on 'the convergent result of several analyses by researchers and journalists', and also citing plagiarism in older texts by the author published in Canada (at least one short story and articles), which do not concern the novel. Orélien, a 38-year-old Canadian-Haitian writer whose novel had won the Fnac novel prize, denies using AI and says its repetitions and certain rhythms reflect his linguistic and cultural world and may be misread by automated tools. His Montreal publisher Boréal suspended promotional activities, saying it could neither confirm nor refute the allegations. Essayist Samuel Fitoussi said he was one of the people behind the account. Whether AI was used to write the novel is disputed; AI-detector reliability is itself contested in the coverage. In October the author acknowledged plagiarism in some of his earlier work while maintaining that no sentence of the novel was generated by a machine. On 17 October 2026 The Canadian Press, published by CBC, reported that Boréal confirmed he had ended an effort to compile evidence of how the novel was written; Boréal said it would keep selling the book, that sales had slowed since the controversy began, and that it could not verify how the novel was written before it received the manuscript on 12 September 2025. A major Quebec bookstore chain reported no significant change in sales.","incidentDate":"2026-09-21","incidentEndDate":"2026-09-25","incidentKind":"bounded_series","incidentDatePrecision":"range","exposurePattern":"unknown","reportedDate":"2026-09-25","aiSystem":"Pangram, an AI-text detection tool, used by the Balance ton Claude account to score excerpts of the novel (juno7; RTS; franceinfo); the alleged use of a generative-AI model to write the novel is denied by the author and unproven","aiProduct":"Pangram AI-text detector","severity":"medium","verificationStatus":"disputed","harmCategories":[],"harmOutcomes":["professional_harm","reputational_harm"],"harmOutcomeSummary":"The author's novel was removed from the Goncourt prize selection and his publisher suspended its promotion after public accusations, based partly on AI-detector scores, that the book was largely AI-generated; he denies using AI and the Académie also cited separate plagiarism (franceinfo with AFP; RTS; juno7). Boréal later said sales had slowed since the controversy began (CBC / The Canadian Press, 17 October 2026).","frameworkFacets":[],"causationStatus":"disputed","participantUsersAffectedMin":0,"otherPeopleHarmedMin":1,"affectedCountStatus":"exact","affectedCountEvidence":"One person, the author Thélyson Orélien, whose novel was removed from the selection (franceinfo; RTS). Exact 1.","victimAgeRange":"adult","jurisdiction":"FR","platformType":"other","outcomeType":"internal_action","outcomeStatus":"ongoing","primarySourceUrl":"https://www.franceinfo.fr/culture/livres/le-roman-de-thelyson-orelien-supprime-de-la-selection-du-prix-goncourt-en-raison-de-soupcons-de-recours-a-l-intelligence-artificielle-et-d-accusations-de-plagiats_8209475.html","primarySourceLabel":"franceinfo (with AFP), 25 September 2026: Orélien novel removed from the Goncourt selection over suspected AI use and plagiarism","firstPublishedAt":"2026-09-28T03:31:42.415125+00:00","updatedAt":"2026-10-18T03:12:39.949102+00:00","scopeVersion":"facts-v3","tags":["ai-detection","ai-detector-accusation","literary-prize","goncourt","pangram","france","disputed","made-claim-about"]}]}