RECORD LOCKING — TWO INDEPENDENT PRACTICE SESSIONS
Owner-controlled hosted test file; no production data.
Requests: RequestID, Status (Text). R001 Draft; R002 Draft.
A changes R001 to In review without committing.
B preserves Ready proposal and reviewed state separately; attempts lock.
B captures actual error immediately; conflict must not write or claim success.
A commits. B retries explicitly, locks then rereads, detects changed state.
Release only this operation's lock before asking for review.
After review, acquire again and recheck before writing.
Test cancel, another change before retry, R002, validation and read-only account.
Capture write and commit errors. Failed commit is not an automatic revert.
Log exact Pro/Server versions, account, operation, actual error and stored value.
Two windows alone do not demonstrate two-client behavior.
Algorithm only; no native implementation or runtime result supplied.