A proposed American initiative
Project Democracy
A way for anyone to send an idea to the government, and a route for the good ones to actually become law.
Almost anyone in America can already call a congressional office and share an idea. When the idea is strong, staff usually pass it along. That first step works. What fails is everything after: most good ideas never get drafted, scored, or scheduled. This proposal is about that second step.
What Project Democracy is
One missing step between a good idea and a law.
Build an app where a resident can describe a problem, propose a fix, and send it to the office that handles it. Staff see the strongest submissions first. If an idea holds up, it gets drafted and moved.
That is the whole design. The government ends up with better ideas than any single office could generate on its own, and the person who sent one finds out what happened to it.
Why it matters
Democracy is a pipeline for public ideas. The pipeline leaks.
A functioning democracy needs three things to be true at once:
People believe their input reaches someone who can act on it.
It actually does reach someone who acts on it.
The government has a reason to want the outcome, which in a democracy means votes.
This proposal pushes on all three at the same time.
The problem
The first half works. The second half does not.
Constituents can already reach nearly every member of Congress, and staff are usually willing to take the call. Ideas move from an office to a paper bag in a hearing room. Then they stall.
A constituent has an idea. It reaches a staffer.
The idea reaches Congress. Nothing is scheduled.
If I can call Congress at any time and nothing happens, then I do not have a voice. Nobody does.
The solution
A coalition with a shared intake.
Members of the House and Senate, plus the administration, agree to receive vetted proposals through one channel. Each office names a staff contact. The project sends ideas that clear review to those contacts, then helps move them through committee, the floor, and the White House.
Signing on does not commit anyone to a vote. It commits them to reading good ideas early, while there is still time to shape them.
What changes
Four practical effects
Anyone can propose a fix
Constituents already know which problems are real. This gives them a route that ends somewhere.
More people become specialists
A public route into policy work pulls in people who would never otherwise write a memo.
Solvable problems get solved
Options that already work stop waiting for a champion who happens to hear about them.
Trust goes up
People can see what happened to their submission. That alone changes how the institution feels.
The case against it is thin.
The real objection is workload. Congressional offices are small and already overloaded. Automated triage handles most of that: duplicates are merged, weak submissions are filtered, and staff see a short list instead of an inbox.
If a problem has a workable solution, the default should be to use it.
What it does for democracy
It makes the promise literal.
Most people experience democracy as a vote every few years. This turns it into a standing channel: write something, send it, watch it move or fail in public.
That is a smaller claim than "save democracy," and a more useful one. People who can see their own input in the system are more likely to defend the system.
The proposed process
From an idea to a committee calendar
Five steps, using tools that already exist on this site. Each one has a named owner and a visible status.
A member never gives anything up by joining. If they dislike a proposal, they say so and the submitter has to answer.
Step 1
Submit an idea or a bill
Anyone can use the Bill Builder and the idea tools to send a proposal, a draft, or a problem description. A rough note is enough to start.
Step 1
Submit an idea or a bill
Anyone can use the Bill Builder and the idea tools to send a proposal, a draft, or a problem description. A rough note is enough to start.
Step 2
Research and revision
The submission gets checked against existing research and known objections. Weak claims are flagged, the argument is tightened, and the author has to answer the obvious counterarguments before it moves.
Step 3
Project review
A proposal that survives revision is marked ready and sent to the staff contacts in participating offices, with a one-page summary and the supporting material attached.
Step 4
Staff response
Staff can accept, object, or ask for changes. An objection is written and answered. The exchange continues until the idea is accepted, rejected on stated grounds, or revised.
Step 5
Legislative consideration
Accepted proposals move through committee, the House, the Senate, and the White House on the normal calendar. Amendments are expected. Nothing is guaranteed.
Revision path
Sent back or declined
Any stage can return a proposal for revision or end it. The process is meant to surface disagreement early, not to promise enactment.
Public participation
Democracy is a way of collecting good ideas
The institution mostly does this through elections, which is a very slow filter. This project adds a continuous one: a place to send an idea, a review process that separates the workable from the wishful, and a staff contact at the other end.
The problem pages already hold research on AI risk, pandemics, factory farming, poverty, cybersecurity, and governance. This initiative is the route from that research into an office.
Anyone can propose a fix
A resident can send an idea to the office that handles it. That is a small sentence with large consequences.
Solvable problems get solved
Options that already work stop waiting for a champion who happens to hear about them at the right moment.
More people become specialists
When submission leads somewhere, people put real work into it. Some of them become the experts offices call later.
A government people can see
Every submission gets a status. Watching an idea move, or fail, is a different experience from wondering.
An example
A researcher who has spent years on pandemic preparedness drafts a proposal in the Bill Builder. It goes through structured review, gets rewritten where the argument is weak, and if it clears the project's threshold it lands with staff in participating offices. That is the intended path. It is a proposal, not a description of something running today.
The coalition
Enough members to move a good bill
The goal is a working bloc in the House and Senate, plus an administration willing to sign. That is what turns a good proposal into a hearing, then a markup, then a vote.
This is a plan. No members have signed on yet, and nothing here describes current operations.
House members
Each participating member names a staff contact. That contact receives verified proposals and decides which ones are worth drafting. The member is never asked to vote on anything they have not read.
Senate members
Same arrangement in the Senate. One staff email per office, a short queue of vetted ideas, and no obligation beyond considering them.
The administration
Presidential involvement is the hardest part to win and the part that makes the rest work. The argument to an administration is straightforward: this is a visible, low-cost way to show that government responds to people.
Designated staff contacts
One person per office. They receive new proposals, can push back in writing, and are the difference between a website and a working channel.
Joining gives nothing away
A member never has to vote for a bill they dislike. If they object, they say why in writing, and the submitter has to answer. That exchange either produces a better draft or settles the question. Either outcome is more useful than another unread email.
Open questions
What we have not settled
A proposal that hides its weak points is not worth reading. Here are ours.
Software sorts, people decide
Submission tools help rewrite weak arguments and check claims. They can rank a queue. They cannot schedule a markup. Every decision that matters stays with staff and members.
Disagreement gets a procedure
An objection is written down and answered. The exchange runs until the idea is accepted, rejected on stated grounds, or revised into something both sides can defend.
Most ideas will not advance
The review exists to filter, not to validate effort. Expect a high decline rate. Criteria and staff workload are still being designed.
Partisan bills are unresolved
A bipartisan coalition cannot spend its credibility on one party's messaging bill. Where that line sits is an open question, and we have not answered it yet.
Clearing review is not the same as becoming law
A proposal still goes through committee, floor scheduling, the other chamber, and the White House. Amendments are normal, and any stage can kill it. The coalition shortens the distance to a committee room. It does not replace the process. The Congress.gov overview is the plainest explanation of what happens next.
Elsewhere on the site
Seven places to go next
Join the coalition
A sign-up for congressional offices, administration staff, and outside collaborators who want to work on this.
Team members
The current list: House and Senate offices, administration contacts, and the researchers and writers helping outside government.
How to solve the world's biggest problems
The working method behind the site: how to scope a problem, find what already works, and turn it into language an office can use.
How ideas are evaluated
The rules we use to decide what to work on, how to judge whether a bill does more good than harm, and when to walk away.
All ideas
The full collection, searchable by problem area: AI risk, global health, poverty, governance, factory farming, cybersecurity.
Bill Builder
Draft and revise legislative text, with research support and version history. Bills can be submitted for review from here.
Idea Workshop
Prompts for turning a half-formed thought into something specific enough to submit. Useful before you have a draft.