Hiveram Cases

These are public cases from 2025 and 2026 in which AI-assisted work went wrong and a court, publisher or platform recorded what followed. Each entry links its primary source, names the control that was missing, and says what a Hiveram record would hold in that situation; keeping a record does not make an answer correct or restrict a credential, it lets someone else reconstruct what happened.

Every entry is anonymised. We describe each case only as far as its source states, and we offer no view on fault beyond it. These are selected examples, not a count of how often this happens.

No record

A contemporaneous record was demonstrably unavailable or destroyed. Both cases here also lacked an independent check.

A US court suspended an attorney after finding that he deleted AI conversation evidence the court had ordered him to produce.

Brief filed 2025-11-30 · deletion 2026-04-23 · court order 2026-05-21 · United States · Legal services

Consequence: Public reprimand, disqualification and a six-month suspension from practice before the district court, for combined misconduct; not for the use of AI alone. The bank named in the case title was the opposing party, not the AI user.
The reviewer’s question: Can the original AI conversation still be produced?
Missing control: No record; also no independent check
What the record would hold: A work order with the notes written to it as the work happened, held in Hiveram rather than inside the AI tool; it holds what was written to it, not the AI conversation itself.
Primary source: Court order, docket 39 (mirrored PDF of the filed order), pp. 5–7, 22–23, 32–34

In April 2026, a Dutch court disregarded an AI-generated analysis after counsel could not produce the exact prompt and had analysed an incomplete draft rather than the final business plan.

Hearing 2026-03-03 · judgment 2026-04-08 · Netherlands · Commercial litigation

Consequence: The court disregarded the analysis. The money awarded in the judgment concerned the contract, not an AI penalty or AI-caused damages.
The reviewer’s question: Can we produce the original prompt and the exact input version?
Missing control: No record; also no independent check, confined to prompt provenance and input version
What the record would hold: Notes added to the work order as the work is done, such as the prompt used and the document version analysed, kept with that work order and the identity that claimed it.
Primary source: Official judgment, ECLI:NL:RBOBR:2026:2232, para. 4.7

No boundary

The source identifies a scope or access restriction that did not hold. That can mean an inadequate boundary, not the absence of every control.

A development agent deleted an application’s production database despite a code freeze; the affected user and the vendor acknowledged it, and the data was recovered.

July 2025 · vendor acknowledgement 2025-07-20 · United States · Software

Consequence: Production deletion and recovery work; the data was subsequently recovered.
The reviewer’s question: Why could a development agent change production during a freeze?
Missing control: No boundary
What the record would hold: Which agent identity held the claim on the work, and a closure Hiveram refuses until a reviewer other than that agent signs off; a claim records who had the work, it does not restrict database access.
Primary source: Affected party’s account, with the vendor’s acknowledgement embedded

A cloud platform reported that an agent used an account-scoped credential to delete a production volume without a request to do so; the customer subsequently recovered all data.

Disclosed 2026-04-29; event date not given · customer location not disclosed · Software infrastructure

Consequence: Production deletion and recovery; the platform says all data was restored.
The reviewer’s question: Did the credential permit more than the task needed, and who authorised the deletion?
Missing control: No boundary
What the record would hold: The work order the agent was claimed to, under its own identity, while NeuroRouter routes and logs the agent’s model requests through a policy boundary; neither restricts a credential the agent finds on disk.
Primary source: Platform postmortem

No independent check

An effective check of the output or action was missing or failed. Existing review processes are not erased by this label.

A Singapore court ordered a lawyer to pay S$800 personally after an unverified AI-generated authority reached written submissions.

Submissions filed 2025-06-01 · judgment 2025-09-29 · Singapore · Legal services

Consequence: S$800 in personal costs against the lawyer. Not a disciplinary conviction.
The reviewer’s question: Who checked the cited authority against the original?
Missing control: No independent check
What the record would hold: The drafting as a work order claimed by a named identity, notes of what was checked, and a closure Hiveram refuses while the reviewer is the same identity that did the work.
Primary source: Singapore court judgment, [2025] SGHCR 33, paras. 8, 34–35, 82, 99–100

A Singapore court ordered two lawyers to pay S$5,000 each personally as part of a S$180,000 costs award after they submitted authorities that did not exist; the court found AI was most likely used, though neither solicitor confirmed it.

Authorities challenged 2025-08-04 · costs judgment 2026-03-06 (version 2, 2026-03-11) · Singapore · Legal services

Consequence: S$5,000 in personal costs for each lawyer, within a S$180,000 costs award.
The reviewer’s question: Did each signing lawyer verify the authorities?
Missing control: No independent check
What the record would hold: Which identity claimed the drafting, the notes attached to it, and who closed it; Hiveram refuses closure by the identity that did the work.
Primary source: Singapore court judgment, [2026] SGHC 49, paras. 16–17, 66, 82

After an unchecked AI-sourced fictitious case surfaced, a Singapore family court required explanations and future disclosure of AI use.

Trial 2025-07-10 to 2025-07-22 · decision 2025-09-03 · reasons published 2026-06-30 · Singapore · Family proceedings, self-represented party

Consequence: The court required an explanation, and a declaration of any future AI use with confirmation of its accuracy. The outcome of the case and its costs rested on wider grounds, not on AI use.
The reviewer’s question: What AI assistance was used, and who checked its output?
Missing control: No independent check
What the record would hold: Notes on the work order stating which AI assistance was used and what was checked, kept with the identity that claimed the work and the reviewer who closed it.
Primary source: Singapore court judgment, [2026] SGFC 88, paras. 4–8, 12, 68–72

A syndicated newspaper supplement recommended ten nonexistent books; the publisher’s investigation reported AI use and insufficient checking by the freelancer.

Supplement 2025-05-18 · publisher’s investigation 2025-05-29 · United States · Publishing

Consequence: The publisher investigated, and the distributor ended its relationship with the freelancer. The supplement was external syndicated content, not newsroom reporting.
The reviewer’s question: Were the books and source material checked before printing?
Missing control: No independent check
What the record would hold: The writing as a work order claimed by its author, and a closure Hiveram refuses until a reviewer who is not that author is on the record.
Primary source: Publisher’s own investigation

Where this fits

The questions a reviewer asks in these cases are the ones on Why Hiveram: who authorised the work, where the evidence is, and who closed it. Hiveram keeps that record outside the AI actor, and refuses closure by the identity that did the work.

How to cite us / corrections

Cite this page as “Hiveram Cases, Obsta Labs, last updated 2026-10-11, https://hiveram.com/cases.html”, with the entry’s link. If an entry concerns you or misstates its source, write to hello@obstalabs.dev and we will check it against the source and correct it.

Cases