TL;DR: A reviewer needs a retained reference to compare with a decision history later. JPS Desk v0.7.0 exports checkpoints and reports which records they cover, including where that coverage ends. I use AI tools to help prepare these updates.
Imagine a procurement reviewer examining a supplier decision. If the operator controls both the stored history and the interface showing it, another look at that interface still depends on the operator's copy. A checkpoint retained separately gives the reviewer a reference for comparison.
This is a hypothetical business scenario. The implementation described here is in Desk, a companion tool for JPS.
What the hand-over records
Desk v0.7.0 adds a hand-over flow under Admin → Project → Decision record.
The operator registers a holder, downloads checkpoint lines, passes the file to that person, and confirms the hand-over. Each holder has a cursor recording the last confirmed position. A download alone does not move it.
Desk preserves the checkpoint bytes produced by Runtime. When the operator confirms, Desk retrieves the relevant checkpoints again and compares their digest with the downloaded file. A stale confirmation is refused.
The test makes the coverage visible
The integration test TestHandOverWithTheRuntime creates three decision records and confirms a checkpoint hand-over. Verification must report three witnessed records and none unwitnessed.
It then creates a fourth record. The expected report becomes three witnessed and one unwitnessed. The next download contains the additional checkpoint; confirming it brings witnessed coverage to four.
The test also truncates Desk's stored checkpoint file and removes its final newline. In both cases, that file must be excluded from the verification inputs, with the affected holder identified.
PR #241 reports this integration test passing with Runtime 0.27.1. These are repository assertions and a reported execution result, not a fresh test run demonstrated in this article.
Confirmation and independent custody are separate
Desk's confirmation records what the operator says happened. It does not prove delivery or retention, and the operator can change Desk's own record.
Independent comparison depends on the holder keeping their own checkpoint copy. The checkpoint covers a particular portion of the history; it establishes neither the correctness of the business decision nor later activity.
The release also lists limits in its verification coverage, including two Desk processes using the same project and hand-over behavior on macOS and Windows. Passing the project tests should not be read as validation of every operating environment.
I am building and validating this tooling in public. External use of JPS to build a solution remains unknown.
Contribute a missing damaged-checkpoint case to the hand-over tests.
Top comments (0)