Founding commitments
The Bega Valley Data Commons begins with place before platform.
The project is not initiated by a technology problem, but by a civic and regional one: local knowledge, needs, memories, documents, conversations and capacities are dispersed across many places and systems. The platform is useful only if it helps those places recognise themselves, connect with one another and hold what they know with greater continuity. The digital layer must remain subordinate to the lived geography of the Valley.
Local difference
A valley-wide structure should not erase the distinctiveness of Eden, Bega, Cobargo, Bermagui, Tathra, Candelo, Pambula, Wyndham or any other place. Shared infrastructure should make difference easier to see and navigate, not smooth it into a single regional voice. Each local node should be able to develop its own tone, priorities, administrators, rhythms and forms of usefulness while remaining part of a wider commons.
Stewardship rather than ownership
The domain, forums, archives, records and tools should not be treated as private property, even where legal ownership has to sit somewhere practical. The deeper question is stewardship: who cares for the resource, who has authority to make decisions, who can access it, who can change it, who can protect it, and how responsibility is transferred over time. Ownership may be a legal necessity; stewardship is the commons principle.
Data with context
Data should remain connected to the conditions under which it was produced. A number, story, map, comment, survey result, service gap or local observation only becomes useful when its context is understood: who noticed it, who recorded it, who is affected by it, what it leaves out, what other knowledge it needs to sit beside. The Commons should encourage evidence that remains connected to place, people, history and use.
Community authority over community knowledge
Where knowledge emerges from a local community, that community should retain meaningful influence over how it is held, interpreted, shared and used. This is especially important where knowledge concerns Aboriginal people, cultural matters, vulnerable residents, service gaps, personal testimony, disability, housing, poverty, emergency response, local conflict or institutional failure. Not everything that can be known should automatically be made public.
Openness with care
Open access is not enough. A useful commons needs generosity and boundaries. It should make public knowledge easier to find, share and use while protecting privacy, cultural authority, vulnerable contributors, unfinished conversations and sensitive information. Transparency is not the same as exposure. Openness is not the absence of rules.
Anti-capture
The project should resist capture by any single founder, faction, institution, funder, business interest, council process, political campaign, personality or professional class. This does not mean refusing partnership or leadership. It means designing structures that keep authority distributed, decisions visible, purposes clear and the core infrastructure protected from being quietly redirected.
Usefulness before scale
A small forum that helps ten people coordinate around a real local issue is more meaningful than a large platform with no civic function. Growth should follow demonstrated usefulness. The first question is not "how big can this become?" but "what does this help people do, remember, understand, protect or change?"
Memory
Communities often lose knowledge because conversations disappear, documents are buried, volunteers burn out, institutions restructure, Facebook threads vanish, grant cycles end and informal networks move on. The Commons should help local civic memory persist: what was tried, what was promised, what failed, who helped, what changed, what remains unresolved and what should not have to be rediscovered every few years.
Shared sense-making
The project is not only a noticeboard or archive. It should help people make sense of conditions together: gathering local evidence, comparing experiences, identifying patterns, linking formal data with lived knowledge, preparing submissions, mapping gaps, recording meetings, allowing different accounts of a situation to sit in view long enough to be understood.
Relationship before representation
The Commons should be cautious about claiming to speak for communities. Representation must be earned, specific and accountable. The Commons can host conversations, preserve records, make evidence visible and help people coordinate, but it should not automatically convert participation into a mandate. Its first legitimacy comes through relationship, not declaration.
Unfinished form
The project should be allowed to begin before all structures are complete, but it must not treat incompleteness as readiness. Early forums, first users, draft principles and informal conversations are legitimate beginnings. They should remain open to revision as real people use the system, challenge assumptions, expose gaps and clarify what the Commons needs to become.