ParlamentPlattform
Sign in Become a member

International partners

The laboratory of democracies — the invitation to the kindred movements worldwide (§ 12 of the draft statutes).

Shared vision Version 0.1 · draft

We have no party programme to reconcile. We have a vision that we make concrete together.

Citizens decide for themselves. A party of this kind carries no opinions, it is the tool with which a society takes, traces and implements its own decisions — the logically next form of society-wide self-organisation.

Verifiable instead of trust-dependent. Every procedure can be recalculated by anyone without special knowledge; rules freeze when a motion is submitted; nothing is ranked in secret; nothing concerning a procedure is ever deleted. Those affected and those with expertise come first. Technology proposes, it never decides. Representatives implement — bound, reporting openly, steered by the members.

One core, many instances. Each country runs the same base software on its own servers, under its own statutes, in its own language — and learns there. We develop the core together, with regular exchange and alignment. Parameters are introduced jointly, their values stay each country's own. Aligning instead of reconciling: as we have no programmes, there is nothing to negotiate but the vision itself — version by version, in the platform council with one vote per country. Connected by tool, schema and vision, not by money.

Full text in both languages: GEMEINSAME_VISION.md (in the package below and in the source code).

One core, many instances

One shared core, one instance per country; between them the parameter schema as a bridge Shared core Source code · releases · schema versioned release Learning progress Parameter schema · parameter.json · kennzahlen.json Austria at-ddoe own servers · own statutes · learns for itself Country B xx-partei own servers · own statutes · learns for itself Country C yy-partei own servers · own statutes · learns for itself

Core and instances. The shared core is the ParlamentPlattform repository: source code, versioned releases, the schema. From it each country runs its own instance — its own database on its own servers, its own parameter register, its own category tree, its own statutes. What is country-specific lives in configuration and data, not in the code.

Alignment. Every quarter the core issues a release; the instances pull it in. Extensions made by one country enter the core if they can be parameterised — otherwise they stay a documented module of that instance. A platform council with one person per country decides on the releases; the minutes are public.

Parameters jointly, effect your own. New settings arise in the core with a language-neutral key and a recommendation. Each instance sets its value itself and keeps learning it in its own register — so the same parameter works in each country in that country's own way.

Learning progress. What one country learns about deadlines, thresholds or turnout becomes comparable through the interface — aggregated, never personal. It is compared; adopting it takes a decision of your own assembly.

The interface

Only what means the same everywhere is exchanged: settings with language-neutral keys and aggregated metrics. Values stay each country's own; personal data never leaves an instance. All addresses are public, without sign-in. Schema version 1.0.

AddressContentKeys (examples)
/parameter.jsonSettings and procedural rules of this instancesupport.threshold · deliberation.window_days · draft_loop.max_rounds
/kennzahlen.jsonAggregated learning progress: members, motions per phase, turnout, implementationmembers.active · votes.turnout_mean · implementation.by_status
/antrag/‹id›/export.jsonVerifiable count of a vote including the checking toolverify/nachrechnen.py
/umsetzung.jsonImplementation register with full history—
policies/*.yamlCategory tree (312 areas of life, language-neutral slugs) and procedural rules as datakategorien-v2.yaml · grundordnung-v1.yaml

Full description: docs/SCHEMA.md · ADR-009 · Id of this instance: at-ddoe

How to get started

Track A · transform an existing party

  1. Share the vision and decide internally: a tool, not a programme.
  2. Lay the statutes kit over your own statutes — adopt the core, work in national law.
  3. The members decide — on request already on an alpha instance, verifiably.
  4. Set up your own instance (checklist), move bodies into roles and representatives into representative steering.
  5. Publish the exports, take a seat in the platform council, first alignment.

Track B · found a new party

  1. A core group of five to ten people, agree on a working language.
  2. Fill in the statutes kit, have it reviewed legally in your own country.
  3. Foundation and registration under national law.
  4. Set up your own instance (checklist), run an alpha with first members and motions.
  5. Publish the exports, take a seat in the platform council, first alignment.

What we contribute: the software under a free licence with Docker and Render templates, the statutes kit with commentary and the Austrian legal review as experience, setting up the instance and the interfaces together, quarterly core releases and the platform council.

What your country does itself: servers and data in your own country, your own identity verification, statutes and procedural rules under your own law and in your own language, learning the values of the settings yourself — and returning honest metrics.

The transfer package

Everything in one file, generated from the current state of the source code — without any data of this instance:

  • GEMEINSAME_VISION.md
  • EINSTIEG.md
  • EINRICHTUNG.md
  • SATZUNG_BAUKASTEN.md
  • SCHEMA.md
  • instanz/docker-compose.yml
  • instanz/env.example
  • instanz/render.yaml
  • policies/kategorien-v2.yaml
  • README-PAKET.md
  • parameter-erstbestand.json
  • verfahrensordnung-aktiv.yaml

Most of these files are in German: the getting-started path and the setup guide carry an English summary, the statute construction kit and the schema do not yet. We will translate them with the first partner who needs them — tell us which file you need first.

Download the package (0.53.0) View the source code

The roadmap of cooperation

1 · Provide the software and set it up together
The ParlamentPlattform is fully open source (AGPL), bilingual and documented — including verifiable counting, a tamper-evident audit log, the council workshop and the parameter register. We help with setup and adaptation to your country.
2 · Shared standards and tools
An open standard for verifiable voting (export format plus independent checking tools), tool exchange under free licences, and a shared schema for participation metrics — honest comparison instead of marketing numbers.
3 · Gather learning progress and parameters together
The parameter register carries language-neutral schema identifiers: what Austria learns about deadlines and others about delegation or thresholds is exchanged in a structured way — a standing exchange of the platform maintainers, designed for decades.

What we bring — and what we seek

We bring: verifiable counting without a need for trust, rule freezing (ongoing procedures keep their rules), binding with a feedback channel (implementation register and execution reports), self-regulation without motions lapsing — statutes and software cast in one piece.

We seek: operational practice of bound mandates, campaign and reach experience, broad-listening tools and eID practice — the strengths of those who have already won elections or gathered decades of rulebook practice.

Let's talk. Short and concrete — with one offer and one learning question. Working language English or German.

Get in touch Download the package

In preparation: the partner account with its own role and interface on this platform — the role foundation for it is already in place.

Feedback
×

Give feedback

What is missing? What bothers you? What would you like?

You are writing anonymously — as a member, we could follow up. Privacy