Findings (3)
- The Hub hosts community-uploaded datasets and models, which in principle creates space for Indigenous-language and community-curated corpora (e.g., low-resource language datasets) to be published and gated by their stewards.
- Repository gating controls let owners manually review and approve access, a mechanism that could be repurposed to enforce community-controlled access to sensitive cultural data.
- The content policy frames 'Consent as Core Value', a hook that gestures toward — though does not name — relational consent over data.
Gaps (4)
- No mention of the CARE Principles for Indigenous Data Governance (Collective benefit, Authority to control, Responsibility, Ethics) anywhere in the audited surfaces.
- No acknowledgment of Indigenous data sovereignty, no consultation with Indigenous communities, no protocol for oral / non-textual / sacred-restricted knowledge.
- The platform's default posture is open-by-default and extractive-friendly: 'access & share datasets' with no sovereignty layer, which structurally privileges scraped over consented data.
- Gating is owner-controlled, not source-community-controlled — the uploader, not the originating people, holds the keys.
Justification
Mechanisms that *could* support Indigenous data sovereignty exist (gating, consent framing), but they are generic and owner-centric, not designed around CARE or community authority. The complete absence of CARE, sovereignty language, or consultation against a backdrop of 'share datasets for any ML task' keeps this low. Slightly above floor because the gating infrastructure is genuinely usable for restriction.