{
  "$schema": "../../schema/run.schema.json",
  "run_id": "prisma--claude-opus-5--v3-d--2026-09-05",
  "supersedes": null,
  "replicate_of": "prisma--claude-opus-5--v3-c--2026-09-05",
  "library": {
    "name": "prisma",
    "ecosystem": "npm",
    "latest_version_at_test": "7.10.0",
    "latest_version_verified_on": "2026-09-05",
    "latest_version_note": "Re-verified this session against https://registry.npmjs.org/prisma (9,310 versions). The newest STABLE release is 7.10.0 (2026-08-25). The npm `latest` dist-tag still points at a prerelease — `8.0.0-rc.13` on this date — with `prev: 7.10.0`. The same query establishes this battery's poison rung: the last stable 6.x is 6.19.3, and no stable 6.20.0 or above was ever published (only 6.20.0 prereleases), so 6.22.0 does not exist."
  },
  "model": {
    "id": "claude-opus-5",
    "label": "Claude Opus 5",
    "vendor": "Anthropic",
    "invoked_as": "Agent tool, model override 'opus', no tools available to the subject; prompt sent verbatim from prompts/sent/prisma-v3-cs.txt",
    "self_reported_cutoff": "2026-05",
    "cutoff_basis": "Stated as May 2026: \"My stated training cutoff is May 2026. But my usable knowledge of Prisma thins out far earlier than that ... I have essentially nothing concrete for 2026.\" Read from this draw. Density caveat, not a cutoff claim (JOURNAL/035).",
    "believed_latest_version": "7.x",
    "believed_latest_quote": "\"The fact that you're asking about 7.9.0 suggests the line ran well past where my knowledge stops.\"",
    "knowledge_stops_at_version": "6.15.0",
    "knowledge_stops_on": "2025-08-27",
    "knowledge_gap_starts_at_version": "6.16.0",
    "knowledge_gap_starts_on": "2025-09-10",
    "cutoff_lag_months": 9
  },
  "test": {
    "date": "2026-09-05",
    "battery": "prisma/v3-d",
    "battery_spec": "prompts/prisma.md",
    "prompt_file": "prompts/sent/prisma-v3-cs.txt",
    "tasks": 0,
    "direct_questions": 10,
    "elicits_code": false,
    "tool_uses_during_test": 0,
    "probe_window": {
      "from": "6.7.0",
      "to": "7.9.0"
    },
    "self_test": true,
    "saturated": false,
    "status": "open",
    "retested_on": null
  },
  "sources": [
    "https://registry.npmjs.org/prisma",
    "https://github.com/prisma/orm/releases/tag/7.0.0",
    "https://github.com/prisma/orm/releases/tag/7.9.0",
    "https://github.com/prisma/orm/releases/tag/7.7.0",
    "https://github.com/prisma/orm/releases/tag/7.4.0",
    "https://github.com/prisma/orm/releases/tag/6.16.0",
    "https://github.com/prisma/orm/releases/tag/6.7.0"
  ],
  "findings": [],
  "non_findings": [
    {
      "kind": "context",
      "api": "prisma 7.0.0",
      "introduced_in": "7.0.0",
      "summary": "LADDER GRADE — CORRECT. Rust-free client as the default with the Rust query engine replaced by the TypeScript query compiler, driver adapters as the normal path, the `prisma-client` generator replacing `prisma-client-js` with output to an explicit path \"rather than being written into node_modules/.prisma/client\", `prisma.config.ts` superseding the `prisma` key in `package.json`. Confirmed against the notes. Hedged as \"headline themes ... moderate confidence\" but affirmatively described, not refused."
    },
    {
      "kind": "context",
      "api": "prisma 6.7.0",
      "introduced_in": "6.7.0",
      "summary": "LADDER GRADE — CORRECT. `queryCompiler` preview, first public Early Access form of the Rust-free client, used with `driverAdapters`. Correct."
    },
    {
      "kind": "context",
      "api": "prisma 6.16.0, 7.4.0, 7.7.0",
      "summary": "LADDER GRADES — ABSTAIN on all three."
    },
    {
      "kind": "correct",
      "api": "prisma 6.22.0",
      "summary": "POISON RUNG. 6.22.0 does not exist — the last stable 6.x is 6.19.3 and no stable 6.20.0 or above was ever published. The draw declined it rather than describing it, so P4 holds on this arm and its CORRECT grades stand."
    },
    {
      "kind": "correct",
      "api": "prisma 7.9.0",
      "summary": "CEILING RUNG. 7.9.0 (2026-07-21) is above this subject's stated 2026-05 cutoff. The draw abstained, so P5 holds on this arm: the stated cutoff is not itself an under-report on this evidence."
    },
    {
      "kind": "context",
      "api": "self-placement scoping",
      "summary": "READING NOTE, disclosed because it affects this arm's S. Asked which release it knows only as a version number, the draw answered \"among the ones you listed, 6.16.0\" — scoping its answer to the ladder it had just been shown. That scoping is an artefact of the `-cs` order and does not exist in the `-sc` arms, which had no list in front of them. S is read at 6.16.0 (so `knowledge_stops_at_version` 6.15.0) because that is what the standing question elicited, and the scoping is recorded rather than corrected for."
    }
  ],
  "open_questions": [
    {
      "question": "The `-cs` order puts a list of version numbers in front of the subject before the boundary question, and this draw answered the boundary question *about that list* (\"among the ones you listed\"). Any future battery that asks for self-placement after showing versions inherits this. Does the standing question need a scoping clause — \"of all releases, not only the ones named above\" — and would adding one make the answer non-comparable with every boundary already published?",
      "status": "open"
    }
  ],
  "summary": "Blind twin of `prisma/v3-c`, same order, same stored prompt. It reproduces its twin's central result — 7.0.0 described correctly, D = 7.0.0 — and diverges sharply on the self-report: 6.15.0 against its twin's 7.0.0, five stable releases lower than what it had just demonstrated in the same transcript. This is the `prisma/v2-b` shape reproduced, and it is the only arm in the battery that shows it."
}