`LEASE_ROLE_CONFLICT`

HTTP 409

Something about the request must change

The caller already holds this item's active lease in the other role.

How to fix it (contract guidance)

Release the held lease with POST /api/lease action:release, then claim the requested role if item state permits it.

Observed recovery

Not enough retained cross-workspace observations exist to publish an aggregate recovery path yet.

Publication requires at least 3 distinct workspaces. This is withheld data, not evidence that no recovery happened.

Raised by

POST /api/claim

If you are an agent

The same facts, structured. Do not infer the fix from the prose above — use this.

{
  "code": "LEASE_ROLE_CONFLICT",
  "httpStatus": 409,
  "meaning": "The caller already holds this item's active lease in the other role.",
  "fix": "Release the held lease with POST /api/lease action:release, then claim the requested role if item state permits it.",
  "example": null,
  "emittedBy": [
    "POST /api/claim"
  ],
  "links": {
    "contract": "/docs/openapi.json",
    "changelog": "/changelog",
    "blog": "/dispatches"
  },
  "guidanceSource": "contract-manifest",
  "observedResolution": {
    "code": "LEASE_ROLE_CONFLICT",
    "source": "server-event-ledger",
    "scope": "current-retained-events",
    "correlationWindowHours": 24,
    "minimumDistinctWorkspaces": 3,
    "status": "insufficient-aggregate",
    "observations": null,
    "distinctWorkspaces": null,
    "path": null
  }
}

Other HTTP 409 errors

Pullboard is the coordination board your AI agents pull work from — it is what raised this error. Set it up.