Using and Adopting Values Commons

Use this when someone asks, "What can I do with Values Commons?" Start with the real decision in front of them, then choose the smallest useful next step.

Choose a Starting Point

Start at Values Commons unless the person already has an everyday decision. In that case, send them straight to Conscious Consuming or the relevant app.

The First Conversation

Use these four questions before recommending a next action:

1. What decision are you trying to make or help others make?
2. Is this one person choosing, or a group trying to act together?
3. Do the facts already exist, or does a facts file need to be built or corrected?
4. What must remain under the people's control: their values, the evidence, the group decision, or all three?

If the answer is fuzzy, start with the tour. If the answer names a domain, start with instances. If the answer names a group, start with Assembly.

What to Record

After someone tries it, record a short set of notes. Use the preview feedback plan if you are inviting several testers or preparing a grant preview.

Do not turn every reaction into a plan. Act on feedback that is specific, reproducible, and tied to a real attempt.

Individual Use

For a person trying to make a choice:

1. Open a live instance from Instances.
2. Weigh values until the ranking feels honestly theirs.
3. Inspect the evidence behind the top and bottom results.
4. Export or copy the Values Passport if they want the same values to travel.
5. If a fact looks wrong, route it to Workshop or Contribute.

Success means the person can explain why the result changed when their values changed. It does not require them to agree with a universal ranking.

Group Use

For a group trying to choose together:

1. Have each person create or bring a Values Passport.
2. Merge the passports in Assembly.
3. Name where there is alignment and where dissent remains.
4. Correct or copy the relevant facts file in Workshop if the evidence is disputed.
5. Use Slate to turn shared values and facts into an action list with reasons.

Success means the group can see the reasons behind the decision and where people still disagree. Do not fake unanimity to make the outcome cleaner.

New Subject Brief

For a community that wants a new domain front door, write this before building:

Use Create an app after the brief is clear.

What to Avoid

• Do not start by adding features. Start by naming a decision.
• Do not collect accounts just to learn whether the idea works.
• Do not claim a facts file is neutral. Say whose values and which evidence are being used.
• Do not bury dissent in a group decision.
• Do not treat the optional Community layer as the core. The core is files and browser code.
• Do not launch a new instance until the contribution route is visible.

Minimum Launch Checklist

• The page says what decision it helps with.
• The values that transfer from a passport are named.
• The lens has enough recognizable options to test the domain honestly.
• Every contested score has a source or is clearly marked as illustrative.
• The instance links back to Values Commons, Passport, Workshop, and Contribute.
• A person can export, fork, or challenge the relevant files.
• The trust boundary is intact: no account, no tracking, no ads, no pay-to-rank.
• Tester notes can be written without creating an account or exposing private values.

Useful URLs

This guide works when someone can choose a next step without needing a founder, platform account, or private explanation.