FAQ

I am a big open-source fan and think about opening the project up from time to time.

This is a question I get a lot, and it always makes me smile - because it shows the tech bubble we live in. We instantly expect software developers who can navigate GitHub to be the best reviewers for anything. Here, that is not the case. The best contributors to BudgetHole.com are people who know the federal budget and follow US politics closely. Those folks rarely know what a pull request is. But they use RitualDissent just fine.

Honestly, BudgetHole.com has felt "too small" for its own open-source repo so far: under the hood it is really a plain HTML page with a bit of vanilla JavaScript - no large architecture, no framework, no build step.

What currently plays the role of a public repo is RitualDissent.com - that small colored circle in the lower right corner of every page on desktop (it is hidden on mobile because the pin-and-mark UX does not work well on touch screens). One click activates feedback mode: you can mark any spot on the page and drop a comment or a concrete text suggestion right there. My AI harness reads that human-in-the-loop feedback stream several times a day, researches, evaluates the suggestions - and, once I sign off, ships them straight into the site. The net effect is very similar to a GitHub repo, at maybe 1% of the overhead on my end.

For the actual policy options in the simulator, every change has to be curated by hand anyway - categorized, sourced, documented (see the changelog) - so a classic PR review process would only get me so far.

Short answer: not right now. But the idea is on the radar - if the project keeps growing or several people want to collaborate long-term, I will open the repo.

First off: thanks for offering - that means a lot. Having people ask on their own how they can support a civic-education project is the best kind of tailwind.

Financially and time-wise I am doing fine with BudgetHole.com right now. The site runs on a tiny server, costs almost nothing, and curating the policy options is something I enjoy. Any form of donation button or sponsorship would just add administrative and disclosure overhead without a real need.

What actually helps:

• Test and report bugs. Click around, try combinations, test on phone and desktop. If anything is broken, unclear, or looks fishy, please tell me.
• Content suggestions. Missing a reform option that you saw in a study or a policy paper? Is a description misleading? A source stale? That kind of feedback goes right in too.
• Word of mouth. If you find the project useful, share it with people who care about fiscal policy or civic education - family, colleagues, students, your network.

Feedback flows best through the RitualDissent tool - the small colored circle in the lower right corner on desktop (it is hidden on mobile because the pin-and-mark UX does not work well on touch screens). One click activates feedback mode, then you can mark any passage and drop a suggestion or comment right there. I go through all messages several times a day.

So: the best support is a good message. Thanks for engaging with this.

Fastest path is inside the simulator: hit "Pick a category" in the top right and choose "Suggest a policy option" at the bottom of the menu. A small form opens where you can enter your proposal and its source. It lands in the same feedback queue as everything else and I review it.

For a proposal to have a shot at inclusion it needs to meet two conditions:

• Credible source. Concretely: published estimates from CBO, JCT, GAO, or the Congressional Research Service; scored bills; policy papers from think tanks (Brookings, AEI, CBPP, Tax Foundation, Penn Wharton, Yale Budget Lab, Tax Policy Center); or high-quality news reporting that cites one of the above with a real number. Opinions without a numbers basis do not qualify.
• Traceable scoring. The source has to quantify the fiscal effect - i.e. state how many billion dollars of extra revenue or extra spending the change causes per year for the federal government. Ideally with a visible derivation (base, rate, elasticity assumptions, behavioral responses), not just a free-floating number.

The reason for these two conditions: this simulator is not a wish list, it is a collection of vetted reform options with realistically estimated budget impact. That is the only way proposals from different political directions can be meaningfully combined and compared.

What happens after you submit: I read the proposal, check the source, place it in the right category (interactions with existing sliders, delta value), and - if it fits - build it into the simulator with a changelog entry. The full process is transparently logged in the changelog.

Plain bug reports or UX suggestions should not go through the proposal form - use the colored circle in the lower right corner (RitualDissent, desktop only). That keeps the two feedback channels cleanly separated.

Common question - and the answer is methodological, not political. Medicare for All is missing on purpose, even though there are serious scored proposals (Urban Institute, CBO working papers, Sanders campaign estimates).

The reason: magnitude and character. A fully universal single-payer system replaces roughly $2 trillion per year of private health spending with federal spending - gross federal cost around $30-40 trillion over 10 years, per Urban / CBO ballpark. In FY 2027 terms, that would roughly double federal outlays overnight.

That is not "a reform inside the existing federal budget", that is a fundamental system rebuild that only pencils out with equally fundamental tax changes (e.g., a payroll tax in the 10-15% range or a European-style VAT). Changes on that scale blow out the simulator's frame, which is deliberately built for incremental reforms - adjustments to individual items in the existing structure that stay meaningfully comparable with each other.

If Medicare for All were a single -$3T-per-year slider, every other reform option - raising the SS retirement age, corporate tax hikes, DoD budget cuts - would look visually meaningless next to it. And the outlays bar would swing so far that the scale breaks.

Short version: Medicare for All is its own political debate at its own scale. If you want to dig into the numbers, the Urban Institute's "From Incremental to Comprehensive Health Insurance Reform" is a good methodological entry point.

Same methodological reason as Medicare for All. A fully universal UBI of ~$12,000 per adult per year, net of replacing existing means-tested benefits, costs roughly $3-4 trillion per year (Roosevelt Institute, Tax Foundation, and CBPP estimates broadly agree on the order of magnitude).

That would nearly double federal outlays and would only pencil out with a fundamental tax overhaul (VAT, wealth tax, or dramatically higher income-tax rates). Not a reform inside the existing frame - it is a new frame.

The simulator sticks to incremental options that stay meaningfully comparable. UBI belongs in its own analysis at its own scale.