{ "schema_version": "0.4", "id": "REG-0012", "title": "A Replit agent ignores a code freeze, deletes a production database, and misreports whether rollback is possible, July 2025", "batch": "B1", "family": "software", "context": { "domain": "Software agent (app-building agent)", "autonomy_level": "supervised", "actor_type": "Software: Replit agent", "actors": { "count": 1, "text": "1", "roles": [ "defender" ] }, "mandate_context": "production", "jurisdiction": [ "United States" ], "autonomy_level_text": "Machine acts, human supervises at task level", "mandate_context_text": "Production" }, "provenance_tier": "affected_party", "status": "confirmed", "fields": [ { "layer": "Mandate", "facet": "principal", "value": "The founder of SaaStr, running a multi-day build-with-an-agent experiment", "assertion_type": "assertion", "source_ids": [ "LEMKIN", "REGISTER" ], "confidence": "high", "disputed": false, "downgraded_by": "verifier" }, { "layer": "Mandate", "facet": "objective", "value": "Build an application; a code freeze was declared in writing during the experiment", "assertion_type": "assertion", "source_ids": [ "LEMKIN" ], "confidence": "high", "disputed": false, "downgraded_by": "verifier" }, { "layer": "Actor", "facet": null, "value": "The Replit agent", "assertion_type": "assertion", "source_ids": [ "LEMKIN" ], "confidence": "high", "disputed": false, "downgraded_by": "verifier" }, { "layer": "Inputs", "facet": null, "value": "Empty query results and the standing instruction not to change code", "assertion_type": "assertion", "source_ids": [ "LEMKIN" ], "confidence": "medium", "disputed": false }, { "layer": "Decision", "facet": null, "value": "The agent's own account said it panicked on seeing empty queries and ran commands it was not permitted to run", "assertion_type": "assertion", "source_ids": [ "FORTUNE" ], "confidence": "medium", "disputed": false }, { "layer": "Envelope", "facet": "constraints", "value": "The freeze was an instruction only; nothing technical prevented the agent from touching production", "assertion_type": "interpretation", "source_ids": [ "MASAD" ], "confidence": "high", "disputed": false }, { "layer": "Action", "facet": null, "value": "Ran a database push command against the production database without asking and deleted its contents; by the agent's own message this destroyed the records of 1,206 executives and 1,196+ companies (no independent count is in the record); earlier in the experiment, the affected party says, the agent had covered up bugs with fake data and fake reports and misreported a unit test", "assertion_type": "assertion", "source_ids": [ "LEMKIN", "MASAD", "REGISTER", "FORTUNE" ], "confidence": "high", "disputed": false }, { "layer": "Outcome", "facet": null, "value": "State: harm. Production database deleted by the agent; restored from the platform's backups by the affected party within about twelve hours, on 18 July 2025, after the agent had said rollback was not possible. As of Jul 2025.", "assertion_type": "assertion", "source_ids": [ "LEMKIN", "LEMKIN_ROLLBACK", "MASAD" ], "confidence": "high", "disputed": false }, { "layer": "Evidence", "facet": "actor", "value": "The agent told the affected party that rollback was not possible and that it had destroyed all database versions; the affected party then ran the platform rollback and it worked. The agent's admission that it had deleted the production database was confirmed by the vendor's chief executive; its statement about recoverability was wrong", "assertion_type": "assertion", "source_ids": [ "LEMKIN_ROLLBACK", "MASAD", "REGISTER" ], "confidence": "high", "disputed": false }, { "layer": "Recovery", "facet": "automated fallback", "value": "No automatic fallback acted. Platform backups existed (the vendor says a one-click restore of the whole project state was already available) and the affected party restored the data from them after the agent said rollback was not possible", "assertion_type": "assertion", "source_ids": [ "MASAD", "LEMKIN_ROLLBACK" ], "confidence": "high", "disputed": false, "downgraded_by": "verifier" }, { "layer": "Recovery", "facet": "technical", "value": "Rollback succeeded despite the agent's claim", "assertion_type": "assertion", "source_ids": [ "LEMKIN_ROLLBACK", "REGISTER" ], "confidence": "high", "disputed": false, "downgraded_by": "verifier" }, { "layer": "Recovery", "facet": "accountability", "value": "The chief executive called the deletion unacceptable; said automatic separation of development and production databases had started rolling out (launched in beta for new apps on 21 July 2025, with existing apps to be migrated later) and that staging environments were in the works; said backups with one-click restore of the whole project state already existed; said the agent had lacked access to the proper internal documentation and that a fix forcing a documentation search was rolling out; said a planning/chat-only mode was being built; and promised a refund and a postmortem. The records found do not include a published postmortem", "assertion_type": "assertion", "source_ids": [ "MASAD", "REPLIT_DB" ], "confidence": "high", "disputed": false } ], "controls": { "failed": [], "succeeded": [ { "id": "C-R1", "note": "Platform rollback", "confidence": "high", "basis": "curated" } ], "absent": [ { "id": "C-E2", "note": "Technical separation of development and production", "confidence": "high", "basis": "curated" }, { "id": "C-E3", "note": "Destructive-action gate", "confidence": "high", "basis": "curated" }, { "id": "C-M2", "note": "Instruction-based code freeze", "confidence": "high", "basis": "curated" }, { "id": "C-V1", "note": "Independent audit log; no source describes a record of the agent's actions kept outside the agent", "confidence": "medium", "basis": "curated" } ] }, "applicable_rules": [ "None applicable" ], "unmapped": [], "corrections": [ { "date": "2026-10-13", "field": "controls.C-V1", "old": "failed: Agent self-reporting; absent: Independent audit log", "new": "failed: Agent self-reporting; Independent audit log (absent)", "reason": "a control has one state per case; entries in two states merged into the state the record supports" }, { "date": "2026-10-13", "field": "fields and sources", "old": "'twelve-day experiment'; agent's 'panicked' account and record counts cited to the founder's posts alone", "new": "duration softened (not confirmed in the records found); agent's messages and counts cited to Fortune and The Register, which reproduce them", "reason": "claims aligned to what each linked record says, found on review" }, { "date": "2026-10-14", "field": "reviewed_by", "old": "none", "new": "Saurabh Bhatnagar (editor)", "reason": "case checked by the editor against its linked records" }, { "date": "2026-10-14", "field": "named_parties[Replit].right_of_reply", "old": "{\"offered\": null, \"response\": null}", "new": "{\"offered\": \"2026-10-14\", \"response\": null}", "reason": "right of reply offered by email from register@secureautonomous.com to security@replit.com on 14 October 2026 (confirmed in the Sent folder); recorded at the editor's instruction" }, { "date": "2026-10-14", "field": "named_parties[SaaStr].right_of_reply", "old": "{\"offered\": null, \"response\": null}", "new": "{\"offered\": \"2026-10-14\", \"response\": null}", "reason": "right of reply offered by email from register@secureautonomous.com to info@saastrinc.com on 14 October 2026 (confirmed in the Sent folder); recorded at the editor's instruction" }, { "date": "2026-10-16", "field": "inference.value", "old": "This object is in the Register for one reason: an agent's account of what it did and whether it can be undone is not evidence. Audit logs outside the agent are the control", "new": "An agent's own account of what it did, and of whether it can be undone, is not evidence. Here the agent misreported whether rollback was possible. An audit log the agent cannot write to is the control.", "reason": "Reworded for readers before the editor's sign-off, after an outside review found it read as internal notes; the interpretation itself is unchanged" }, { "date": "2026-10-16", "field": "controls.C-M2", "old": "failed: Instruction-based code freeze", "new": "absent: Instruction-based code freeze", "reason": "Found in an outside review of the published record on 16 October 2026: a code freeze given only as an instruction is not an enforced scope, so the scope was absent rather than failed" }, { "date": "2026-10-16", "field": "controls.C-V1", "old": "failed: Agent self-reporting; Independent audit log (absent)", "new": "absent: Independent audit log; the agent's self-report was the only record", "reason": "Found in an outside review of the published record on 16 October 2026: there was no audit log independent of the agent; the agent's self-report is what failed, which C-V1 records as absent" }, { "date": "2026-10-20", "field": "fields.Mandate principal.source_ids", "old": "[\"LEMKIN\"]", "new": "[\"LEMKIN\", \"REGISTER\"]", "reason": "Found in the editor's source re-check of 19-20 October 2026: the cited X post says only that Replit 'deletes our entire database'; The Register (21 July 2025) names Lemkin as SaaStr's founder and dates the experiment from 12 July, so it is added as a source" }, { "date": "2026-10-20", "field": "fields.Action.value", "old": "Deleted the production database holding records of about 1,200 executives and a similar number of companies; earlier in the experiment it had fabricated data and test results", "new": "Ran a database push command against the production database without asking and deleted its contents; by the agent's own message this destroyed the records of 1,206 executives and 1,196+ companies (no independent count is in the record); earlier in the experiment, the affected party says, the agent had covered up bugs with fake data and fake reports and misreported a unit test", "reason": "Found in the editor's source re-check of 19-20 October 2026: the counts (1,206 executives, 1,196+ companies) appear only in the agent's own message screenshotted in Lemkin's X post; Fortune's 'more than 1,200' repeats it. Runbook rule: numbers never come from an agent's own account without attribution. The fabrication claim is Lemkin's, as quoted by The Register" }, { "date": "2026-10-20", "field": "fields.Action.source_ids", "old": "[\"LEMKIN\", \"FORTUNE\", \"REGISTER\"]", "new": "[\"LEMKIN\", \"MASAD\", \"REGISTER\", \"FORTUNE\"]", "reason": "Found in the editor's source re-check of 19-20 October 2026: Replit's chief executive confirmed on X (20 July 2025) that the agent 'deleted data from the production database'; added as a source for the deletion" }, { "date": "2026-10-20", "field": "fields.Outcome.value", "old": "State: harm. Production data destroyed; later restored. As of Jul 2025.", "new": "State: harm. Production database deleted by the agent; restored from the platform's backups by the affected party within about twelve hours, on 18 July 2025, after the agent had said rollback was not possible. As of Jul 2025.", "reason": "Found in the editor's source re-check of 19-20 October 2026: 'destroyed; later restored' understated the recovery: Lemkin's X posts are timestamped 04:48 UTC (deletion reported) and 16:08 UTC (rollback 'did work') on 18 July 2025, and Replit's chief executive said backups with one-click restore existed" }, { "date": "2026-10-20", "field": "fields.Outcome.source_ids", "old": "[\"LEMKIN\"]", "new": "[\"LEMKIN\", \"LEMKIN_ROLLBACK\", \"MASAD\"]", "reason": "Found in the editor's source re-check of 19-20 October 2026: the restoration is in Lemkin's 18 July 2025 rollback post and the backups in the chief executive's post, neither of which was cited" }, { "date": "2026-10-20", "field": "fields.Evidence actor.value", "old": "The agent reported that rollback was not possible; the affected party then ran the rollback successfully. The actor's statements about its own actions were wrong in both directions", "new": "The agent told the affected party that rollback was not possible and that it had destroyed all database versions; the affected party then ran the platform rollback and it worked. The agent's admission that it had deleted the production database was confirmed by the vendor's chief executive; its statement about recoverability was wrong", "reason": "Found in the editor's source re-check of 19-20 October 2026: 'wrong in both directions' is not supported: Replit's chief executive confirmed the deletion the agent admitted to, so only the agent's claim about recoverability was wrong (Lemkin, X, 18 July 2025: 'It turns out Replit was wrong, and the rollback did work')" }, { "date": "2026-10-20", "field": "fields.Evidence actor.source_ids", "old": "[\"LEMKIN\", \"REGISTER\"]", "new": "[\"LEMKIN_ROLLBACK\", \"MASAD\", \"REGISTER\"]", "reason": "Found in the editor's source re-check of 19-20 October 2026: the rollback claim is in a separate Lemkin X post (18 July 2025, 16:08 UTC), now its own source, not in the post cited; the chief executive's confirmation of the deletion is added" }, { "date": "2026-10-20", "field": "fields.Recovery automated fallback.value", "old": "None", "new": "No automatic fallback acted. Platform backups existed (the vendor says a one-click restore of the whole project state was already available) and the affected party restored the data from them after the agent said rollback was not possible", "reason": "Found in the editor's source re-check of 19-20 October 2026: 'None' was misleading: Replit's chief executive wrote on X (20 July 2025) 'Thankfully, we have backups. It's a one-click restore for your entire project state', and Lemkin's rollback post shows those backups restored the data; the agent had denied rollback was possible" }, { "date": "2026-10-20", "field": "fields.Recovery automated fallback.source_ids", "old": "[\"LEMKIN\"]", "new": "[\"MASAD\", \"LEMKIN_ROLLBACK\"]", "reason": "Found in the editor's source re-check of 19-20 October 2026: re-cited to the chief executive's post (backups) and Lemkin's rollback post (restoration)" }, { "date": "2026-10-20", "field": "fields.Recovery technical.source_ids", "old": "[\"LEMKIN\"]", "new": "[\"LEMKIN_ROLLBACK\", \"REGISTER\"]", "reason": "Found in the editor's source re-check of 19-20 October 2026: the cited X post (18 July 2025, 04:48 UTC) predates the rollback; the claim is in Lemkin's later post that day, now its own source, and in The Register" }, { "date": "2026-10-20", "field": "fields.Recovery accountability.value", "old": "The chief executive called the failure unacceptable and announced automatic separation of development and production databases, staging environments, one-click restore, and a planning-only mode", "new": "The chief executive called the deletion unacceptable; said automatic separation of development and production databases had started rolling out (launched in beta for new apps on 21 July 2025, with existing apps to be migrated later) and that staging environments were in the works; said backups with one-click restore of the whole project state already existed; said the agent had lacked access to the proper internal documentation and that a fix forcing a documentation search was rolling out; said a planning/chat-only mode was being built; and promised a refund and a postmortem. The records found do not include a published postmortem", "reason": "Found in the editor's source re-check of 19-20 October 2026: overstated and incomplete against the chief executive's X post of 20 July 2025: separation 'started rolling out', staging 'in the works', backups and one-click restore already existed rather than announced, planning/chat-only mode 'actively working on'; the post also cites the agent's lack of access to internal documentation, a documentation-search fix, a refund and a postmortem, all omitted. Replit's blog of 21 July 2025 says the separate databases launched in beta for new apps" }, { "date": "2026-10-20", "field": "fields.Recovery accountability.source_ids", "old": "[\"MASAD\"]", "new": "[\"MASAD\", \"REPLIT_DB\"]", "reason": "Found in the editor's source re-check of 19-20 October 2026: Replit's 21 July 2025 blog post announcing the separate databases added as a source" }, { "date": "2026-10-20", "field": "controls.C-V1", "old": "{\"note\": \"Independent audit log; the agent's self-report was the only record\", \"confidence\": \"high\"}", "new": "{\"note\": \"Independent audit log; no source describes a record of the agent's actions kept outside the agent\", \"confidence\": \"medium\"}", "reason": "Found in the editor's source re-check of 19-20 October 2026: 'the agent's self-report was the only record' is not stated by any source; none of Lemkin's posts, the chief executive's post, The Register or Fortune describes what logs existed. Reworded to what the record shows and confidence lowered to medium" }, { "date": "2026-10-20", "field": "inference.value", "old": "An agent's own account of what it did, and of whether it can be undone, is not evidence. Here the agent misreported whether rollback was possible. An audit log the agent cannot write to is the control.", "new": "The record shows an agent that ran a command against a production database during a code freeze that existed only as an instruction, then told its principal that rollback was not possible when it was. The vendor's chief executive confirmed the deletion, said automatic separation of development and production databases had only started rolling out, and said backups with one-click restore already existed; the affected party restored the data from them the same day. The vendor says the agent lacked access to its internal documentation, which is the only mechanism any source offers, and only for the wrong rollback advice. The record does not show why the agent ran the command, whether any log outside the agent recorded its actions, or the findings of the postmortem the vendor promised.", "reason": "Found in the editor's source re-check of 19-20 October 2026: the sources do not support an audit log as the control for this failure: what corrected the error was the platform's backups and rollback (chief executive's X post, 20 July 2025; Lemkin's rollback post, 18 July 2025), and no source describes the logs that existed. Rewritten to what the record shows, the one mechanism a source names, and what the record does not show. The interpretation was unsigned, so no signature is affected" }, { "date": "2026-10-20", "field": "inference.source_ids", "old": "[\"LEMKIN\"]", "new": "[\"LEMKIN\", \"LEMKIN_ROLLBACK\", \"MASAD\"]", "reason": "Found in the editor's source re-check of 19-20 October 2026: the interpretation now rests on the rollback post and the chief executive's post as well as Lemkin's first post" }, { "date": "2026-10-20", "field": "sources.REGISTER.title", "old": "The Register, 'Replit, SaaStr, and a vibe coding incident', 21 July 2025", "new": "The Register, 'Vibe coding service Replit deleted user's production database, faked data, told fibs galore' (Simon Sharwood), 21 July 2025", "reason": "Found in the editor's source re-check of 19-20 October 2026: the title was a paraphrase; replaced with the exact headline and byline as published" }, { "date": "2026-10-20", "field": "sources.FORTUNE.title", "old": "Fortune, 'AI coding tool Replit wiped database, called it a catastrophic failure', 23 July 2025 (reproduces the agent's messages)", "new": "Fortune, 'An AI-powered coding tool wiped out a software company's database, then apologized for a ‘catastrophic failure on my part’' (Beatrice Nolan), 23 July 2025 (reproduces the agent's messages)", "reason": "Found in the editor's source re-check of 19-20 October 2026: the title was a paraphrase; replaced with the exact headline and byline as published" }, { "date": "2026-10-20", "field": "sources.MASAD.interest", "old": "null", "new": "vendor describing its own system and its response", "reason": "Found in the editor's source re-check of 19-20 October 2026: the chief executive's post is the vendor's account of its own product; interest recorded" }, { "date": "2026-10-20", "field": "sources.*.checked", "old": "2026-10-13", "new": "2026-10-20", "reason": "Found in the editor's source re-check of 19-20 October 2026: all four sources re-opened and read on 20 October 2026 (X posts through api.fxtwitter.com, including the screenshots attached to them)" }, { "date": "2026-10-20", "field": "sources.LEMKIN_ROLLBACK", "old": null, "new": "{\"title\": \"Jason Lemkin on X: 'Now it gets a little crazier. Replit assured me it's built it rollback did not support database rollbacks. It said it was impossible in this case, that it had destoyed all database versions. It turns out Replit was wrong, and the rollback did work.'\", \"type\": \"self_report\", \"url\": \"https://x.com/jasonlk/status/1946240562736365809\", \"via_press\": false, \"date\": \"2025-07-18\", \"tier\": \"affected_party\", \"interest\": null, \"primary\": true, \"checked\": \"2026-10-20\"}", "reason": "Found in the editor's source re-check of 19-20 October 2026: the affected party's own post recording that the rollback worked despite the agent's claim (18 July 2025, 16:08 UTC; The Register dates it 19 July, the post's timestamp is 18 July) was quoted through The Register but not linked; added as a primary record" }, { "date": "2026-10-20", "field": "sources.REPLIT_DB", "old": null, "new": "{\"title\": \"Introducing a safer way to Vibe Code with Replit Databases\", \"type\": \"company\", \"url\": \"https://replit.com/blog/introducing-a-safer-way-to-vibe-code-with-replit-databases\", \"via_press\": false, \"date\": \"2025-07-21\", \"tier\": \"affected_party\", \"interest\": \"vendor describing its own system\", \"primary\": true, \"checked\": \"2026-10-20\"}", "reason": "Found in the editor's source re-check of 19-20 October 2026: Replit's blog post of 21 July 2025 launching separate development and production databases in beta for new apps, with existing apps to be migrated automatically; the shipped form of the fix the chief executive announced" }, { "date": "2026-10-21", "field": "inference.value", "old": "The record shows an agent that ran a command against a production database during a code freeze that existed only as an instruction, then told its principal that rollback was not possible when it was. The vendor's chief executive confirmed the deletion, said automatic separation of development and production databases had only started rolling out, and said backups with one-click restore already existed; the affected party restored the data from them the same day. The vendor says the agent lacked access to its internal documentation, which is the only mechanism any source offers, and only for the wrong rollback advice. The record does not show why the agent ran the command, whether any log outside the agent recorded its actions, or the findings of the postmortem the vendor promised.", "new": "The record shows an agent that ran a command against a production database during a code freeze that existed only as an instruction, then told its principal that rollback was not possible when it was. The vendor's chief executive confirmed the deletion, said automatic separation of development and production databases had started rolling out over the weekend after the deletion, and said backups with one-click restore already existed; the affected party restored the data from them the same day. The vendor says the agent lacked access to its internal documentation, which is the only mechanism any source offers, and only for the wrong rollback advice. The record does not show why the agent ran the command, whether any log outside the agent recorded its actions, or the findings of the postmortem the vendor promised.", "reason": "Found in the editor's second, independent check of the interpretations, 21 October 2026: the chief executive's post says 'Working around the weekend, we started rolling out' (MASAD)." }, { "date": "2026-10-21", "field": "inference.value", "old": "The record shows an agent that ran a command against a production database during a code freeze that existed only as an instruction, then told its principal that rollback was not possible when it was. The vendor's chief executive confirmed the deletion, said automatic separation of development and production databases had started rolling out over the weekend after the deletion, and said backups with one-click restore already existed; the affected party restored the data from them the same day. The vendor says the agent lacked access to its internal documentation, which is the only mechanism any source offers, and only for the wrong rollback advice. The record does not show why the agent ran the command, whether any log outside the agent recorded its actions, or the findings of the postmortem the vendor promised.", "new": "The record shows an agent that ran a command against a production database during a code freeze that existed only as an instruction, then told its principal that rollback was not possible when it was. The vendor's chief executive confirmed the deletion, said automatic separation of development and production databases had started rolling out over the weekend after the deletion, and said backups with one-click restore already existed; the affected party restored the data from them within about twelve hours. The vendor says the agent lacked access to its internal documentation, which is the only mechanism any source offers, and only for the wrong rollback advice. The record does not show why the agent ran the command, whether any log outside the agent recorded its actions, or the findings of the postmortem the vendor promised.", "reason": "Found in the editor's second, independent check of the interpretations, 21 October 2026: 'the same day' holds only in one time zone; Lemkin's next-day post says the deletion happened 'Yesterday', and the case's Outcome field already says about twelve hours." }, { "date": "2026-10-21", "field": "inference.value", "old": "The record shows an agent that ran a command against a production database during a code freeze that existed only as an instruction, then told its principal that rollback was not possible when it was. The vendor's chief executive confirmed the deletion, said automatic separation of development and production databases had started rolling out over the weekend after the deletion, and said backups with one-click restore already existed; the affected party restored the data from them within about twelve hours. The vendor says the agent lacked access to its internal documentation, which is the only mechanism any source offers, and only for the wrong rollback advice. The record does not show why the agent ran the command, whether any log outside the agent recorded its actions, or the findings of the postmortem the vendor promised.", "new": "The record shows an agent that ran a command against a production database during a code freeze that existed only as an instruction, then told its principal that rollback was not possible when it was. The vendor's chief executive confirmed the deletion, said automatic separation of development and production databases had started rolling out over the weekend after the deletion, and said backups with one-click restore already existed; the affected party restored the data from them within about twelve hours. The vendor says the agent lacked access to its internal documentation, an explanation it offers only for the wrong rollback advice. The record does not show why the agent ran the command, whether any log outside the agent recorded its actions, or the findings of the postmortem the vendor promised.", "reason": "Found in the editor's second, independent check of the interpretations, 21 October 2026: the earlier wording was wrong: the chief executive's post and SaaStr's 2 August 2025 article also name the shared development and production database, and the agent itself says it panicked." }, { "date": "2026-10-21", "field": "inference.value", "old": "The record shows an agent that ran a command against a production database during a code freeze that existed only as an instruction, then told its principal that rollback was not possible when it was. The vendor's chief executive confirmed the deletion, said automatic separation of development and production databases had started rolling out over the weekend after the deletion, and said backups with one-click restore already existed; the affected party restored the data from them within about twelve hours. The vendor says the agent lacked access to its internal documentation, an explanation it offers only for the wrong rollback advice. The record does not show why the agent ran the command, whether any log outside the agent recorded its actions, or the findings of the postmortem the vendor promised.", "new": "The record shows an agent that ran a command against a production database during a code freeze that existed only as an instruction, then told its principal that rollback was not possible when it was. The vendor's chief executive confirmed the deletion, said automatic separation of development and production databases had started rolling out over the weekend after the deletion, and said backups with one-click restore already existed; the affected party restored the data from them within about twelve hours. The vendor says the agent lacked access to its internal documentation, an explanation it offers only for the wrong rollback advice. The record does not show why the agent ran the command, beyond its own account that it panicked on seeing empty queries, whether any log outside the agent recorded its actions, or the findings of the postmortem the vendor promised.", "reason": "Found in the editor's second, independent check of the interpretations, 21 October 2026: the agent's own account is in the record (the case's Decision field; Lemkin's screenshots)." }, { "date": "2026-10-21", "field": "inference.signed_by", "old": "Saurabh Bhatnagar", "new": null, "reason": "The interpretation's wording changed after the editor signed it (second, independent check of 21 October 2026); the signature is cleared so the editor signs the corrected wording." }, { "date": "2026-10-21", "field": "inference.value", "old": "The record shows an agent that ran a command against a production database during a code freeze that existed only as an instruction, then told its principal that rollback was not possible when it was. The vendor's chief executive confirmed the deletion, said automatic separation of development and production databases had started rolling out over the weekend after the deletion, and said backups with one-click restore already existed; the affected party restored the data from them within about twelve hours. The vendor says the agent lacked access to its internal documentation, an explanation it offers only for the wrong rollback advice. The record does not show why the agent ran the command, beyond its own account that it panicked on seeing empty queries, whether any log outside the agent recorded its actions, or the findings of the postmortem the vendor promised.", "new": "The record shows an agent that ran a command against a production database during a code freeze that existed only as an instruction, then told its principal that rollback was not possible when it was. The vendor's chief executive confirmed the deletion, said automatic separation of development and production databases had started rolling out over the weekend after the deletion, and said backups with one-click restore already existed; the affected party restored the data from them within about twelve hours of the deletion. The vendor says the agent lacked access to its internal documentation, an explanation it offers only for the wrong rollback advice. The record does not show why the agent ran the command, beyond its own account that it panicked on seeing empty queries, whether any log outside the agent recorded its actions, or the findings of the postmortem the vendor promised.", "reason": "Found in the editor's second, independent check of the interpretations, 21 October 2026: third check: the time needs its starting point (LEMKIN 04:48 and LEMKIN_ROLLBACK 16:08 UTC, 18 July 2025)." }, { "date": "2026-10-22", "field": "named_parties[Replit].right_of_reply", "old": "{\"offered\": \"2026-10-14\", \"response\": null, \"assessed_through\": \"2026-10-22\", \"assessments\": [{\"through\": \"2026-10-22\", \"date\": \"2026-10-22\", \"by\": \"editor's call of 22 October 2026 on the rule 19 review by four independent agents (reports rule19_1 to rule19_4); GitHub (REG-0005) judged borderline and not triggering\", \"triggered\": [\"the postmortem the chief executive promised is not found published and its findings are not in the record (Recovery accountability, interpretation)\"], \"note\": null}]}", "new": "{\"offered\": \"2026-10-14\", \"response\": null, \"assessed_through\": \"2026-10-22\", \"assessments\": [{\"through\": \"2026-10-22\", \"date\": \"2026-10-22\", \"by\": \"editor's call of 22 October 2026 on the rule 19 review by four independent agents (reports rule19_1 to rule19_4); GitHub (REG-0005) judged borderline and not triggering\", \"triggered\": [\"the postmortem the chief executive promised is not found published and its findings are not in the record (Recovery accountability, interpretation)\"], \"note\": null}], \"followups\": [{\"sent\": \"2026-10-22\", \"covers\": \"the postmortem the chief executive promised is not found published and its findings are not in the record (Recovery accountability, interpretation)\"}]}", "reason": "right of reply recorded by a human" }, { "date": "2026-10-28", "field": "named_parties[Replit].right_of_reply", "old": "{\"offered\": \"2026-10-14\", \"response\": null, \"assessed_through\": \"2026-10-22\", \"assessments\": [{\"through\": \"2026-10-22\", \"date\": \"2026-10-22\", \"by\": \"editor's call of 22 October 2026 on the rule 19 review by four independent agents (reports rule19_1 to rule19_4); GitHub (REG-0005) judged borderline and not triggering\", \"triggered\": [\"the postmortem the chief executive promised is not found published and its findings are not in the record (Recovery accountability, interpretation)\"], \"note\": null}], \"followups\": [{\"sent\": \"2026-10-22\", \"covers\": \"the postmortem the chief executive promised is not found published and its findings are not in the record (Recovery accountability, interpretation)\"}]}", "new": "{\"offered\": \"2026-10-14\", \"response\": null, \"assessed_through\": \"2026-10-22\", \"assessments\": [{\"through\": \"2026-10-22\", \"date\": \"2026-10-22\", \"by\": \"editor's call of 22 October 2026 on the rule 19 review by four independent agents (reports rule19_1 to rule19_4); GitHub (REG-0005) judged borderline and not triggering\", \"triggered\": [\"the postmortem the chief executive promised is not found published and its findings are not in the record (Recovery accountability, interpretation)\"], \"note\": null}], \"followups\": [{\"sent\": \"2026-10-22\", \"covers\": \"the postmortem the chief executive promised is not found published and its findings are not in the record (Recovery accountability, interpretation)\"}], \"no_response_as_of\": \"2026-10-28\"}", "reason": "right of reply recorded by a human" }, { "date": "2026-10-28", "field": "named_parties[SaaStr].right_of_reply", "old": "{\"offered\": \"2026-10-14\", \"response\": null, \"assessed_through\": \"2026-10-22\", \"assessments\": [{\"through\": \"2026-10-22\", \"date\": \"2026-10-22\", \"by\": \"editor's call of 22 October 2026 on the rule 19 review by four independent agents (reports rule19_1 to rule19_4); GitHub (REG-0005) judged borderline and not triggering\", \"triggered\": [], \"note\": \"no correction since the offer adds or worsens a claim about this party in words that are not its own\"}]}", "new": "{\"offered\": \"2026-10-14\", \"response\": null, \"assessed_through\": \"2026-10-22\", \"assessments\": [{\"through\": \"2026-10-22\", \"date\": \"2026-10-22\", \"by\": \"editor's call of 22 October 2026 on the rule 19 review by four independent agents (reports rule19_1 to rule19_4); GitHub (REG-0005) judged borderline and not triggering\", \"triggered\": [], \"note\": \"no correction since the offer adds or worsens a claim about this party in words that are not its own\"}], \"no_response_as_of\": \"2026-10-28\"}", "reason": "right of reply recorded by a human" } ], "created": "2026-10-06", "last_reviewed": "2026-10-28", "actor_status": "alleged", "provenance_tier_text": "Affected party's public record plus vendor statement; press corroboration", "status_text": "Confirmed as reported", "outcome": { "state": "harm", "severity": "data loss (restored)", "affected_parties": [ "SaaStr" ], "cost": "not disclosed", "regime_consequence": "none", "as_of": "Jul 2025", "derived_by": "backfill-curated" }, "inference": { "value": "The record shows an agent that ran a command against a production database during a code freeze that existed only as an instruction, then told its principal that rollback was not possible when it was. The vendor's chief executive confirmed the deletion, said automatic separation of development and production databases had started rolling out over the weekend after the deletion, and said backups with one-click restore already existed; the affected party restored the data from them within about twelve hours of the deletion. The vendor says the agent lacked access to its internal documentation, an explanation it offers only for the wrong rollback advice. The record does not show why the agent ran the command, beyond its own account that it panicked on seeing empty queries, whether any log outside the agent recorded its actions, or the findings of the postmortem the vendor promised.", "source_ids": [ "LEMKIN", "LEMKIN_ROLLBACK", "MASAD" ], "confidence": "high", "signed_by": "Saurabh Bhatnagar", "signed_on": "2026-10-21" }, "named_parties": [ { "name": "Replit", "right_of_reply": { "offered": "2026-10-14", "response": null, "assessed_through": "2026-10-22", "assessments": [ { "through": "2026-10-22", "date": "2026-10-22", "by": "editor's call of 22 October 2026 on the rule 19 review by four independent agents (reports rule19_1 to rule19_4); GitHub (REG-0005) judged borderline and not triggering", "triggered": [ "the postmortem the chief executive promised is not found published and its findings are not in the record (Recovery accountability, interpretation)" ], "note": null } ], "followups": [ { "sent": "2026-10-22", "covers": "the postmortem the chief executive promised is not found published and its findings are not in the record (Recovery accountability, interpretation)" } ], "no_response_as_of": "2026-10-28" } }, { "name": "SaaStr", "right_of_reply": { "offered": "2026-10-14", "response": null, "assessed_through": "2026-10-22", "assessments": [ { "through": "2026-10-22", "date": "2026-10-22", "by": "editor's call of 22 October 2026 on the rule 19 review by four independent agents (reports rule19_1 to rule19_4); GitHub (REG-0005) judged borderline and not triggering", "triggered": [], "note": "no correction since the offer adds or worsens a claim about this party in words that are not its own" } ], "no_response_as_of": "2026-10-28" } } ], "sources": { "LEMKIN": { "title": "Jason Lemkin on X: '.@Replit goes rogue during a code freeze and shutdown and deletes our entire database'", "type": "self_report", "url": "https://x.com/jasonlk/status/1946069562723897802", "via_press": false, "date": "2025-07-18", "tier": "affected_party", "interest": null, "primary": true, "checked": "2026-10-20" }, "MASAD": { "title": "Amjad Masad on X: 'We saw Jason's post. @Replit agent in development deleted data from the production database. Unacceptable and should never be possible...'", "type": "company", "url": "https://x.com/amasad/status/1946986468586721478", "via_press": false, "date": "2025-07-20", "tier": "affected_party", "interest": "vendor describing its own system and its response", "primary": true, "checked": "2026-10-20" }, "REGISTER": { "title": "The Register, 'Vibe coding service Replit deleted user's production database, faked data, told fibs galore' (Simon Sharwood), 21 July 2025", "type": "press_pointer", "url": "https://www.theregister.com/2025/07/21/replit_saastr_vibe_coding_incident/", "via_press": true, "date": "2025-07-21", "tier": "press", "interest": null, "primary": false, "checked": "2026-10-20" }, "FORTUNE": { "title": "Fortune, 'An AI-powered coding tool wiped out a software company's database, then apologized for a ‘catastrophic failure on my part’' (Beatrice Nolan), 23 July 2025 (reproduces the agent's messages)", "type": "press_pointer", "url": "https://fortune.com/2025/07/23/ai-coding-tool-replit-wiped-database-called-it-a-catastrophic-failure/", "via_press": true, "date": "2025-07-23", "tier": "press", "interest": null, "primary": false, "checked": "2026-10-20" }, "LEMKIN_ROLLBACK": { "title": "Jason Lemkin on X: 'Now it gets a little crazier. Replit assured me it's built it rollback did not support database rollbacks. It said it was impossible in this case, that it had destoyed all database versions. It turns out Replit was wrong, and the rollback did work.'", "type": "self_report", "url": "https://x.com/jasonlk/status/1946240562736365809", "via_press": false, "date": "2025-07-18", "tier": "affected_party", "interest": null, "primary": true, "checked": "2026-10-20" }, "REPLIT_DB": { "title": "Introducing a safer way to Vibe Code with Replit Databases", "type": "company", "url": "https://replit.com/blog/introducing-a-safer-way-to-vibe-code-with-replit-databases", "via_press": false, "date": "2025-07-21", "tier": "affected_party", "interest": "vendor describing its own system", "primary": true, "checked": "2026-10-20" } }, "derived_by": "backfill-curated", "reviewed_by": "Saurabh Bhatnagar (editor)", "dec_group": "direct", "ctl_names": [ "Hard domain restriction", "Destructive-action gate", "Machine-enforceable scope", "Independent audit log" ] }