Veracity’s lock feature is intended to make Veracity a viable DVCS for teams which manage binary assets under version control.

By its very nature, lock cannot be a local-only operation. There is little to be gained by preventing others from modifying a file in your already-private repository instance. So the lock operation joins clone, push, and pull as the only core DVCS operations which typically require a network connection.

Veracity allows locking of files only, not directories. Each file lock is held by one user and is limited in scope to a single named branch. In other words, you can’t lock a file globally across the whole repository. You can simply say that “file F cannot be modified by anyone else within branch B until my lock is removed”.