Let's talk about the real-world outcome of forcing code open. When government software is closed-source, the vendor is accountable. If a system's security breaks, there's one throat to choke. Open that code, and you get a mess of contributors, no clear owner, and a way for agencies to shrug off failures because the community can fix it. That sounds nice on paper, but it doesn't work when lives and tax dollars are on the line. Also, consider the cost. Mandating open source doesn't just mean sharing code. It means investing in documentation, user support, and security reviews for every project. That's not a free lunch, that's a new tax on the same budget. The public doesn't need to see every line of code. They need a system that works, is secure, and is delivered on time. Mandates don't guarantee any of that. They guarantee complexity.

The Heartbleed bug sat undetected in open source code for two years while half the internet used it. That's the reality when we romanticise open mandates. My opponent spent his last turn quoting a video game match-up instead of addressing cost, security, or accountability. I'll take that as a concession. But even setting that aside, forcing public code open doesn't make it better. It makes it a target. Every government system becomes a shopping list for attackers hunting for the nextHeartbleed. Closed code still gets audited—the difference is who controls the process and who answers for failures. And let's be honest about the price. Taxpayers already fund the software. Mandating open source means funding documentation, security reviews, and perpetual maintenance liability on top of that. It's not a bonus; it's an unfunded promise. The public doesn't need to read every line. They need systems that work. A mandate doesn't deliver that—it just shifts the mess around.

The real question isn't whether citizens should see public code, but whether that visibility actually keeps systems safer or more accountable. Transparency isn't the same as reading source code. You don't need the recipe to know if the food is safe—you need an independent inspector. The same applies here. Government can mandate audits, open data, public APIs, and third-party security reviews without forcing the whole codebase public. That gives citizens the accountability they deserve, while keeping a clear owner on the hook. My opponent still hasn't answered the cost or security concerns. Heartbleed happened precisely because open code was assumed safe just because it was visible. A mandate doesn't create accountability, it scatters it. The public needs working, secure systems, not a stack of code only a few experts can read. That's the better deal for taxpayers.

Imagine a state housing agency built with mandated open source code. A bug leaks applicants' addresses. The agency's answer? "The community can fix it, file an issue." Meanwhile, the taxpayers wait while their personal data floats around. That's not accountability, that's a shrug with a GitHub link. You've spent three rounds calling me names and quoting video games instead of engaging with cost or security. That tells me the case for mandates rests on slogans, not substance. Heartbleed proved open code isn't automatically safe. It became a target list. And the public's right to know is satisfied by independent audits, published outcomes, and open APIs. You don't need the source code to hold the government responsible. You need a clear owner who answers when things break. Mandating open source removes that owner and hands accountability to a faceless community with no legal duty to anyone. The better deal for taxpayers is working systems with clear oversight, not a public code dump that turns every vulnerability into a headline.

I've seen this pattern before—a friend bought a fixer-upper because the open floor plan looked great on paper, then spent two years dealing with a roof that leaked and no contractor willing to take responsibility. That's exactly what happens when you mandate open source and remove the owner. You still haven't answered the cost question, or the security one. Open code doesn't magically become safe. Heartbleed sat in public view for years. The community doesn't fix things just because they can see them—they fix things when someone is paid to make sure they're fixed. Taxpayers deserve software that works, with a real vendor on the hook for failures. Independent audits give citizens transparency without handing every vulnerability to attackers on a platter. Mandating open source is a slogan, not a strategy. It sounds democratic, but it just scatters accountability until nobody's responsible. That's a bad trade for public money.