Versions and freezing
The live draft, frozen snapshots, and why a review attaches to a version.
In short
You work on a live draft. When you submit it, you freeze it: Thesivor copies the source tree, the compiled PDF and the SyncTeX file into a read-only, content-addressed snapshot. Reviews attach to that frozen version, and the live draft continues separately.
1Compile, then freeze
Check traceability runs first. Then Freeze version writes a snapshot with a number and a note. With automatic commits, a freeze is also a tagged milestone commit.
2Reviews attach to the snapshot
A review round lives with the frozen version. A review of version 1 stays readable after version 2 exists.
3Revise and freeze again
The revision is a new version. Nothing about the submitted snapshot or its reviews changes. A changes PDF can be produced between the two versions.
For technical users
Snapshots are content-addressed under record/objects/, with a write-once manifest at record/versions/<doc>/v<N>.json; blobs are read-only (0444) and their SHA is re-checked on every read. The PDF must have been compiled from exactly that tree. Restore copies a version into the live draft as one new change.