Libraries as civic learning and access points
Help a patron move from a headline to a checkable public record. The library pathway centers on access, source literacy, and neutral process navigation rather than asking a library to support or oppose a development proposal.
A kit for the next question at the desk
The library civic resource kit organizes terminology, land-use records, utility and regulatory material, public-money questions, environmental records, and meeting notices. It is a starting point for locating records, not a database of local answers.
Print the kit for a reference desk, link it from a research guide, or use its prompts in a staff or community learning session. When a patron names a proposal, record the jurisdiction, issuer, document date, and question before drawing a conclusion from a general article.
Build local context without speaking for everyone
A library can identify a local hearing notice, an official planning page, a public dataset, or a gap in an existing source list. Submit the original link and describe why it matters. A meeting notice is evidence of a scheduled process, not evidence that a proposal was approved.
Do not send patron records, private questions tied to an identifiable person, or restricted material. Institutional participation does not authorize a public statement on behalf of patrons or the surrounding community.
Request a session or a resource collection
Use the briefing request form to propose a data-literacy session, a library workshop, or a discussion about reading infrastructure claims. Tell us the audience, geography, preferred dates, access needs, and topic. Submission records a request; it does not reserve a speaker or confirm a date.
An approved organization can propose a local collection made from reviewed public contributions. Each resource keeps its source-level attribution. An organization profile is published only after a separate public-display review and consent check.
What approval does and does not mean
Participation is not endorsement of this project, any organization, or data-center development. Institutions may submit evidence and context, but they cannot execute or publish Team_Compute articles. Article publishing remains owner-only.
Applications, source submissions, regional associations, events, and resource collections have separate review states. A received request is not an approved relationship. An approved workflow state is not a measure of evidence quality. Public material retains its issuer, date, geography, limitations, review context, and a correction route.