Written by Yux Seow, Cultural Research and Development Lead
Recently, in a room of Traditional Owner organisations, Winyama’s Managing Director, Andrew Dowding, made a claim that left the room quiet: whatever legacy is left in the management of cultural heritage, it will be the legacy of culture, not of technology.
Between that claim and a working system there are a few steps. Culture doesn't reach a system on its own. It reaches it through governance, through decisions about who can see and use what, made by the people with the cultural authority to decide. Governance is what makes continuity possible, across staff, across platforms, across generations.
This story gets told two ways. The first is the cautionary tale: the system built the wrong way, the risk, the data migration that turns into a crisis. Those stories are real, and we have told them ourselves. They also leave communities exactly where the first essay in this series argued they should not be, cast as people with something to defend rather than people with the power to build. This is the other version.
The philosopher Jonathan Lear describes radical hope as hope "directed toward a future goodness that transcends the current ability to understand what it is." Not optimism, which expects good things to happen. Something harder, and more useful: acting now on behalf of a good we cannot yet specify. It is a practice rather than a sentiment, which means it has to be resourced like one.
Data governance done well is radical hope in practice. Imagine the version that goes right: one system built the way it ought to be, from the day it is commissioned to the day the great-grandchildren of the people who built it are using it. The technology may be replaced several times over. By the end, we will be standing a century away from a scoping meeting, looking back at the few weeks in which all of it was decided, by people who never saw what it became.
At the start, the question is referred to cultural authority
An organisation gets funding for a cultural mapping project. The scoping conversation covers storage, licences, field apps, and training days. Somewhere in it, someone asks who should be able to see the restricted material. It is the most important question in the project, and the people who can answer it are not in the room, because scoping meetings are for technical requirements.
So the organisation does the thing that feels, at the time, like a setback. It stops. The question goes where it belongs, to the people who hold the cultural authority to decide it, while the build waits. This is the decision the whole system rests on. It doesn’t look like a technical achievement - it looks like delay.
A few months in, the decision reaches the software
Now that there is an answer to that question, the system being built can express it rather than invent one. What that looks like seems unremarkable. Material that shouldn't be held isn't collected, so there is no field for it, nothing to leak, and nothing for a future administrator to switch on by accident. Restricted material sits in its own store rather than behind a checkbox on a shared one, so neither a mistake nor an imperfect migration can expose it. Records carry their own terms in their metadata: which protocols apply, and who holds the authority to decide. None of that is difficult. It is only possible because the decision already existed.
Three years on, the reasoning is still there
People move on. The person who set up the system leaves. What doesn't leave with them is the governance. A new coordinator can look at a restricted layer and find out why it is restricted, who said so, and who to ask if the protocol needs to change. The difference between a restriction that came from an Elder's instruction and one that came from a permissions screen is legible, because it was recorded when it was made. That sounds like an administrative detail. It is the difference between an organisation that can answer questions about its own holdings and one that has to guess.
Thirty years on, the platform changes but nothing important does
The vendor is acquired, new technology emerges, the licence increases, or the version stops being supported. The organisation makes a decision to migrate. It is tedious but it is not a crisis. The questions the migration raises are technical ones: formats, field mapping, testing. Nobody has to work out who can see what all over again, under time pressure, with a decommissioning date approaching. The governance has now outlived its first platform, which is the first real evidence it was the foundation.
Two generations on, it is simply how things are done
The young people who weren't born when the system was commissioned are now running it. They did not inherit a mystery. They inherited governance that works, and they can change it, because they can see what the decisions were and who made them. Meanwhile the material has been accumulating. The same stretches of Country, observed year after year. Records repatriated from university archives, government departments, and consultants' hard drives, brought back and held under protocols the community set.
Three and four generations on
This is the part that is hard to picture and worth trying.
What that Aboriginal organisation holds is something almost nobody else in the country has: a continuous, governed record of Country, made by the people responsible for it, across a century. Not a survey commissioned for one project and filed when it ended, but a record with no gap in it.
Records like that answer questions nobody thought to ask when they were made. Someone will want to know how a creek line behaved before a change that hasn't happened yet, or what was growing where, or when a soak last filled reliably. A single year of monitoring is a fact. Ten years of it is a baseline, and a baseline is what lets an organisation say what has changed, by how much, and since when.
The protocols will still be there too, revised many times over, by people with the cultural authority to do so, but never restarted. This is Indigenous Data Sovereignty exercised across generations. The records accumulate one at a time. Authority compounds.
What the legacy actually is
Platforms have a limited working life. Governance, and the people who hold authority under it, run on a different timescale entirely.
So the thing being built in that first scoping meeting is not actually the system. It is the governance, and the system is where it happens to be expressed in this decade. Andrew closed his presentation by saying: we won't bend culture to fit technology, we'll bend technology to fit the oldest living culture on Earth.
Which makes this a familiar kind of work. Deciding carefully now, on behalf of people you will not meet, is not a data governance innovation. It is the oldest practice there is, and it is what radical hope looks like when it's practised. What future generations inherit is decided by what gets governed now.
