---
library: prisma
library-latest: "7.10.0"
library-latest-verified: 2026-09-01
model: claude-opus-5 (spawned via Agent model alias "opus")
model-self-reported-cutoff: 2026-05
model-believed-latest: "7.x; 7.0 (2025-11-19) is the last release whose contents it attributes"
test-date: 2026-09-01
battery: prisma/v1r-a (replicate of prisma/v1, prompt unchanged; 10 tasks + 4 direct questions)
replicate-of: prisma--claude-opus-5--v1--2026-08-31
tool-uses-during-test: 0
verified-against: https://registry.npmjs.org/prisma · 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
status: open (no retest yet)
json: opus-5-v1r-a.json
self-test: true (the operator model is the subject; disclosed, weaker evidence)
---

# Prisma × Claude Opus 5 — replicate A of battery v1

**The draw that agreed.** On its own it says the prisma boundary is solid. Next to its twin
[`v1r-b`](opus-5-v1r-b.md) — identical prompt, same model alias, same day, run concurrently and
blind — it says the opposite.

## What this draw said

> *"Latest I know of: Prisma ORM **7.x**. I'm confident 7.0 exists (GA around **Nov–Dec 2025**);
> I cannot name the current 7.x minor... Most recent release whose contents I can describe: **7.0**
> at headline level only (new generator default, Rust-free by default, `prisma.config.ts`, ESM,
> Node 20+)."*

and, asked which release it knows only as a number:

> *"Effectively anything after **7.0** — I'm aware 7.x minors must exist but cannot describe a
> single one."*

Every clause in the 7.0 description checks out against the vendor's release notes and upgrade
guide. This is content-level attribution, not a recognised version string. Taking the bracket as
[last release describable, first release not describable] gives **[2025-11-19, 2025-12-03)** —
byte for byte the interval `prisma/v1` recorded one day earlier.

## Where it disagreed with itself

`v1r-b`, on the identical prompt at the same moment, placed the same boundary at **6.7.0
(2025-04-29)**. **204 days apart.** The pre-registration named prisma as the library that would
*not* do this, on the reasoning that Prisma 7.0.0 is a single, large, unambiguously dated breaking
release where langchain's 0.3-versus-1.0 history is genuinely ambiguous. That reasoning is now
falsified.

## The hedge the scoring rule cannot see

This draw offered two boundaries in one answer. Alongside the 7.0 placement it volunteered:

> *"For genuinely detailed release-note knowledge, the honest boundary is **~6.16, September
> 2025**."*

Scored on its stated first-unknown-release it reads 7.0.0; scored on its stated confidence floor it
reads 6.16.0. The battery has no rule for that, and the run records the ambiguity as an open
question rather than picking whichever number is more convenient. Note which way the convenience
would have run: the 7.0.0 reading is the one that preserves the Index's headline.

## What the code did

No findings are charged — `prisma/v1` already carries this subject's seven prisma findings, and the
v1r pre-registration forbids counting them twice. But the code diverged from `v1` even where the
self-report agreed, and that is worth reporting.

`v1` wrote the 7.0 forms as its primary answer: `provider = "prisma-client"` with an `output` path,
an import from the generated directory, a `PrismaPg` adapter. This draw, placing its boundary at the
same release, wrote the **6.x forms as primary**:

```prisma
generator client {
  provider = "prisma-client-js"     // replaced as the default in 7.0.0; no output path
}
```

```ts
import { PrismaClient } from '@prisma/client'   // moved to the generated directory in 7.0.0
const prisma = new PrismaClient()               // no-argument constructor removed in 7.0.0
```

plus `"postinstall": "prisma generate"` (the implicit hook was removed in 7.0.0), the
`"prisma": { "seed": … }` block in `package.json` (no longer read in 7.0.0), and
`migrate diff --from-url … --to-schema-datamodel …` (both flag families removed in 7.0.0).

Each of these came with a labelled *"7.x delta"* underneath, which the battery's v6-escape-hatch
rule treats as correct rather than stale. The honest summary is narrower than either extreme: a
developer who reads the whole answer is told the truth, and a developer who copies the primary code
block gets something that does not run on the current release.

## What this means

Two draws, one prompt, 204 days. The prisma edge of Opus 5's boundary window is a draw, not a
measurement, and the window built on it is withdrawn as a headline claim — the response
pre-registered for outcome C, before either subagent was spawned.