We debug democracy.
DESH stands for Democratically Elected System Hackers. Right now it is a lab: open to anyone who clears the core reading, working in the open, arguing about mechanisms. A party is where it is headed, and the lab is what has to exist first. We treat governing as a system to be engineered rather than a stage to perform on. India is the first test bed, and nothing in the design depends on India.
Experts on the controls
Put the people who run a system in charge of the rules for that system. A career in politics teaches you how to win office, which is a real skill and an unrelated one. The person deciding how aircraft get certified has usually never certified anything, and the cost of that learning curve is carried by everybody else.
Engineering discipline
Software teams did not get reliable by hiring better people. They got there on unglamorous habits: write the change down, have someone who knows the area read it, try it somewhere small, keep the ability to undo it. Almost none of that survives contact with a legislature, and there is no good reason for that.
100 founders
A hundred is the legal threshold to register a party in India. We would rather fill it with people who have spent a decade inside aviation, health, defence, finance or infrastructure than with people who have spent a decade near politics. The first hundred set the bar for everyone who comes after.
A technocratic democracy
Democratic in who decides, technocratic in what counts as an argument. Evidence and measured outcomes over rhetoric and electoral arithmetic. Not left, not right. Forward. See the vision →
Politics runs on legacy code. It works, roughly. Nobody still around knows why it works. And there is no way to roll back a bad release.
Open by default, not on request
The RTI Act made opacity expensive by putting a statutory clock on it, and that has been worth more than any speech about honesty. The next version shouldn't wait for the application. Decisions, votes and money get published as they happen, because a record you have to ask for is a record someone can lose.
Small releases, fast reverts
A policy that reaches everyone on day one cannot be wrong safely. Run it in a few districts, measure the thing you said you would measure, keep the undo wired up. The goal is not speed. The goal is that being wrong stops being catastrophic.
Anyone can send a patch
Open source is a permission structure, not a mood: anyone may propose a change, and people who know the area decide on it in public. Parties are the exact inverse of that. This one works like a repository, with the arguments and the rejections visible too.
You already know what's broken in your field.
Everyone we talk to can name the three things wrong with their domain and the reason none of them get fixed. That knowledge is the scarce input here.
Join the System Hackers →