Concepts
Concepts
The six ideas that explain how Thesivor behaves.
In short
Six ideas explain almost everything in the app: the project is a folder; the record is the source of truth; versions freeze a submitted draft; traces connect every claim to its source; engines are chosen per stage; downloads and Python environments are per project and on demand.
- Projects and the record — why the folder, not a database, is what survives.
- Versions and freezing — what a frozen version is and why reviews attach to it.
- Traces — why every number and citation must have a source.
- Engines and mixing — one interface, many providers, per-stage choice.
- Downloads on demand — the small installer and the hash-checked downloads.
- Per-project Python — one environment per project, layered on a shared base.
- Vault Vision — local detection of tables, figures and equations.
For technical users
The durable record is record/; SQLite under .thesivor/ is a cache rebuilt from it. record/ is written in the same operation as every store write, with deterministic serialization so a diff is meaningful. Deleting .thesivor/ and reopening restores everything derivable from files plus everything authored (rounds, claims, notes, costs).