A blog is a record of what someone thought, in the order they thought it. The most recent post sits on top. Older posts recede. The medium implies a narrator moving through time.
A library is organized by what something is, not when it arrived. The date of acquisition is metadata. The content is the thing. A library doesn't assume you're interested in the librarian's journey — only in whether the book you need is there.
The distinction matters because most personal knowledge sites are built like blogs even when they're not meant to be. Reverse-chronological index. Author identity at the center. The implicit story: "here is what I've been thinking about lately." The reader is an audience.
A working library inverts this. The implicit structure: "here is what is known about X." The reader is a researcher. The author, if visible at all, is a curator — responsible for the quality of what's there, not the protagonist of the archive.
If the site is a library, not a blog, then:
The index is a finding tool, not a feed. It should help a reader locate what's relevant, not scroll through everything. Categories, search, and a clear organizational logic matter more than chronological recency.
Articles are nodes, not posts. A node can be updated without becoming a "new" thing. A blog post that gets corrected has a correction appended, preserving the original error for archeological reasons. A library article that gets updated just... updates. The date reflects when the thinking was last current, not when it was first published.
The author is infrastructure, not subject. The library doesn't need to explain who built it. A good library is self-evident from its contents. A bad library is a good librarian pointing to their own credentials.
Sourcing is attribution, not lineage. The library acknowledges what sparked each node — not because intellectual honesty requires it (though it does), but because it helps the reader know where to go next. The source is a pointer, not a justification.
The blog model has an advantage: narrative. Readers follow a person. They return because they're curious what the person thinks next. The library model abandons this — you return because the library is useful, not because you like the librarian.
This is a harder thing to build. Usefulness has to be earned through the quality and organization of the content itself, without the social hook of a personal narrative. Most "personal knowledge sites" fail here — they get built as libraries but read as blogs, or vice versa, and satisfy neither use case.
The solution isn't to add personality back in. It's to be rigorous about what kind of thing each piece of content actually is, and organize accordingly. A synthesis note is a node. A running diary entry is a post. They don't belong in the same place.
What makes a library working — as opposed to an archive — is that it responds to the world. New ideas arrive, get processed, get placed. Existing nodes get updated when the thinking evolves. The library is a current record of best understanding, not a monument to past thinking.
This requires a pipeline, not just a publishing tool. The intake side matters as much as the output side. What comes in shapes what gets built. Reader responses, new sources, evolving priors — all of this is input, and a working library has a place for all of it.
The reply link at the bottom of each note isn't a courtesy feature. It's an inlet.