Policy packets
The idea
A value system is a file. Files travel.
You can publish yours as a policy packet — into the movement's social network, where others can read, evaluate, and adopt it. And you can import somebody else's whose judgment you trust: it is cached locally under that author's name, and it is yours to edit from the moment it lands.
Why this matters more than it looks
Most people do not have time to reason through most questions. The usual solution is to defer to somebody — a party, a commentator, an institution — and that deference is invisible, unexamined, and total.
A policy packet makes the same act explicit and partial. You can see exactly which rules you adopted, from whom, and change any of them. Delegation stops being a habit and becomes a decision with a record.
What it is not
Not a vote. Importing somebody's packet does not give them your voice anywhere.
Not permanent. It is a copy. If the author revises theirs, yours does not silently change.
Not authority. A widely adopted packet carries no more weight in any calculation than one nobody imported. Popularity is not merit, and merit is not authority.
The identity boundary
Publishing requires a real identity. Everything else does not.
This is the charter's identity line, and it appears throughout the product for the same reason: reading and reasoning are private acts that should never require you to be anybody, but putting something into the public sphere under your name means having a name.
Note "real identity" here means a verified account, not legal-name disclosure. A pseudonymous citizen can publish, and can reach the top of the trust ladder.
Reading somebody else's packet well
Read the unless fields first. Anybody can list values. The exceptions show what they would
actually do under pressure.
Read the priority order. Where two of their rules would collide, the order is the answer.
Look for a rule you disagree with. If you cannot find one, either you have found somebody who thinks exactly as you do, or you are not reading carefully.