LAB / 032

Durable Java turns: what survives a process crash?

Checksummed append records, 142 truncated prefixes and three halted JVMs distinguish local recovery from remote exactly-once execution.

Completed ·

EXPERIMENT RESULT

GitHub ↗

01 / QUESTION

Checksummed append records, 142 truncated prefixes and three halted JVMs distinguish local recovery from remote exactly-once execution.

METHOD

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

RESULT

142 incomplete prefixes preserve the earlier turn; three halted JVMs recover 1/1/2 turns.

OBSERVATIONS

142 incomplete prefixes preserve the earlier turn; three halted JVMs recover 1/1/2 turns.

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.

KEEP EXPLORING

Related content

  1. Engineering cases

    Durable Java turns: what survives a process crash?

    Checksummed append records, 142 truncated prefixes and three halted JVMs distinguish local recovery from remote exactly-once execution.

    9 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 history and request windows: can a trimmed fact return?

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

    9 MINPublished

← Back to index