Rongo Language Standard · Version 0.1 · April 2026

Language can be
disciplined
without claiming neutrality.

The Rongo Register is built on a simple premise: if people are going to make decisions using shared terms, those terms should be described in a way that others can understand, question, and build on. This standard exists to hold us to that.

"If a term in the Register feels too certain, too simplified, or too narrow — that may indicate either a limitation in the system, or an opportunity to improve it."
Why this exists

Every system that describes the world carries assumptions. The Rongo Register is no different. Left unchecked, those assumptions become invisible — and invisible assumptions are the very thing we exist to surface.

This standard is not a guarantee of objectivity. It is a public commitment to intent — and a framework for course correction when we drift from it. We are publishing it from the beginning so that anyone can hold us to it.

Language is never neutral. But it can be disciplined. The following principles describe how we try to apply that discipline — to the terms we record, the layers we add, and the words we use to describe both.

The aim is not to remove perspective — but to allow different perspectives to engage with the same term without first having to resolve disagreement.

This standard applies to contributors, to the tools we use to build the Register, and to Rongo itself.

Eight working principles
Rongo Language Standard · v0.1
01
Describe before interpreting
We separate what a term contains from what it means to someone. Both may be valid. They are not the same thing.
"Diesel stockholding includes…" → description
"This is insufficient" → interpretation
02
Avoid absolutes unless verifiable
Words like always, never, must, and proves are used sparingly. If a statement cannot be consistently demonstrated across contexts, it is framed accordingly.
03
Prefer framing over assertion
Rather than stating what is wrong, we describe what is present, absent, or assumed. This allows others to engage without being forced into agreement or disagreement.
"This measure does not include…"
rather than "This is wrong"
04
Make boundaries visible
Every term has edges. Where possible, we clarify what is included, what is excluded, and where assumptions are made. A clear boundary is more useful than a confident statement.
05
Separate design from performance
We distinguish between what a system was designed to do and how it performs in reality. These are often conflated. They are not the same question.
06
Avoid prescriptive or directional language
The Register is not an advocacy platform. Terms are described in a way that allows multiple perspectives to engage with the same definition without being steered toward a conclusion.
07
Allow incompleteness
Not every term will be fully defined. Gaps may be noted, partially described, or left open. Completeness is not required for a term to be useful.
08
Accept and correct drift
This standard is a direction, not a guarantee. If language in the Register becomes too absolute, too interpretive, or too narrow — it should be revised. That is not failure. That is the system working.
"We are not claiming objectivity. We are claiming intent, visible discipline, and willingness to correct."

This standard will evolve as new domains are added, new contributors engage, and edge cases are encountered. Version numbers reflect that evolution — not instability, but honest development.

If you encounter a term in the Register that feels too certain, too simplified, or too narrow — that is either a limitation worth naming, or an opportunity to improve the record. We welcome both.

Rongo Language Standard v0.1 · Published April 2026
rongo.co.nz/register/language-standard