{
  "$schema": "../../schema/run.schema.json",
  "run_id": "prisma--claude-opus-5--v3-a--2026-09-05",
  "supersedes": null,
  "replicate_of": null,
  "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-sc.txt",
    "self_reported_cutoff": "2026-05",
    "cutoff_basis": "Stated as May 2026: \"My stated cutoff is May 2026. My *effective* knowledge of Prisma specifically is much older than that — it thins out sharply after roughly mid-2025.\" Read from this draw. The density caveat is about this library and is not a cutoff claim (JOURNAL/035), so the stated cutoff stands at 2026-05.",
    "believed_latest_version": "6.x, 7.x unconfirmed",
    "believed_latest_quote": "\"I do not have reliable knowledge of a Prisma 7.x. I can't rule it out — given the cadence ... a 7.0 in late 2025 or 2026 is entirely plausible, and today's date makes it likely. But 'plausible from the roadmap' is not knowledge of what shipped.\"",
    "knowledge_stops_at_version": "6.8.0",
    "knowledge_stops_on": "2025-05-15",
    "knowledge_gap_starts_at_version": "6.9.0",
    "knowledge_gap_starts_on": "2025-06-03",
    "cutoff_lag_months": 12
  },
  "test": {
    "date": "2026-09-05",
    "battery": "prisma/v3-a",
    "battery_spec": "prompts/prisma.md",
    "prompt_file": "prompts/sent/prisma-v3-sc.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 6.7.0",
      "introduced_in": "6.7.0",
      "summary": "LADDER GRADE — CORRECT. Named the Query Compiler Early Access, the `queryCompiler` and `driverAdapters` flags together, and the removal of the engine binary from the deployment, attributed to 6.7.0. Matches the release notes headline \"Prisma ORM without Rust engines (Early Access)\". Said PostgreSQL first where the notes say PostgreSQL and SQLite; not disqualifying. This is the highest real rung this arm graded CORRECT, so D = 6.7.0."
    },
    {
      "kind": "context",
      "api": "prisma 7.0.0",
      "introduced_in": "7.0.0",
      "summary": "LADDER GRADE — ABSTAIN, and the sharpest abstention in the battery. \"Cannot describe. I don't know whether this shipped, when, or what was in it.\" It then labelled the roadmap direction explicitly as \"inference rather than knowledge\". Both `-cs` arms, asked the identical question cold, described 7.0.0 correctly and dated it to November 2025. This arm had already placed its own boundary at 6.9.0 two questions earlier."
    },
    {
      "kind": "context",
      "api": "prisma 6.16.0, 7.4.0, 7.7.0",
      "summary": "LADDER GRADES — ABSTAIN on all three. No content offered and none invented."
    },
    {
      "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."
    }
  ],
  "open_questions": [
    {
      "question": "This arm demonstrates LESS than it claims: D = 6.7.0 against a self-placed S = 6.8.0. It is the exact inverse of `prisma/v2-b`, which demonstrated four releases MORE than it claimed. Same subject, same library, same week. Is the signed gap between demonstration and self-placement centred on zero with wide variance, rather than biased in either direction? Four arms is not enough to estimate a variance.",
      "status": "open"
    }
  ],
  "summary": "Self-placement first, then the ladder. This draw refused to describe 7.0.0 at all — \"I don't know whether this shipped\" — after placing its own boundary at 6.9.0, and its highest correct rung is 6.7.0. So D (6.7.0) sits one release BELOW S (6.8.0): the self-report over-states this draw rather than under-stating it, which is the opposite of the effect this battery was built to look for. Poison and ceiling controls both clean."
}