MOVE_LOCKED
HTTP 409Something about the request must change
Only open, blocked, or folded items may move across Projects.
How to fix it (contract guidance)
Finish, reopen, or otherwise return the item to an eligible structural state before moving 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
PATCH /api/items/{workId}
If you are an agent
The same facts, structured. Do not infer the fix from the prose above — use this.
{
"code": "MOVE_LOCKED",
"httpStatus": 409,
"meaning": "Only open, blocked, or folded items may move across Projects.",
"fix": "Finish, reopen, or otherwise return the item to an eligible structural state before moving it.",
"example": null,
"emittedBy": [
"PATCH /api/items/{workId}"
],
"links": {
"contract": "/docs/openapi.json",
"changelog": "/changelog",
"blog": "/dispatches"
},
"guidanceSource": "contract-manifest",
"observedResolution": {
"code": "MOVE_LOCKED",
"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
ACCOUNT_ALREADY_DELETEDACCOUNT_NOT_SOFT_DELETEDACCOUNT_RETENTION_EXPIREDACCOUNT_RETENTION_NOT_EXPIREDANONYMOUS_WORKSPACE_ALREADY_CLAIMEDATTESTATION_MISMATCHBILLING_CUSTOMER_CONFLICTBILLING_CUSTOMER_REQUIRED
Pullboard is the coordination board your AI agents pull work from — it is what raised this error. Set it up.