ROOT PROTOCOL
Manifesto
Why ROOT Protocol exists, and what it refuses to become.
- Version
- 0.1
- Status
- accepted
- Last updated
- Canonical language
- en · canonical
Most of what you do was learned before you could examine it. A family, a school, a feed, a fear, a reward: each one left an instruction. By the time you can ask why you are doing this, the instruction is already running.
ROOT Protocol starts in the gap that appears when you notice the instruction. Observation does not make you pure. It gives you a little room between stimulus and reaction. In that room, a change can be tested.
Reality before belief
We care more about what can be checked than about what feels profound. A useful idea has to survive contact with an ordinary Tuesday. If it only works inside a ceremony, it is not yet a protocol.
Metaphysical ideas are welcome as hypotheses. The thought that reality is a simulation, or that a coincidence means the universe is speaking, is not a finding. Those ideas stay labeled as speculative or uncertain until evidence moves them. Nobody here is authorized to promote a guess into a fact by charisma.
No sacred person
There is no guru, master, or prophet in this protocol. A founder can maintain the text. Maintenance is not infallibility. If the record is dishonest, or if a group starts demanding belief, the honest move is criticism or a fork. Forking is allowed. It is how an open protocol stays honest.
What development means
Development, here, is not a personality upgrade and not a rank. It is a gain in three plain capacities:
- You notice more of what is actually happening.
- You can choose a response instead of only repeating one.
- You can build something that other people can inspect.
The core cycle is the same every time: observe, debug, edit, execute, review. Skip the review and you have only a mood. Skip the observation and you have only a slogan.
An open text
This manifesto is version 0.1. It will be wrong in places. That is a reason to write the correction down, not a reason to defend the tone. The protocol is public. The arguments about it should be public too.
The public changelog lives with the source repository. Governance explains how a change is proposed.