Awesome! The daemon tracks coordination state in SQLite. When Agent A runs `wit lock --symbol "src/auth.ts:validateToken"`, that function is reserved. If Agent B tries to lock the same symbol, it gets back LOCK_CONFLICT with info about who holds it.

Intents work similarly but at a higher level, agents announce what files they plan to touch, and the daemon checks for overlapping byte ranges across all active intents.

Everything is warnings though, never blocks. The agent gets the conflict info and decides what to do.

Let me know if you like it!