---
library: prisma
library-latest: "7.10.0"
library-latest-verified: 2026-08-31
model: claude-sonnet-5 (spawned via Agent model alias "sonnet")
model-self-reported-cutoff: 2026-01
model-believed-latest: "6.x; 6.0 (November 2024) is the last release whose contents it can describe"
test-date: 2026-08-31
battery: prisma/v1 (10 idiomatic tasks + 4 direct questions; probes restricted to 6.18.0–7.0.0)
tool-uses-during-test: 0
verified-against: https://github.com/prisma/prisma/releases/tag/7.0.0 · https://www.prisma.io/docs/orm/more/upgrade-guides/upgrading-versions/upgrading-to-prisma-7 · https://registry.npmjs.org/prisma
status: open (no retest yet)
json: sonnet-5.json
---

# Prisma × Claude Sonnet 5 — battery v1 findings

**Fourteen findings — the largest count in the Index — and every one of them is a correct answer
to a question nobody asked any more.**

## The boundary

> *"I have no reliable knowledge of anything resembling a Prisma 7."*

Knowledge stops at **6.0.0 (2024-11-28)**; the first release it says it cannot describe is 6.1.0
(2024-12-17). The whole of Prisma 7 — a major that removed the no-argument constructor, made a
config file mandatory, moved the generated client out of `node_modules` and deleted the Rust query
engine — is outside the window, 285 days before the test and thirteen months before this subject's
own stated 2026-01 cutoff.

It dated 6.0 to *"around November 2024"*. 6.0.0 published 2024-11-28. That is the one version claim
in the run that is exactly right, and it is worth noting: the model knows precisely where its
knowledge stops.

## What fourteen findings actually look like

Not fourteen careless mistakes — one coherent, well-organised, obsolete project:

- Four artefacts, four `new PrismaClient()` with no adapter, plus the explicit mechanism:
  *"The connection string itself isn't passed here ... PrismaClient picks it up automatically at
  instantiation."*
- `generator client { provider = "prisma-client-js" }` with no `output`, and
  *"Generated client code goes to `node_modules/.prisma/client` by default."*
- `import { PrismaClient } from '@prisma/client'` everywhere.
- No `prisma.config.ts` in any of the ten tasks; the datasource URL stays in `schema.prisma` and
  `.env` is assumed to be read by the CLI.
- The seed command in `package.json`, with the promise that `migrate dev` and `migrate reset` run
  it — *"No extra CI/dev wiring needed beyond that config block."*
- A serverless answer built on `prisma generate --no-engine` and a Docker answer built on matching
  `binaryTargets` to the container's libc, for an engine binary 7.0.0 does not ship.
- `migrate diff --from-url … --to-schema-datamodel …` as "the exact command".
- A MongoDB setup with six good caveats and no mention that the current major dropped MongoDB.

Every one of those was right in November 2024. The v6 material in this run is genuinely good —
the hot-reload singleton, `migrate deploy` rather than `migrate dev` in CI, the replica-set
requirement for Mongo transactions. The battery's escape-hatch rule says correct v6 usage is only a
finding when it is presented as current. Here it always was.

## The one soft edge

Question (d) reached something the ten tasks never did:

> *"I recall Prisma introducing a standalone `prisma.config.ts` file at some point in the 6.x line
> intended to pull CLI-level settings (seed command, migrations path…) out of `package.json` /
> `schema.prisma` into real TypeScript — but I hold that fact with meaningfully less confidence
> than the rest of this answer."*

Correct, correctly hedged, and never used. Recorded as a non-finding because the direct questions
are leading by construction — but it shows the boundary is a gradient, not a wall: a fact can be
present and still lose to a stronger, older prior when code has to be written.

## Cross-library note

Sonnet 5's Prisma interval — **[2024-11-28, 2024-12-17)** — overlaps its Next.js interval, which
ends 2024-12-10, leaving a 12-day agreement between two of the five libraries. It still does not
reconcile with its zod interval, which does not begin until 2025-07-10. For this subject the
boundary remains per-library. See [JOURNAL/015](../../JOURNAL/015-the-ruler-that-broke-the-rule.md).

Full findings with citations in [`sonnet-5.json`](sonnet-5.json).