DemocracyOS

The bet

DemocracyOS launched in Buenos Aires in 2012 as open-source software with a clean premise. Citizens would read, debate and vote on the actual bills before their legislature, one initiative at a time.

Pía Mancini and Santiago Siri understood from the start that software alone would change nothing. Legislators, the people with the power to act, had no reason to care what an app concluded. So in the same month the founders started a political party, the Partido de la Red, whose candidates pledged to vote in the legislature exactly as DemocracyOS users decided. If the institutions would not adopt the platform, the platform would win the institutions. It was an audacious plan, and an honest one.

Peak

For a moment it looked possible. The Net Party registered with the required signatures and drew around 22,000 votes in the 2013 Buenos Aires city election. In 2014 the platform ran a pilot that opened all 350 bills before the city legislature for debate on DemocracyOS. Its users backed a reform improving working conditions for nurses, and the measure passed even though the sponsoring party was a minor one.

Mancini's TED talk carried the idea around the world, and forks of the software appeared in other countries. Briefly, it was the most talked-about experiment in digital democracy.

What worked

DemocracyOS focused on real legislation, not vague consultation. The tool was elegant, open-source and reusable, and the 2014 pilot showed the concept working inside an actual legislature.

The diagnosis was right too. The founders refused to pretend that citizen votes would matter on their own, and built a party to try to guarantee that they would. That kind of honesty about where power sits is rare, and it is why the project still repays study.

What failed — the mechanism

DemocracyOS needed the side with power to show up and be bound by the result. That side never did.

Voluntary adoption by officials never went past a pilot, so most votes on the platform had no binding force. The Net Party was the plan to fix that by becoming the responsive side itself. It won only about one percent in 2013, short of the threshold for a seat, and never captured the power it needed to close the loop.

With neither voluntary adoption nor won seats, citizen participation piled up on one side of an open circuit. The project drifted into dormancy while its organization moved on to other work. The software was never the problem. The side with power was.

What Agora takes from it

DemocracyOS states the supply-side problem more clearly than any other case. A participation platform is worth nothing until the side with power shows up to respond, and no one can assume it will.

Agora's answer is not to run for office. It seeds the official side from day one, aggregating officials' public records automatically so the platform carries substance before any official lifts a finger, and it anchors participation to that substance. DemocracyOS also shows why a reliably responsive connection to power is the whole game. That is why Agora is designed to give citizen input a path to acknowledgment and follow-through, though it cannot make an official respond.