We're not building a party. We're building a system.
Seven rules for how Folket works. How you vote, what happens to your answer, and when a majority counts. The document is open.
The problem
You get to vote once every four years. You vote for an entire package — not on individual issues. Afterwards, you can't change anything.
Three things are wrong: it happens too rarely, it's too imprecise, and you can't withdraw your mandate.
Continuous answers
You vote continuously. A proposal opens, people respond, and the direction becomes visible immediately. You can change your answer as long as the proposal is open.
You vote when there's something to vote on — not just every four years.
Proposals and answers
Everything starts with a concrete proposal. It has a timeframe and a threshold for when the result counts. Your answer is your position on that one issue — for, against, or undecided.
You always respond to something specific. Never just into thin air.
Signal and mandate
When people respond, the answers become a signal — a visible distribution of for and against. When enough people have responded, and the threshold is reached, a mandate emerges.
Mandate isn't something someone claims to have. It's something everyone can see and verify.
Transparency
The rules are known in advance. The threshold for a mandate, the timeframe, and the format — everything is set before the vote opens. No one can change the rules while it's running.
If the system can't be explained, it can't earn trust. Everything must be visible and understandable.
Encryption
No one can see what you voted. Your answer is encrypted. But the overall result — how many voted for and against — is public.
One person, one answer per proposal. As little data as possible. The protection is built into the vote itself.
Scope
Folket is a layer between you and those who decide. It's not a party. Not a campaign. It's a way to make the public will visible — continuously and verifiable.
The system doesn't interpret. It shows what people think.