On-screen

Narration

Anna: When we say "open" in tech circles, people assume GitHub repos and creative commons everything. But for Indigenous communities, openness is negotiated, relational and grounded in tikanga. Our goal here is to show how you can invite collaboration without handing over guardianship of taonga.
Greg: Right, and it’s not just an ethical stance—it’s a strategic one. Communities want to drive impact from language archives, climate data or health studies, yet they’ve seen extractive research hollow trust. Balancing openness with cultural safety means designing processes that answer "who benefits?" and "who decides?" before a single CSV is shared.

On-screen

Narration

Anna: The tension we manage focuses attention on a concrete part of the work. Communities want visibility for their stories, research wants data, and platforms default to "public", Cultural safety requires respecting protocols, whakapapa and the right to say "not now", and Openness is a spectrum: open to whom, for what purpose, and under whose authority?.
Greg: In practice, ask who owns the work, what evidence proves it happened, and what handoff comes next. Use the supporting details as a checklist: Cultural safety requires respecting protocols, whakapapa and the right to say "not now"; Openness is a spectrum: open to whom, for what purpose, and under whose authority?; Treat each dataset as taonga first, asset second.

On-screen

Narration

Anna: Frameworks like CARE and OCAP® give teams language to operationalise sovereignty. They flip the script from FAIR’s "make everything findable" to "how does this data deliver collective benefit, and who retains authority to say no?"
Greg: Exactly. When you cite UNDRIP Articles 18 and 31 in an agreement, you’re grounding decisions in international law that recognises cultural expressions as living knowledge. That empowers community tech-leads to slow down eager researchers and convene hui before any export happens.

On-screen

Narration

Anna: Consent isn’t a one-off signature; it’s an ongoing conversation. We’re recommending teams define sensitivity tiers so elders can differentiate between language-learning clips that can go to schools versus karakia that never leave the marae.
Greg: And document the stories behind the data. Provenance notes, cultural narratives and explicit usage boundaries travel with the dataset so future analysts understand the tikanga context. That’s how you avoid someone training a model on sacred audio because they only saw a file name.

On-screen

Narration

Anna: Tiered access strategies focuses attention on a concrete part of the work. Create membership-based portals with whānau-first access and layered researcher permissions, Use data sharing agreements that require reciprocity, cultural briefings and return of insights, and Establish community review boards that can veto or amend release plans.
Greg: In practice, ask who owns the work, what evidence proves it happened, and what handoff comes next. Use the supporting details as a checklist: Use data sharing agreements that require reciprocity, cultural briefings and return of insights; Establish community review boards that can veto or amend release plans; Schedule sunset reviews so sharing levels evolve with community comfort.

On-screen

Narration

Anna: Tiered portals and review boards are how you translate those principles into day-to-day decisions. Whānau get first access, then trusted researchers who have gone through cultural briefings and signed reciprocal data-sharing agreements.
Greg: Governance lives in the paperwork too—MOUs that spell out kaitiaki roles, dispute resolution and benefit-sharing. Add Traditional Knowledge labels so licences travel with files, and insist partner institutions appoint liaison staff accountable back to the tribal council.

On-screen

Narration

Anna: People sometimes assume cultural safety is just policy, but the tech stack matters. Attribute-based access control lets you honour roles and protocols, and audit logs show exactly who downloaded which clip and when.
Greg: Pair that with encryption keys controlled by community stewards and monitoring for unusual usage. If someone suddenly scrapes thousands of files, alerts fire and the licence can be paused while you convene a restorative hui. Technology becomes a guardian alongside people.

On-screen

Narration

Anna: The roles slide shows this isn’t a solo act. You need cultural advisors sitting with engineers, and data stewards who can translate tikanga into access policies. Typically it’s one cultural lead per squad and a steward overseeing three to five partnerships.
Greg: Career-wise, we’re seeing interns from iwi digital hubs grow into community tech-leads, while policy analysts pivot into Chief Data Steward roles. The common traits are relational intelligence, patience and the ability to negotiate between community expectations and platform roadmaps.

On-screen

Narration

Anna: The scenario is intentionally practical. A university wants to add iwi audio to an open corpus, but they first have to produce a CARE-aligned impact statement and show how whānau benefit. Access is time-bound and requires reporting back in te reo Māori.
Greg: And there’s accountability—breaches trigger suspension, a restorative hui and potentially pulling derivative models. That’s the message: openness isn’t the absence of control, it’s shared responsibility with cultural governance setting the guardrails.

On-screen

Narration

Anna: The key takeaway is this: Openness can honour Indigenous sovereignty when cultural governance sets the terms of sharing.
Greg: Use that takeaway to name the owner, evidence, and next action that should be visible after the work is done.