Community defines the purpose
No project begins with a model. It begins with a collectively recognized need and people with standing to define it.
A proposed governance & learning layer
Infrastructure can be local.
Authority must travel through it.
An independent sketch of a community-owned way to carry purpose, authority, knowledge boundaries, accountability, and the right to refuse through the life of an AI system—read against Purple Maiʻa’s public work, and shown to no one there.
PurposeAuthority
KnowledgeControl
Use case
under review
under review
Unsolicited independent analysis. Not Purple Maiʻa policy, and not requested by them.Written from public material alone; Purple Maiʻa has not been contacted, has not seen this, and has agreed to nothing. Were any of it ever taken up, Purple Maiʻa and the relevant community and cultural authorities would define the substance. This prototype only demonstrates a possible structure.
The opportunity
The stack already has a technical body. This is a possible way to give its decisions a durable form.
Purple Maiʻa’s public work describes local compute, open models, edge hardware, place-based environmental observation, and Indigenous approaches to technology. The open question this proposal explores is whether a reusable governance layer would help carry authority through those systems without reducing sovereignty to a checklist.
Publicly groundedPurple Maiʻa’s published work on the Sovereign Stack, KILO, Kānāwai, Kula, Waiw.AI, and Rooted Futures.
Proposed by RNThe decision gate, system record, pilot sequence, governance roles, and learning translations shown here.
Not yet knownWhether this solves a real constraint, who should govern it, whether KILO is the right pilot, and what may be documented.
Not everything becomes data
The process must make room for knowledge that is restricted, contextual, ephemeral, seasonal, sacred, or never appropriate to digitize.
Refusal is an operating capability
A sovereign process can approve, limit, redesign, defer, contest, withdraw, or refuse. “No” is not a technical failure.
Designed under authority, never in place of it.
RN’s proposed role is governance and legal-technical translation: listening, mapping, documenting, prototyping, testing, and transferring the implementation. RN would not define Hawaiian values, decide who speaks for a community, validate kānāwai, or authorize a use of knowledge or data.