Projects and the record
Why a Thesivor project is a folder, what record/ holds, and what survives a clone.
In short
A project is an ordinary folder. Thesivor keeps the work you authored in record/, tracked by git, and a fast cache in .thesivor/, which can be rebuilt from the record. That means a clone of the folder still contains your rounds, notes and claims.
1Everything you author lands in record/
Boardroom rounds, verdicts, paper notes, claims, claim links, annotations, literature state, documents, versions, cost events and the tracker log.
2The cache can be thrown away
.thesivor/ holds SQLite for speed. Delete it and reopen: datasets and papers come back from record/index/ plus the files on disk; rounds, claims, notes and costs come back from record/.
3The README is a projection
README.md has a managed block between <!-- thesivor:begin --> and <!-- thesivor:end -->. Thesivor rewrites only that block; anything you write outside it is never touched.
For technical users
Serialization is deterministic (sorted keys, stable ordering, fixed number formatting, newline-terminated) so an autosave does not produce a spurious diff. A dataset whose bytes changed is reported, never restored pointing at nothing. A link whose passage id is gone is re-linked by recorded coordinates, never guessed. Cost files record model, tokens, cost and purpose — never keys or request bodies.