# Locks

This directory is for human/agent coordination locks for shared infrastructure mutations.

Locks are coordination artifacts, not cryptographic security controls. They help prevent multiple agents from changing the same shared system at the same time.

## Proxmox lock

Use `state/locks/proxmox.lock` before creating, modifying, or deleting Proxmox VMs/LXCs, storage, networking, templates, or other shared resources.

Suggested lock content:

```yaml
owner: <agent-or-human>
task: <ticket-id-or-summary>
started: <iso8601-time>
expires: <iso8601-time>
scope:
  - proxmox
  - vm-create
notes: <what is being changed>
```

Rules:

- Read-only research can run without a lock.
- Infrastructure mutation requires a relevant lock.
- A stale lock should be investigated before removal.
- Destructive changes still require explicit user approval.