A noticeboard that machines can read too
Every town once had a physical noticeboard: events, things for sale, club meetings, services offered. The community library carries that function digitally—plus the guide information a town runs on: amenities and their locations, local businesses, organisations and clubs, for locals and tourists alike. Because entries are written in the shared dictionary, a visitor's phone, a kiosk or a local assistant can answer "what's on, where, for whom"—and the information stays in the community instead of feeding a platform's advertising engine.
A living archive
Heritage and historical societies curate their own collections; local media publishes; community groups keep their records in community-controlled storage—rather than on a corporate platform that can vanish, or a hard drive in a shed nobody can reach. The library holds what a community knows about itself, under the community's own stewardship.
A window on local government
Here the civic/civics distinction becomes visible: the library belongs to the community, but it provides the interface to civic institutions. Council submissions and consultations, new initiatives and proposed laws, grants and funds, links to government services and GIS mapping, reporting issues like potholes, licensing matters—reachable from the same place a resident checks the noticeboard, without the council's systems holding the community's data.
One namespace, many communities
The library is also the community's digital hub—and that matters technically, not just socially. When neighbouring communities run the same stack, their public resources need a predictable way to find and query each other: a shared namespace—one agreed addressing scheme for the town's noticeboard, collections, amenities and services—so that federated queries (standards like SPARQL) can reach across sites without a central platform in the middle.
That is what turns a local catalogue into a regional one: each community keeps its own data and its own rules, while the shared namespace lets people—and software—discover resources, skills and projects across the whole network. A resident can find which ground has a free workshop bench, an event worth the drive, or a project needing their skills; the network can answer questions no single site could answer alone.
When shared work earns
The library also handles the money where the ledger says it should go. When commercial users buy derivative works built on community contributions, the fees route back to the original contributors until their obligation costs are fairly met. And if a contributor does not want the money, they can nominate a charity or cause to receive it—the acknowledgement still lands in their community portfolio, because recognition and payment are separate things.
The same account opens the gate
Because the library is part of the same ecosystem as the grounds, a person's profile works as a universal local key: campsite check-ins, access to amenities, small payments for shared services, IoT-connected facilities. One account, one set of permissions, no fragmented third-party systems—and the person can see exactly what each access shared.
What it stands on
The library is an application, not a foundation—it requires the layers beneath it: personal data safes for the people it serves, the databox for governed exchange, the knowledge-bank cooperative to run it, the community ledger for contribution and compensation, and the edge stack it physically runs on. Which is precisely the point: each foundation makes institutions like this possible, and each institution makes the foundations worth having.