diff --git a/docs/decisions/0006-persistence-postgresql-prisma.md b/docs/decisions/0006-persistence-postgresql-prisma.md
index cd054f4..b0717ba 100644
--- a/docs/decisions/0006-persistence-postgresql-prisma.md
+++ b/docs/decisions/0006-persistence-postgresql-prisma.md
@@ -46,6 +46,22 @@ The engine is pinned to the latest stable major at workspace bootstrap, and trac
 
 Prisma is wired into NestJS via the `nestjs-prisma` integration, with a dedicated `PrismaService` extending `PrismaClient` and exposed through DI. Migrations are managed by `prisma migrate`, committed to the repository, validated in CI, and applied through a controlled deployment step (covered by a future infrastructure ADR).
 
+### Prisma version pin: 6.x in v1
+
+The "latest stable major" rule above is **temporarily** narrowed to **Prisma 6.x** in v1. Reason: at the time of workspace bootstrap, Prisma 7 was the latest major, but `nestjs-prisma@0.27.0` (the only maintained NestJS integration) is not compatible with Prisma 7 — `PrismaClient` instantiation throws under the new driver-adapter contract. We hit this directly in PR #3 and downgraded to Prisma 6.
+
+Concretely:
+
+- `prisma` and `@prisma/client` are constrained to `6.x` in `package.json`.
+- `renovate.json` declares an `enabled: false` rule for **major** bumps of `prisma`, `@prisma/*`, `nestjs-prisma` so Renovate stops re-proposing the upgrade until we lift the pin.
+
+This pin is revisited (and an upgrade ADR is opened) when **either** of these triggers fires:
+
+1. `nestjs-prisma` ships a release that supports Prisma 7 (the wrapper catches up); or
+2. We decide to drop `nestjs-prisma` in favour of a hand-rolled `PrismaModule` (the wrapper is replaced).
+
+Either path is a non-trivial change — schema, client instantiation, and the request-scoped lifecycle all need to be re-validated — so it warrants its own ADR rather than a silent Renovate merge.
+
 ### Consequences
 
 - Good, because PostgreSQL is the de facto enterprise open-source RDBMS — mature HA, replication, RLS, JSONB, full-text search.
@@ -58,9 +74,10 @@ Prisma is wired into NestJS via the `nestjs-prisma` integration, with a dedicate
 
 ### Confirmation
 
-- `apps/portal-bff` depends on `prisma` and `@prisma/client`.
+- `apps/portal-bff` depends on `prisma` and `@prisma/client`, both pinned to `6.x` (see "Prisma version pin: 6.x in v1" above).
 - A single `schema.prisma` lives at `apps/portal-bff/prisma/schema.prisma`.
 - `nestjs-prisma`'s `PrismaModule` is imported globally in the BFF.
+- `renovate.json` carries an `enabled: false` rule on `matchUpdateTypes: ["major"]` for `prisma`, `@prisma/*`, `nestjs-prisma`. The rule disappears in the same PR as the Prisma 7 upgrade ADR.
 - CI runs `prisma validate` and `prisma migrate diff` against the staging schema.
 - Database engine version is pinned in deployment manifests.
 
diff --git a/renovate.json b/renovate.json
index 3b1284f..e996a6e 100644
--- a/renovate.json
+++ b/renovate.json
@@ -38,6 +38,12 @@
       "groupName": "Prisma",
       "matchPackageNames": ["prisma", "@prisma/*", "nestjs-prisma"]
     },
+    {
+      "matchPackageNames": ["prisma", "@prisma/*", "nestjs-prisma"],
+      "matchUpdateTypes": ["major"],
+      "enabled": false,
+      "description": "Prisma 7 requires a coordinated upgrade with nestjs-prisma compatibility (Prisma 7 was downgraded to 6 in PR #3 because nestjs-prisma 0.27.0 is incompatible with Prisma 7). Re-enable once a Prisma 7 ADR lands and the wrapper situation is settled — see ADR-0006 §'Prisma version pin: 6.x in v1'."
+    },
     {
       "groupName": "Vitest",
       "matchPackageNames": ["vitest", "@vitest/*", "/^vitest-/"]