A2 / Concurrent history commits

01 / QUESTION

Reproduce reversed response order with real Java threads, then enforce versioned commits, complete turns and bounded receipts.

METHOD

Actual Java threads with latch-controlled response order; eight session checks.

RESULT

The fast reply commits; the stale reply is rejected. One pair and one version increment remain.

OBSERVATIONS

Receipts, version conflicts and incomplete turns are handled separately; no model requests.

CONCLUSION

Request generation can happen outside the lock, but stale responses cannot blindly join current history.

LIMITATIONS

In-process state and bounded receipts only; no remote exactly-once guarantee or exhaustive concurrency proof.

REPRODUCE

See the pinned repository for code, frozen parameters, raw results and independent auditing.

1. Engineering cases

   Java LLM IV: which concurrent response may commit?

   Reproduce reversed response order with real Java threads, then enforce versioned commits, complete turns and bounded receipts.

   2026-10-038 MINPublished
2. PROJECT / 002

   Java LLM Practice

   Reproducible Java conversation, retry and persistence boundaries, alongside attention, cache-cost and quantization-error experiments.

   Building