The source's documents live in RAM and nowhere else

A source hands you 300 pages. You open them in a container, but not on its disk. You drop them into /ramdisk, the RAM-backed scratch space every container has.

/ramdisk is never on a disk. Not in a snapshot, not in a backup, not on a seized drive. /ramdisk/secrets is mode 0700; only the container's own root can open it. You read, grep, take notes elsewhere, and rm the folder when you're done. The RAM frees itself.

A founder uses the same mount to keep a heavy query out of storage. You use it because the documents should not survive you closing the tab. Same directory, opposite reason.

The pool is 512 MiB by default, shared across your containers on that server.

The safest place to keep a file is one that was never written.