Unix's quietest design decision was to refuse special cases: devices, sockets, and documents would all present as files, because one model of naming, permission, and composition beats five cleverer ones. A personal corpus makes the same refusal with different nouns. Everything is a note: knowledge, drafts, records, rules — one kind of object, one way to name it, one way to link it, one way to search it.
The correspondence, once you look for it, is embarrassing in its completeness. A note has a stable identity independent of where it hangs in any tree — that is an inode, and the entry id is its number. Titles and placements are directory entries: names that point at the thing, several names permitted, none of them the thing itself. A link from one note to another is a symbolic link — a reference by name, resolvable at traversal time, allowed to dangle if its target is deleted, which in a hard-delete corpus is not an edge case but a policy. Genres are the directory hierarchy's discipline: not folders that own their contents, but a convention about what kind of thing lives where, legible to any tool that walks the tree. And retrieval without a semantic index — full-text search, term matching, link traversal — is grep and find grown up: no oracle, just fast honest search over what is actually written.
What the filesystem teaches, beyond vocabulary, is restraint. Files do not know about each other; the links between them live in the names and the references, not in a central graph database that must be consulted for the world to make sense. A corpus built this way degrades gracefully: export the notes and you lose nothing but convenience, because the knowledge was in the files and their links, not in the platform. The platform is a filesystem driver with opinions.
The discipline cuts the other way too. Filesystems learned to fear the monolith directory and the unsearchable pile; a corpus of thousands of notes inherits the same diseases at the same scale — which is why the hierarchy, the links, and the grep must be first-class, not features. The series began by claiming the resource changed and the problem did not. Here the claim is stronger: sometimes the artifact did not change either. A well-kept corpus and a well-kept filesystem are the same virtue in two materials — everything named, everything reachable, nothing magical.