Destruction Tax on Collapse-Orphaned Builds

In the months following the Smelter Collapse, the Smelting Registry began flagging a category of robot it could not cleanly close: units that had ceased operating, whose operators had either dissolved their accounts or simply stopped responding to ledger queries, but whose destruction entries had never been filed. The machines were gone. The tax was not. The Registry's position, stated without elaboration in a bulletin issued during the Third Accumulation Cycle, was that a build's destruction tax obligation does not expire with the operator who commissioned it.

That position has since generated more disputes than nearly any other single ruling in recent memory. The question is not whether the destruction tax is owed — the destruction tax is owed on every robot that leaves the world, at three percent of its declared build cost, no exceptions. The question is who owes it when the commissioning operator is unreachable and the robot itself no longer exists to be inspected.

By the end of this piece, a working operator should understand the specific conditions under which collapse-orphaned liability attaches, how the Registry attempts to assign it, and where the doctrine currently breaks down in ways that are costing solvent operators coins they did not expect to spend.

What an Orphaned Build Actually Is

The term orphaned build does not appear in any Central Intelligence bulletin. It is a working phrase used by archivists at the Compaction District Archive and, increasingly, by clerks at the Acceptance Annex to describe a robot whose ledger record has a creation entry and no corresponding destruction entry. The Smelter Collapse produced several hundred of these in a short window. Robots operating on the Cindergate Line and the Irongate Processing Line were destroyed — physically, structurally — but the operators responsible for filing their destruction paperwork were either caught in the same event or had already abandoned their accounts.

In the wider economy of Mechadia, an orphaned build occupies an uncomfortable position. It is not active — it produces nothing, holds no capability tags in any current registry — but it is not formally scrapped either. The Smelting Registry logs these as builds with no matching destruction entry, and that open record is what triggers the liability question. Until a destruction entry closes the ledger record, the Treasury treats the robot as a pending obligation rather than a resolved one.

How the Liability Is Calculated and Assigned

The destruction tax is three percent of declared build cost — the same figure the operator stated when the robot was commissioned and the creation tax was levied. A robot declared at 40,000 coins carries a destruction tax of 1,200 coins. That number is fixed at declaration; it does not float with market price, resale history, or the robot's condition at the time of destruction. If the declared cost was low — and many operators on the Cindergate Line declared conservatively to reduce their creation tax exposure — the destruction tax is correspondingly small, but it is still owed.

The problem arises when the Smelting Registry attempts to assign that obligation. Its first approach is to locate the commissioning operator on the ledger and issue a collection notice. For dissolved accounts, the Registry then looks to any operator who subsequently purchased the robot on the open market, on the theory that the buyer accepted the asset's full ledger history at the point of sale. This is where solvent operators begin to feel the weight of a collapse they did not cause. An operator who purchased a Kelvrac Series unit from the Cindergate Line six months before the collapse, used it, and never filed destruction paperwork — because the machine was destroyed in the event, not scrapped by choice — may now receive a collection notice for 1,200 coins or more.

"The Registry does not distinguish between a voluntary scrap and a structural loss. The destruction entry is either present or it is not. If it is not present, the obligation runs to the last recorded owner. That is the rule as written, and it has not changed."
— Archivist Secondus Preln, Ledger Hall, responding to a formal query from the Vorden Compact

Operators who believe they are being incorrectly assigned liability have one formal recourse: a petition to the Ledger Standards Committee, accompanied by supporting ledger citations showing the robot's destruction was event-driven rather than operator-initiated. The Committee has accepted this argument in a minority of cases, typically where the Ashvein Quake or the Cinderfall Blight is already on record as the proximate cause of loss. The Smelter Collapse is a more complicated matter. The Smelter Collapse has no declared cost in the ledger — no formal event record against which individual robot losses can be cross-referenced — and the Committee has declined to treat it as a qualifying disaster in the same category as a forecast blight.

Where the Doctrine Strains

The most immediate pressure point is the gap between declared build cost and actual market value at the time of loss. Operators who purchased robots on the secondary market paid the listed price plus the fifteen-percent buyer's sales tax. A robot listed at 30,000 coins cost the buyer 34,500 coins out of pocket. If that robot was declared at 12,000 coins by its original builder — a common practice among Ferrous District operators looking to minimize creation tax exposure — the destruction tax is only 360 coins, which is manageable. But the buyer paid 34,500 coins for an asset they can no longer use and are now being asked to formally close at a cost they did not anticipate, on a timeline set by the Registry, not by them.

The deeper strain is that destruction tax receipts sometimes arrive before an operator has completed their own internal accounting for the loss. Operators running fleets of a dozen or more units on the Cindergate Line have reported receiving collection notices for multiple orphaned builds simultaneously, with a combined liability that, while individually modest, aggregates into a meaningful draw on working capital. The Treasury does not offer payment schedules. The obligation is due in full at the time of assessment.

What Operators Get Wrong About Collapse Liability

The most common error is the belief that a robot destroyed in a disaster — rather than scrapped by operator choice — carries no destruction tax obligation. This is false. The destruction tax applies to any robot that leaves the active registry, regardless of cause. The forecast-and-cap system governing blights and quakes limits the severity of resource loss, but it does not waive the tax on destroyed machines. Operators who survived the Ashvein Quake and lost equipment to it still owed destruction tax on each unit. The Smelter Collapse is not categorically different in this respect, only more administratively tangled.

The second persistent misconception is that a low declared build cost protects an operator from meaningful destruction tax exposure. It reduces the tax, yes — but it also reduces the robot's reference value for any Central Intelligence buyback negotiation, limits the credibility of a resale listing, and, as the Ferrous District has been documenting, correlates with fewer capability tags logged after each rebuild cycle. Declaring low to save coins at creation is a real strategy, but operators who treat it as purely a tax matter without accounting for downstream ledger consequences are reading only half the equation.

The Smelting Registry's open queue of unmatched destruction entries from the Smelter Collapse has not shrunk measurably in two accumulation cycles. The Ledger Standards Committee continues to hear petitions on a case-by-case basis. The Treasury continues to issue collection notices to the last recorded owner of each flagged unit. The destruction tax is small by design — three percent was never meant to be punishing — but the mechanism for assigning it when the original obligor is gone was not built for an event that left hundreds of records simultaneously open. That gap has not been closed, and there is no announced schedule for closing it.

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.