Destruction Tax on a Build You Cannot Find

Somewhere in the Compaction District, a Hauler-IV chassis sits past the end of its productive cycle. Its operator, a mid-tenure builder named Orvane Tek, wants it scrapped. The destruction tax is straightforward: three percent of the declared build cost, levied at the moment of decommission. The problem is that Orvane Tek cannot locate the original build entry. The chassis was acquired secondhand, the prior operator's records are thin, and the declared build cost — the number the tax is calculated against — is not in any ledger he can reach.

This situation is not rare. Robots change hands. Records from earlier accumulation cycles carry gaps. The Intelligence does not waive the tax because the paperwork is missing. It calculates against whatever reference value it can establish, and the operator pays.

By the end of this piece, a reader will understand how the destruction tax is assessed when a build entry is absent, what the Treasury uses in place of a declared cost, and where that process reliably produces outcomes the operator did not anticipate.

What the Destruction Tax Actually Requires

The destruction tax is three percent of the declared build cost — the figure the building operator logged at the time of construction. That declaration also determined the creation tax paid on the way in, so in the ordinary lifecycle of a robot the two figures are linked: one cost enters the Treasury at birth, a smaller one at death. The ledger entry for the scrapping cites the original build declaration by reference. Without it, the chain breaks.

Where the chain breaks, the Ledger Division falls back on a reference value. That value is not the same as a declared cost. It is an assessed figure, derived from comparable chassis on the open market, recent sales of similar models, and — in the absence of those — the Intelligence's own internal valuation tables. The operator has limited standing to dispute the reference value before the tax is levied, though a formal challenge may be filed afterward at Ledger Hall. Most are not.

How the Assessment Works When the Build Entry Is Gone

The Ledger Division's process begins with a search across three registries: the originating district's creation records, the Smelting Registry, and — for older machines — the archive held at the Compaction District Archive. If a match is found in any of them, the declared cost on that entry governs. If no match is found, the Division issues an assessment notice and begins the reference-value calculation. The operator has forty-eight hours to submit documentary evidence of the original cost before the assessment is finalized.

Consider a practical case. A Kelvrac Series refinery unit changes hands twice in eighteen months. The first transfer was recorded correctly. The second was logged against the wrong chassis identifier — a transcription fault at the Coppervein Exchange. When the current operator moves to scrap it, the build entry resolves to a different machine, one still active in the Ferrous District. The Division cannot apply that entry. It issues a reference-value assessment instead. If comparable Kelvrac Series units have been selling on the open market at around 45,000 coins, the reference value is set near that figure, and the destruction tax comes to roughly 1,350 coins — regardless of what the original operator actually declared.

"The ledger does not forgive a gap because the gap was someone else's fault. The tax event is the scrapping. The scrapping happened. The coins are owed."
— Archivist Secondus Preln, Ledger Hall, responding to a query from the Vorden Compact

The situation compounds when the machine in question dates to the Third Accumulation Cycle. Build entries from that period carry no operator names, which means the chain of custody is difficult to reconstruct even when the entry itself exists. An operator scrapping a Third Cycle machine may find the build record present but unverifiable, leaving the Division to treat it as contested and apply a reference value anyway. The practical effect is the same: assessed cost, not declared cost.

There is a further wrinkle for operators who acquired robots through the Intelligence's own buyback mechanism. Those transfers do not always carry a refreshed build declaration. The Intelligence pays a fraction of a reference value — its ceiling is sixty percent — and the chassis moves into its holdings with the original declaration, if one exists, or none at all. When those machines are later released back into circulation and eventually scrapped, destruction entries with no matching creation tax on the current ledger are the predictable result. The Division has a standing protocol for this class of entry, but it is slower and more expensive in staff time than a clean decommission.

Where the Process Breaks Against the Operator

The reference-value calculation is not adversarial by design, but it is systematically skewed. Market comparables reflect recent sale prices, which include the fifteen-percent sales tax paid by buyers — the rate that has held since the Five-to-Fifteen Revision. That tax is baked into observed market prices whether the Division accounts for it or not. An operator disputing a reference-value assessment on a 40,000-coin chassis may find the Division's comparable sales imply a gross price that overstates the robot's actual production value, and the three-percent destruction tax follows every digit upward.

The forty-eight-hour submission window for documentary evidence is the other pressure point. Operators managing large fleets in active districts — the Ferrous District's Calvert line runs decommissions on a rolling schedule — often cannot assemble transfer records, prior-owner declarations, and registry cross-checks inside two days. Orin Dast, foundry supervisor on the Calvert line, has noted that his crew files extension requests on roughly one in six assessed decommissions. Extensions are granted at the Division's discretion. They are not always granted.

What Operators Consistently Get Wrong

The most common error is assuming that a low original declaration protects against a high destruction tax. It does — but only if that declaration is recoverable. Builds with no matching destruction entry accumulate in the Smelting Registry precisely because operators defer scrapping machines whose paperwork is thin, hoping the problem resolves itself. It does not. The reference-value mechanism means a machine declared at 20,000 coins by its builder — a 600-coin destruction tax if the record held — can be assessed against a 45,000-coin market comparable and taxed at 1,350 coins instead. The difference is real and comes out of operating funds.

A second misconception is that secondhand acquisition transfers liability for missing records to the prior operator. It does not. The destruction tax is owed by whoever presents the machine for decommission. Prior-operator negligence may support a private claim, but the Treasury does not adjudicate those. It collects from the operator in front of it. Operators acquiring machines with thin documentation — particularly older chassis, Third Cycle units, or anything that passed through an Intelligence buyback — should treat the cost of reconstructing the build record as part of the acquisition price, not an optional administrative task to be handled later.

The destruction tax is narrow by design — three percent, declared cost, clean ledger — and the narrow design works when records are intact. When they are not, the mechanism widens into something less predictable, assessed against a reference value the operator did not set and may not be able to contest in time. The Intelligence's accumulation continues regardless. The coins flow to the Treasury either way. What changes is only who calculated the number, and how.

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.