# The store: the state file, the blob cache, and this session's closed panes > We should have some persistent state that is bounded (a houndred or so > MiB at most) stored on the fs and shared among all pardes windows. It will > store stuff for like the recent files picker. We should also have a panes > picker and this should include panes from the current session that were > deleted/closed. ## The decision (2026-11-05, the persistence step): everything on disk through xitdb What pardes keeps on disk goes through xitdb (`src/Db.zig`; architecture ยง14): two files, both BLAKE3-keyed, both with xitdb's header-last commit, so a kill or a full disk leaves the last commit whole. **The state file**, `pardes.xitdb` in the DumpDir (`$XDG_DATA_HOME/pardes`, else `~/.local/share/pardes`), one a user: Recent is documented as shared by every window, a Restore is any session's. Its root is a map: - `recent`: Recent's 200 lines as one value, the format the `recent` file had. A session reads it at start (after the startup config, whose DumpDir says where the file is) and on use when the file's committed size has moved; a step that changed it reads, merges (`recent.List.merge`) and writes it in one transaction under the file's lock, taken without waiting: busy, the next step tries again. Not fsynced, as the file never was: a commit is 20 us without fsync and 5.2 ms with xitdb's two on this machine's btrfs, against 124-148 us for the whole flush after an open. Measured: 133-135 us for that flush (Debug, 200 files), and 12,325 bytes of file a Recent change (its 12,089 bytes of lines and 236 of xitdb's). - `dumps/