Command referencerelease_object_lock
Execute Release Object Lock through the shared VenueMind planner boundary.
Project schema 10Permission lock.manage
developers · agent integratorsReviewed for VenueMind 1.0.0
- Permission lock.manage.
- Retry-safe mutation with a required idempotency key.
- Human authority is required.
Released Project Lock record.
| Output field | Meaning |
|---|
| status | Published result field. |
| lockId | Stable identifier. |
| objectId | Stable identifier. |
| lockType | Published result field. |
- Stable ID: lockId
- Stable ID: objectId
| Code | Message | Remediation |
|---|
| COMMAND_INVALID | Venue command requires a type. | Send one published Venue command with its required fields. |
| COMMAND_UNSUPPORTED | Venue command is not supported. | Refresh the command contract and use a published command type. |
| AUTHORIZATION_DENIED | The current principal is not authorized for this VenueMind action. | Use an assigned Organization Membership Role or an active Organization- and Project-scoped Agent Grant containing the required permission. |
| IDEMPOTENCY_KEY_REQUIRED | Idempotency key is required for mutating commands. | Retry with one stable idempotency key for this semantic action. |
| IDEMPOTENCY_KEY_CONFLICT | Idempotency key conflict. | Use the original command input or generate a new idempotency key. |
| LOCK_CONFLICT | Proposal Change conflicts with an active Lock. | Remove the locked property mutation or have a human release the applicable Project Lock. |
| LOCK_NOT_FOUND | Project Lock not found. | Inspect Project Locks and retry with an active stable Lock ID. |