Reference
Project layout
Every folder and file a Thesivor project can contain.
In short
A project is a folder you choose. Thesivor adds a handful of its own files and folders and never moves, renames or edits the files you already have.
<project>/
README.md managed block, rewritten by Thesivor; your text outside it is untouched
record/ TRACKED IN GIT — the durable record (rounds, notes, claims, documents, versions, literature, reviews, zenodo)
.thesivor/ gitignored cache (SQLite, agent workspace, run folders)
data/ your datasets (raw/ and processed/)
notebooks/ .ipynb files
papers/ vault PDFs, stored by content hash
figures/ exported figures and charts
draft/ main.tex, sections/, references.bib
proposal/<slug>/ proposal documents (never merged into the paper)
review/ response letters and changes PDFs (confidential by default)For technical users
record/ is the source of truth and is tracked; .thesivor/ is a cache rebuilt from it. record/ is laid out per entity type (record/boardroom/<round>.json, record/notes/<paper-sha>.json, record/index/<entity>.json, and so on), with deterministic serialization so diffs are meaningful. Reviews are excluded from git by default via .git/info/exclude; a review already tracked is untracked by a removal-only commit. .thesivor/agent-work/ and .thesivor/agent-runs/ are added to the project's .gitignore on the first CLI run.