Explore the apps Catalogue Your values Kosplora Where to Message Workshop Adoption guide Build guide

Each app covers a different subject. The same values file and scoring engine work across all of them.

Use it in different subjects

Apps that can read the same values file

Each app has its own subject, facts, and language. They belong here only if your values can travel in and every claim can be checked.

Compare the live apps Build the next app Read the adoption guide Read the build guide

Live and illustrative

Three apps, same engine

Conscious Consuming is the real-data flagship. The other two show how the same engine can move into new subjects with only new facts and a new look.

Live data

Conscious Consuming

Everyday dollar decisions across sourced categories.

 Learning demo

Kosplora

A learning atlas with real routes: at every station, your values choose the resource.

 Messaging demo

Where to Message

A messenger choice tool for privacy, openness, reach, and practical adoption.

 Next app

Your subject

A nonprofit guide, local civic map, school resource list, buyer guide, or movement plan.

What every app shares

What stays shared, what changes

Each app should feel native to its subject without trapping people or changing the core. The portability test is simple: can a values file travel in, and can the facts be inspected or patched?

Shared engine Scoring, bands, values files, group combining, plan-building, and graph tools stay common.
Shared shell Ranking, sliders, verdict details, import/export, and the on-device flow stay reusable.
Local facts The subject chooses its options, criteria, source notes, and honest scope.
Local look The app can look and sound like its own world while keeping the same ethics.

How values carry over

Values travel where the subject can honestly express them

Each app maps broad values into local criteria through universalToLocal. A value that does not belong in the subject should be reported as not transferred, not smuggled into a fake score.

Universal vocabulary Planet, people, openness, access, wellbeing, autonomy, animals, community, quality, and joy.
Kosplora carries Openness, access, quality, joy, wellbeing, people, and community into learning-resource criteria.
Where to Message carries Autonomy, openness, access, community, and wellbeing into messaging criteria.
What stays home Unsupported values stay visible as not transferred, so the user can see the boundary instead of trusting a fiction.

Before a new app is public

What the next app needs before it is public

A new subject should feel independent, but it must still keep the commons promises: portable values, inspectable evidence, and no pay-to-rank.

Plain decision Name the real choice and who needs it.
Sourced facts Use sources for strong claims, dates for facts, and honest labels for judgements.
Visible path Link back to Values Commons, the values file, fact repair, and neighboring apps.
Values bridge State which universal values transfer into the local vocabulary.
Trust boundary Keep the core no-account, no-tracking, no-ads, no-pay-to-rank, and static-capable.
Clear corrections Show where to send a better source, missing option, or alternate facts file.

New subject brief

Write this before code

A clear decision and a small set of sourced facts matter more than a new interface. Write down who the app serves and which values truly belong in the comparison.

Decision What real choice should this app help someone rank or decide?
Audience Who needs it first, and what language would make the domain feel native to them?
Starter facts What 8-20 options and 3-7 criteria are enough to prove the subject?
Values bridge Which universal values transfer, and which should stay visibly not transferred?
Source floor What claims need citations before the app is trustworthy enough to share?
Contribution route Where do corrections, missing options, forks, and disputes go after launch?
Use the new-subject brief Use the full brief Plan contributions

Create one

Build from one facts file

Define the options and criteria, choose a look for the subject, then use the shared shell and engine. The app can remain fully static. Open the starter builder → to make and download the facts file and page.

lens.js + index.html skin + engine.js + shell.js

1. Name the decision. What choices should be ranked, and for whom?
2. Source the facts. Each assessed claim needs a reason, URL, and date.
3. Keep the values portable. Accept exported values instead of trapping users.
4. Publish static. A folder on a static host is enough for the core.
Read the implementation guide Start with the adoption guide Open the Lens Workshop