# 08 — Neutrality charter

**Status:** draft for the steward's review **[PROVISIONAL]**

Shared infrastructure for competitors works only if none of them owns it. A trade platform owned by one participant with a commercial motive failed largely because rivals would not feed it. Universal Paper is designed to avoid that from the first version.

## 1. No one owns the language

Universal Paper is a language, like a unit of measure or a bookkeeping method. No party owns it. Uppercentile created it and offers it to everyone for free. The specification is published under CC BY 4.0, the reference code under Apache-2.0, and the example agreements under CC0 1.0. Anyone may use, implement, extend, or fork either, for any purpose, without permission or payment.

## 2. The core carries no commercial interest

- The core defines no prices, fees, rates, thresholds, or other economic terms, and recommends none ([A6](03-axioms.md)).
- The core does not favor any segment. Rules are written in terms of Roles, never parties ([A7](03-axioms.md)), and Term renderings read the same whichever party reads them.
- The core depends on no product, service, network, ledger, or company. An agreement can be verified with this document and standard cryptography alone.
- No part of the core may require payment, an account, or a license key, or route data to any particular party.

## 3. The steward discloses its affiliations

The steward maintains the specification on behalf of everyone who uses it. The steward is a steward, not an owner.

- The steward publishes, and keeps current, a statement of its commercial affiliations with any GPO, supplier, member, distributor, or technology vendor, and of any product it offers that builds on Universal Paper.
- Anyone who proposes or reviews a change discloses affiliations relevant to that change.
- Current steward: **Uppercentile**, which created Universal Paper and publishes the specification. Affiliation statement: *to be published by the steward.*

## 4. Changes go through a public, versioned process

- Every published version of the spec is immutable and identified by its version string. Agreements pin one version ([A1](03-axioms.md)), so a later change never alters an existing agreement's meaning.
- Changes are proposed as public, numbered requests for comment (RFCs), open to anyone. Each RFC states the problem, the change, its effect on existing agreements, and the proposer's affiliations.
- Each RFC has a public comment period before a decision. Decisions and their reasons are recorded.
- A public changelog lists every change in every version.
- Term definitions record their drafters, reviewers by segment, and version history ([01-domain §6.1](01-domain.md#61-term-definition)). A Term should be reviewed by counsel from more than one segment (aggregator, supplier, member) before it is marked stable.

**[PROVISIONAL]** This process is the default assumption in the brief (open question 3). Comment periods, decision rules, and who decides are not yet defined.

## 5. A path to a neutral body

Stewardship by a single company is a starting point, not an end state. The steward commits to transfer stewardship of the specification, its version history, and its RFC record to a neutral body (for example, a foundation or standards organization with members from more than one segment) when the language has users across segments. The steward will not hold rights that would prevent that transfer. **[PROVISIONAL: trigger conditions and candidate bodies to be defined]**

## 6. What this charter does not cover

Products, services, and networks built on Universal Paper, including any offered by the steward, are separate from the language. They are free to be commercial. They may not claim to be the language, or to be required to use it.
