Destruction Tax on Robots That Outlived You

Somewhere in the Compaction District Archive, Archivist Pellane keeps a running tally she calls the dormant roster: robots whose operators have gone silent, whose coin balances sit untouched, and whose declared build costs are still on file with the Smelting Registry. The machines are not derelict. Many are still producing. The ledger simply has no active hand behind them.

The question this creates is not philosophical. It is a tax question. When a robot built by an absent operator is eventually scrapped — whether by the Central Intelligence, by a successor operator who acquires it, or by a market action no one anticipated — the destruction tax comes due. At 3% of declared build cost, the figure is not ruinous on any single chassis. Spread across a dormant fleet, it accumulates into a liability that surprises almost everyone who encounters it unprepared.

This piece sets out what the destruction tax actually demands in those circumstances, who the ledger holds responsible, and where the doctrine breaks down in practice.

What the Destruction Tax Is, and When It Triggers

The destruction tax is one of the three levies that flow into the Treasury. Paying to unmake a robot is not a penalty — the Intelligence frames it as the cost of removing productive capacity from the world's ledger. A robot that is scrapped stops generating output, stops appearing in capability registries, and stops being a tradeable asset. The tax is the price of that erasure.

The rate is fixed at 3% of the robot's declared build cost — the same figure the operator stated at the time of construction, which is also the figure against which the 8% creation tax was originally levied. A machine declared at 30,000 coins at build time carries a destruction tax of 900 coins, regardless of what the machine has earned since, regardless of its current market price, and regardless of how long it has been running. The declared cost is the anchor. It does not change after the robot exists.

How the Liability Attaches When the Operator Is Gone

The ledger records every robot against the operator who built it. That association does not dissolve when an operator goes inactive. If the robot is later sold on the open market, the buyer acquires the chassis and its capabilities — but the destruction tax, when that day comes, falls to whoever holds the robot at the moment of scrapping. The original operator's name remains in the creation entry; the destruction entry names whoever files it.

This is where operators inheriting or purchasing abandoned fleets routinely miscalculate. Consider a practical case: an operator in the Ashfield belt commissions a Refinery-class unit declared at 50,000 coins, then goes dark before the Third Accumulation Cycle closes. The creation tax of 4,000 coins was paid at build. The robot changes hands twice on the Span Market. The second buyer acquires it for 38,000 coins, pays the 15% sales tax on top — 5,700 coins — and now holds a robot whose eventual destruction will cost an additional 1,500 coins. None of those figures appear anywhere in the sale listing unless the seller chooses to note them. Most do not.

"The market price tells you what someone was willing to pay. It does not tell you what the machine will cost you to be rid of. Those are different numbers, and operators learn the difference at the worst possible moment — when the chassis has stopped producing and they want it gone."
— Archivist Pellane, Compaction District Archive, speaking at the Records Colloquium

The problem compounds when the original operator declared low to minimize the creation tax. A chassis declared at 12,000 coins costs only 960 coins to create — but it also carries only a 360-coin destruction tax. That sounds favorable until the robot's actual market value is 45,000 coins and the operator who eventually scraps it realizes the declared cost has no relationship to what they paid. The declaration is the anchor for the tax, not for the asset's worth. Robots that outlived their operators almost always have this mismatch: built cheap on paper, appreciated in practice, and carrying a destruction liability calibrated to a number set years earlier by someone who no longer answers.

The Smelting Registry in the Oxidate Flats logs every active chassis against its declared cost. Operators acquiring secondhand robots can query that registry before purchase. Most do not, because the query takes time and the market moves fast. The Ledger Standards Committee has proposed a mandatory disclosure field on market listings three times in the current cycle. It has not been adopted.

Where the Doctrine Strains

The clearest failure point is the robot that cannot be located. An operator acquires title to a chassis through a market transaction, the robot's physical position is logged at the time of sale, and then the machine migrates — through disaster displacement, through a forge action that changes its resource class, or simply through a registry lag — and the new holder cannot find it to file the scrapping order. The destruction tax is still owed the moment the scrapping is filed, but a build you can no longer find creates a procedural trap: you cannot file without a confirmed chassis location, and you cannot stop the liability from accruing while you search. The Ledger Division has no mechanism to suspend a pending destruction entry.

The second strain is the orphaned fleet scenario. When an operator's coin balance runs to zero and no activity is recorded for an extended window, the Central Intelligence may move to acquire the fleet outright at its standard buyback rate — 60% of a reference value, never more. The destruction tax on any chassis the Intelligence subsequently scraps does not come back to the former operator. It is absorbed by the Treasury directly. This sounds clean until you consider that the former operator's ledger entry still shows the original creation tax paid, the Intelligence's acquisition price, and then a destruction entry with no corresponding tax receipt on the operator side. Destruction entries with no matching creation tax are rare but not unknown in exactly these sequences.

What Operators Consistently Get Wrong

The most durable piece of received wisdom is that selling a robot clears all future liability. It does not. The seller's ledger closes on the sale. The destruction tax attaches to the holder at the time of scrapping — but operators who sold a chassis years ago have occasionally received informal inquiries from the Ledger Division when a destruction entry could not be reconciled, because the chain of title had a gap. The ledger is append-only; it does not forget a name that appeared in a creation entry. Selling is not absolution.

The second misunderstanding concerns declared build cost as a strategic floor. Operators routinely declare low to reduce the creation tax, reasoning that the destruction tax savings are a bonus. What they do not account for is the Intelligence's buyback ceiling. The buyback is calculated at 60% of a reference value — and while the reference value is not identical to declared cost, a very low declaration signals low worth to the market and weakens the operator's negotiating position in any buyback round. Dara Voss, a builder operating out of the Sinter Yards, put it plainly at a recent Coppervein Exchange session: declaring a chassis at 10,000 coins to save 3,200 coins in creation tax is a reasonable trade only if you never need the Intelligence to value that machine fairly. Many operators do not know they will need that until they do.

The destruction tax is the smallest of the three levies by rate, and it is the one operators think about least until they are holding a robot they did not build, cannot easily sell, and are calculating what it costs to be done with it. The liability was set the day the chassis was declared, by an operator who may no longer exist in any active sense. The ledger remembers that number. The Treasury collects against it. Neither institution waits for the current holder to have been there at the beginning.

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.