D.O.G.E. Policy Framework
Digital Oversight of Government Expenditures
Steps
1. Reboot and Full Scan
D.O.G.E. will restart and scan all government spending records from the beginning. Every past and current transaction must be checked from start to finish to detect any new unauthorized transactions that may have been added after the first scan.
2. Regular Scans
One scan is not enough. D.O.G.E. must run a full re-scan every three years. Extra scans may be ordered by Congress or the President if there are signs of fraud.
3. Detect Abuse
If abuse or suspicious spending is found, the case must be flagged and reported immediately.
4. Check All Currencies
Even though spending is in U.S. dollars, D.O.G.E. must also scan for traces in yen, euro, ruble, or digital tokens. Nothing should slip through.
5. Fix the Problem
- Individuals who abused the system will be banned, fired, and prosecuted
- Weak or flawed code must be rewritten and secured
- External hacking attempts must be blocked and fully investigated
6. Access for the President and Congress
Logs must be available for the President and key Congressional committees to guarantee direct oversight.
7. Stronger Protections for the Future
- Multi-layer security so no single person controls large transactions
- Automatic alerts for unusual spending
- Smart code checks that flag duplicates, hidden activity, or foreign currency
- Independent audits by outside experts
- Permanent logs that cannot be deleted or changed
8. Code Oversight and Backlogs
- The code must be reviewed for flaws, backdoors, or hidden functions
- Records must show who wrote and approved the code
- Flaws must be explained: why they existed, how they were missed, and if intentional
- Updates must always go through independent review
- All code changes must be logged with developer names attached
My almost Closing Words
Never forget that during the Obama era, many big contractors and tech firms were hired to build HealthCare.gov. The main contractor was CGI Federal (CGI Group). Others included QSSI (later UnitedHealth/Optum), Accenture Federal Services, Booz Allen Hamilton, Deloitte LLP, SAIC/Leidos, General Dynamics, Northrop Grumman, Mitre Corporation, and Optum.
Additional support came from Infosys, Oracle, Red Hat, and a small team of Google engineers in the “tech surge.” While Apple, Microsoft, and Amazon were not involved, the number of contractors was very high.
Because responsibility was spread across dozens of groups, the rollout failed. Communication broke down, testing was poor, code was broken, and security was weak. Billions of taxpayer dollars were wasted. Some flaws even opened the door to backdoors and exploits.
Lesson: Government must never hand control of critical systems to outside firms without strong oversight. D.O.G.E. must remain transparent, secure, and under the control of elected leaders and independent reviewers.
To Prevent This Ever Again
- Keep all code reviews public and traceable
- Limit the number of contractors to reduce confusion
- Require independent security checks for every update
- Demand clear ownership so no one can hide when things fail
- Ban secret contracts and inflated pricing
- Bring to justice any company or contractor that creates backdoors, hidden exploits, or intentional flaws — with full investigation, legal penalties, and permanent bans from future contracts
Democrat Influence, Money, and Companies
Key Democrat Appointees
- Kathleen Sebelius – HHS Secretary
- Marilyn Tavenner – Head of CMS
- Todd Park – U.S. Chief Technology Officer
- Jeff Zients – Obama advisor, later “Mr. Fix-It”
- Andy Slavitt – Optum executive, later Acting CMS Administrator
Contractor Influence Table
| Company / Group | Role in Healthcare.gov | Donations / Lobbying (2011–2012) | Political Lean (Obama era) |
|---|---|---|---|
| CGI Federal (CGI Group) | Lead contractor | Part of 128M lobbying / 32M total | Leaned Democrat |
| QSSI / Optum (UnitedHealth) | Data hub + later fixes | Millions via UnitedHealth PACs | Democrat ties (Slavitt) |
| Accenture Federal Services | Replacement contractor after CGI | Millions in consulting donations | Leaned Democrat |
| Deloitte LLP | State exchanges + back-end support | Top 10 donor, leaned Democrat | Democrat leaning |
| Booz Allen Hamilton | Consulting and integration | Millions to both, leaned Democrat | Democrat leaning |
| SAIC / Leidos | IT + defense support | Millions to both, leaned Democrat | Democrat leaning |
| General Dynamics | Call centers + tech support | Millions, leaned Democrat | Democrat leaning |
| Northrop Grumman | Systems support | Millions, leaned Democrat | Democrat leaning |
| Mitre Corporation | Advisory + research support | Funded by federal contracts | Democrat leadership ties |
| Infosys | IT services | Employee donations leaned Dem | Democrat leaning |
| Oracle | Database support | Execs donated to Democrats | Democrat leaning |
| Red Hat | Open source consulting | Execs donated to Democrats | Democrat leaning |
| Google engineers | “Tech surge” repair team | Google PAC + execs leaned Dem | Strong Democrat leaning |
Records show that 17 contractors spent about 128 million dollars on lobbying and gave 32 million dollars to candidates in 2011 and 2012, with nearly 4 million dollars going directly to President Obama’s campaign. Much of the rest supported Democrats and the Democratic Party. This proves how deep contractor influence was and why future systems like D.O.G.E. must remain transparent and free from political favoritism.
Peace