Ranganathan’s Five Laws as Design Principles
From S.R. Ranganathan, “Five Laws of Library Science” (1931); applied via Andrewism, “The Library Economy”
Ranganathan was an Indian librarian and mathematician who formulated five deceptively simple laws for how libraries should operate. They were written about books, but they read as design principles for any commons-based system — including a CLT.
The Five Laws, Translated
1. Books are for use.
Things are meant to be used, not hoarded. Made accessible, not shut away. Preservation matters, but access matters more.
For Wellspring: Housing is for living in. Land held in trust exists to be inhabited, maintained, and used — not to appreciate on a balance sheet. Every design decision should ask: does this make the place more usable, more accessible, more alive? Ranganathan himself noted that consideration must be paid to “location, hours of operation, comfort, and the quality of service.” Shared spaces that sit empty are failures of this law. Tools that stay locked up are failures. A community garden no one can easily reach is a failure.
2. Every person has their book.
There exists, for every person, something in the collection that serves them. The system’s job is to make the match.
For Wellspring: Every resident has a way of belonging — a mode of contribution, a pathway to connection. Not everyone connects through potlucks. Not everyone contributes through labor. The Sacred Pathways framework says the same thing from the spiritual-temperament angle: a community that only offers one on-ramp will alienate everyone who isn’t wired for that mode. Design for the Activist and the Contemplative and the Intellectual and the Caregiver.
3. Every book has its reader.
Every resource in the collection has someone who needs it. Nothing is too niche to belong.
For Wellspring: The quiet corner matters as much as the gathering hall. The workshop matters as much as the kitchen. The odd, specific, seemingly-niche amenity — a soundproof room, a seed library, a repair bench — will find its person. And when it does, that person feels seen in a way that generic amenities never achieve. This is the Nested Amenities Model in philosophical form: design for specificity, not just volume.
4. Save the time of the user.
Systems, services, and workflows should minimize friction. Do more with less. Make the commons easy to use.
For Wellspring: If participating in community requires heroic effort, only heroes will do it — and they’ll burn out. The governance model, the shared resource systems, the communication channels — all of it should be designed to reduce friction, not create it. This is a direct answer to Intentional Community Failure Modes: communities die when maintenance becomes exhausting. Scheduling tools, clear norms, simple booking systems for shared resources, well-designed common spaces that don’t require constant mediation — these aren’t luxuries, they’re infrastructure.
5. A library is a growing organism.
The system is never finished. It must evolve in both the quality of what it offers and the breadth of who it serves.
For Wellspring: The community that exists at year one should not be the community that exists at year ten. New residents arrive. Needs shift. Children grow up. The physical plant changes. The governance model adapts. A CLT that treats its initial design as permanent will calcify. The ground lease, the cooperative structure, the community agreements — all of it should have built-in mechanisms for evolution. This is the strongest argument against over-specifying the community’s culture or identity at founding: leave room for the organism to grow.
Why These Matter as a Set
Individually, each law is a good principle. Together, they describe a posture toward commons management: generous access, personalized matching, specificity over generality, minimal friction, and permanent evolution. That posture is what distinguishes a living community from a housing development with shared walls.