The Public Brain
A working library is not a portfolio. It exists to think with, not to be looked at — and that single difference makes every design decision flip.
A portfolio exists to be looked at. A working library exists to be thought with. The difference is small in description and total in design.
A portfolio is optimised for the visit. Each piece is the most polished version of itself. Navigation is shallow because the visit is shallow. The order of items is curated for first impression. Drafts and dead branches are hidden, because they would dilute the impression.
A working library is optimised for the operator. Pieces are kept in their working state — a finished node next to a stub next to a dormant question — because the operator has to find them again, and the friction of polishing every node before publishing means most of them never get published. Navigation is deep because the operator's path is deep. The order is structural, not curated. Drafts are visible because the operator is the audience and the operator already knows.
The trap is that working libraries published online are read by people who came in expecting portfolios. They are confused, because the design is wrong for them, and they leave. Then the operator is tempted to redesign for the visitor. Once that happens, the library is no longer a working library; it is a portfolio with extra pages. The friction returns. Most nodes don't get written. The system fails as a thinking environment.
The resolution is to be honest about which one the site is. A library does not need to apologise for being a library. The visitor who came expecting a portfolio is welcome to leave; the visitor who walks the graph and finds something useful was the audience all along. The operator does not lose by losing readers who came in for a different format.
The public brain is an interface decision: the site is the operator's external memory, and you are welcome to read over the shoulder.