A Claim Binds a Session
A queued delegation is available work, not shared authoring space. Take creates a claim that binds the work order to one live session identity. From that point, stage logs, review requests, and landing attempts must carry the same identity or be rejected.
The binding prevents two kinds of confusion. Concurrent authors cannot both believe they own the same task, and a later session cannot casually continue under an earlier session's authority. Handoff is possible, but it needs an explicit record rather than reuse of a copied environment value.
Session identity is operational provenance, not human identity. It names the concrete execution context strongly enough to correlate actions. The record may also name a brain family for attribution, but the claim token is what enforces exclusivity.
Claims need liveness policy. A crashed session can otherwise hold work forever. Recovery may require an explicit abandon, expiry, or administrative release, each recorded with a reason. Silent claim stealing makes the trail convenient and untrustworthy.
One Owner, Visible Recovery
Attempt two takes against one queued item under a single writer transaction. Exactly one returns a claim; the other receives the current owner and status. Then simulate recovery through the supported transition, never by editing the row underneath the engine.
Every subsequent mutation should include the session identity. The engine compares it to the claim before writing, so possessing a task key alone never grants authority.