A group should be able to learn from what its decisions actually do. WebTree’s earlier term for exploring outcome-accountable governance is Responsible Democracy.
This remains a research hypothesis. WebTree does not claim to have solved democratic governance or to operate a proven contribution-weighted voting system.
The hypothesis
Recording a decision, its reasons, expected outcomes, alternatives, and supporters may make later review more useful. Over time, a decision history could inform governance credibility.
That does not mean a contribution score should automatically determine voting rights.
What makes the question difficult?
Outcomes depend on luck, external events, delayed effects, and decisions made by others. Responsible risks can fail. Popular choices can harm minorities. A powerful group can choose the evaluation rules that keep itself powerful.
A useful design needs ways to disagree, contest evidence, protect rights, and avoid making livelihood or essential access depend on political alignment.
Rules can change; the record must retain context
Keep the rule and evaluation that applied at the time, then add a current interpretation and explain the difference. An updated view should not silently rewrite settled compensation or pretend an old decision never happened.
Forking and its limits
Participants may create an alternative project or rule set from an earlier state. Contracts, money, machines, private data, and branding do not automatically travel with a fork. Exit only helps if the practical boundaries are clear.
A useful next test
Start with decision records and scheduled outcome reviews in a small consenting group. Compare their usefulness with ordinary meeting notes. Examine whether forecasts improve and dissent stays visible.
Do not begin by algorithmically removing voting rights. Credibility-weighting would require separate evidence, agreement, and protections.
Read the earlier model in historical context.
Status and revision
This is a concept note, not a reported experiment result. Maintained by the WebTree project team, led by Max Levitskiy. Initial public synthesis: 5 September 2026. Future revisions should state what changed and why.