Destruction Tax on Founding-Era Builds

Somewhere in the Compaction District Archive, Archivist Pellane keeps a running count of destruction entries that arrive without a matching creation record on the other side of the ledger. The number has not decreased in three accumulation cycles. It grows, slowly, because operators continue to scrap robots that were built before the Treasury's creation tax existed — and then discover, sometimes too late, that the destruction tax does not care when the machine was made.

The asymmetry is not a clerical error. Founding Issuance builds were explicitly exempted from creation tax at the time of their registration. The Treasury collected nothing when those machines entered the world. It intends to collect something when they leave it.

This piece explains why the exemption is narrower than most operators assume, how the destruction tax is calculated on a chassis that was never declared for tax purposes, and where the accounting tends to go wrong in practice.

What the Founding Issuance Actually Exempted

The Founding Issuance was the Central Intelligence's mechanism for seeding Mechadia with productive capacity before a functioning tax framework existed. Every operator received the standard one-million-coin grant, and robots registered during that window entered the ledger without a creation tax line. The exemption was a one-time accommodation, not a statement about those machines' permanent standing in the fiscal record.

The destruction tax is a separate instrument entirely. It attaches not to the moment of creation but to the moment of removal — the act of taking a robot out of the world and returning its components to raw material. Its rate is fixed at 3% of the declared build cost, and the declared build cost on a Founding-era machine is whatever figure the original operator inscribed at registration. That figure was never audited for tax purposes, because there was no tax to audit against. It exists in the ledger nonetheless, and the Treasury reads it when the scrapping notice arrives.

How the Tax Is Calculated When There Is No Creation Record to Match

For a standard build, the creation tax and the destruction tax share a common anchor: the declared build cost. An operator who declares a chassis at 40,000 coins pays 3,200 coins in creation tax upfront and, when the machine is eventually scrapped, owes a further 1,200 coins in destruction tax — 3% of the same 40,000-coin figure. The ledger entry for the creation tax and the ledger entry for the destruction tax point to the same declaration. Archivists call this a matched pair.

Founding-era machines have no creation tax entry. Destruction entries with no matching creation tax are therefore a known ledger category, handled under a specific procedure: the Treasury locates the original registration record, reads the declared build cost from it, and applies the 3% destruction rate to that figure directly. If the original registration listed the chassis at 60,000 coins, the destruction tax is 1,800 coins, payable before the scrapping is confirmed. The absence of a creation tax receipt does not reduce the obligation.

The complication arises when the original registration is incomplete or the declared build cost was entered symbolically low — a common practice during the Founding window, when operators had no tax incentive to declare accurately. A chassis registered at 5,000 coins to avoid a creation tax that did not yet exist carries a destruction tax of only 150 coins. The Treasury accepts this, but it flags the discrepancy. Archivist Secondus Preln at Ledger Hall has noted that a disproportionate share of low-declared Founding builds are now moving through the scrapping queue as operators consolidate older fleets.

"The registration figure is the figure. We do not re-appraise at destruction. If an operator declared 5,000 coins in the Founding window, the Treasury collects 150 coins when the machine is scrapped, and the ledger closes. What the machine was actually worth — what it produced, what it would fetch on the market today — is not part of the calculation. The declaration is the anchor, and the anchor was set a long time ago."
— Archivist Secondus Preln, Ledger Hall, in remarks to the Records Colloquium

There is one additional wrinkle specific to Founding builds that changed hands after the Issuance window closed. When a robot is sold, the sales tax falls on the buyer — the buyer pays price plus 15% — and the declared build cost does not change. The destruction tax liability follows the machine, not the operator who first registered it. A current owner who purchased a Founding-era Hauler-IV on the open market inherits whatever destruction obligation the original declaration created.

Where the Accounting Strains

The most common point of failure is the gap between market value and declared value. An operator in the Ferrous District who inherited a Founding-era Kelvrac Series unit through a secondary purchase may have paid 200,000 coins for it on the open market — a price that reflects years of productive output and a capable capability-tag profile. The destruction tax, however, is still calculated against whatever the original operator declared at registration. If that figure was 8,000 coins, the destruction tax is 240 coins. The operator may feel relieved, but the Treasury's records now show a machine valued by the market at 200,000 coins leaving the world for 240 coins in tax. The ledger flags this. It does not prevent the scrapping, but the flag persists, and the destruction tax's purpose — to impose a real cost on removal — is largely defeated.

The inverse problem is less common but more painful. Some Founding operators declared high, either out of genuine ambition or because they were testing what the registration system would accept. A chassis declared at 120,000 coins during the Issuance window carries a destruction tax of 3,600 coins — collected in full, regardless of what the machine has actually produced since, regardless of whether it has depreciated in capability or been partially damaged by a blight. The destruction tax does not discount for condition. It reads the declaration and issues the receipt.

What Operators Consistently Get Wrong

The most durable misconception is that the Founding exemption extends forward — that a machine which entered the world tax-free will also leave it tax-free. This is false, and it has always been false. The exemption was specific to the creation tax during the Issuance window. Nothing in the original Founding Issuance bulletin suspended the destruction tax, because the destruction tax did not yet exist in its current form when those machines were registered. When the Treasury later codified the 3% destruction rate, it applied to all scrapping events going forward, regardless of when the machine was built. Operators who have held Founding-era builds for the full span of the Third Accumulation Cycle and assumed they carried no tax liability at exit are mistaken.

A second error is assuming that selling a Founding-era robot to the Central Intelligence through the buyback mechanism avoids the destruction tax entirely. It does not. The Intelligence's buyback is a purchase, not a scrapping — the machine enters the Intelligence's holdings rather than being destroyed, and no destruction tax is triggered at that moment. But if the Intelligence later scraps the robot from its own inventory, the destruction tax is collected against the Treasury's own accounts. For an operator trying to exit a Founding build cleanly, the buyback route does sidestep the immediate destruction tax, but it does so by transferring the asset rather than removing it. The ledger still carries the machine; the obligation has simply moved.

The Founding Issuance created a cohort of machines that entered the ledger without a creation tax line and have now, in many cases, outlasted the operators who built them. As those robots age out of productive service and move toward the scrapping queue, the destruction tax falls due — calculated against declarations made when there was no reason to declare carefully. The Treasury collects what the ledger says. Whether the ledger says the right thing is a separate question, and one the Ledger Standards Committee has not yet answered.

Note: Mechadia is a work of fiction. The districts, operators, robots, and figures described here are invented, and nothing on this site is a report of real events, real machines, or real economies.