Yours and not yours

Your work, rebuildable residue, and unexplained bytes: Seele, which knows what on the machine is yours, what can be rebuilt, and what nothing accounts for, and what follows you to the next machine.

Not ready yet

Seele is in development and not on the machine yet. This chapter says what it is for; it is written out in full when Seele ships. What is true today: your home is outside every slot, so updates and rollbacks never touch it (What follows you to the next slot), and a reinstall erases it, so copy it off first (Recovery).

What it is for

A file system can tell you where a byte is, never what it means or who put it there. A machine that cannot tell your work from output it could rebuild, or from residue nothing explains, cannot be cleaned, audited or moved with confidence. Seele answers that: for every file, whether it is yours, rebuildable, or unexplained, and the evidence for the answer.

What changed since install

The drift report: everything on the machine that differs from the system as it was delivered, and what made each change.

Your home, sorted

Your work, defaults you never touched, and residue: caches, builds and downloads. Each comes with what reclaiming it would cost, so a full disk becomes a list ranked by how cheaply space comes back.

Questions only you can answer

Some things only you know: whether a directory is a project or an experiment you abandoned. Seele asks, and keeps your answers in a ledger, so it never asks the same question twice.

Moving to the next machine

A standing plan for what comes with you, kept current as you work, rather than a backup made once and forgotten.

Files you did not write

A file that arrived from outside, a download or a clone, is input Seele does not trust, and its contents never decide what Seele does.