Governance

An RFC is a public proposal to change the protocol. This phase is read-only. There is no vote, no hidden committee, and no sacred author.

Principles

• Every accepted change should be readable later: who proposed it, what problem it answered, and what was rejected.
• Maintainer is a role of care, not a source of infallibility.
• If the public record is not enough, the protocol can be forked. Forking is a legitimate exit, not a betrayal.

Lifecycle

Draft, discussion, testing, voting, then accepted, rejected, or implemented. Voting is described here and is not open in this phase.

Example RFCs

• RFC-0001 · ACCEPTED

  Definition of Root State

  Root State names a temporary condition of clearer observation, not a permanent rank and not a mystical achievement.

• RFC-0002 · DISCUSSION

  Reality Access verification principles

  Claims about reality keep an explicit status. Verification is a record of evidence, not a blessing.

• RFC-0003 · ACCEPTED

  Multilingual translation governance

  English is the canonical language of the core documents. A translation can be verified without becoming a second original.