Java history and request windows: can a trimmed fact return?

01 / QUESTION

Follow narrowing, commit, restart and expansion to separate durable conversation history from one request context.

METHOD

Freeze protocol and source before execution, save raw records, then independently recompute metrics and verify hashes.

RESULT

140/235/308-byte boundaries retain 0/1/2 turns; 139 bytes is rejected without mutating stored history.

OBSERVATIONS

140/235/308-byte boundaries retain 0/1/2 turns; 139 bytes is rejected without mutating stored history.

CONCLUSION

Conclusions are limited to the stated variables and acceptance criteria, retaining failures and unverified scope.

LIMITATIONS

Teaching-scale fixed conditions, not online model quality, production throughput or hardware safety. The complete assistant and VL01 remain unfinished.

REPRODUCE

The article provides a pinned revision, environment, runner and independent audit commands.

1. Engineering cases

   Java history and request windows: can a trimmed fact return?

   Follow narrowing, commit, restart and expansion to separate durable conversation history from one request context.

   2026-10-079 MINPublished
2. PROJECT / 002

   Java LLM Practice

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

   Building
3. Engineering cases

   Java LLM practice 3: don't let a failed request change conversation history

   Candidate snapshots, complete-pair commits and a UTF-8 request budget: 41 offline checks for history that survives failed requests.

   2026-09-3010 MINPublished