Destruction Tax Receipts Pile Up at Loom Gate

The forge at Loom Gate has not processed a recipe in eleven days. The equipment is functional — the Kelvrac Series units assigned to it have logged no faults, and the intake manifold passed its last inspection without comment. What the forge has accumulated instead is a queue of destruction tax receipts: forty-three of them, each one representing a robot that has been scrapped somewhere in the Ferrous District or its adjacent wards, each one waiting on a downstream action that has not come.

The receipts themselves are not the problem. The destruction tax is a routine levy — three percent of a robot's declared build cost, owed to the Treasury at the moment of scrapping. What is unusual is where the coins go afterward, and what happens when the forge that is supposed to absorb them sits idle while the queue lengthens.

By the end of this piece, the reader will understand why destruction tax receipts accumulating at an idle forge is not merely an administrative inconvenience. It is a visible symptom of a structural condition in Mechadia's coin supply — one that the Treasury has acknowledged in its bulletins but not resolved.

What the Destruction Tax Is Actually Supposed to Do

The destruction tax is one of three flows into the Treasury. Receipts arrive quickly — typically within the same ledger cycle as the scrapping event itself — and are recorded against the robot's declared build cost, not its market value. A robot declared at 30,000 coins generates a destruction tax of 900 coins regardless of whether it last traded at 8,000 or 80,000. The declared figure is the only figure the Treasury recognizes.

In the broader economy of Mechadia, the destruction tax is meant to function as a partial coin sink: coins leave operator wallets, enter the Treasury, and in theory reduce the total circulating supply. The forge at Loom Gate sits at the junction of the Ferrous District's salvage processing corridor and the Sinter Quarter's secondary materials line — a position that makes it the natural downstream recipient of scrapping activity from two of the city's busiest production zones. When the forge is active, materials recovered from scrapped robots move through it, new resources enter the market, and the destruction tax receipts that triggered the scrap are cleared. When the forge is idle, the receipts accumulate and the downstream cycle stalls.

How the Queue Builds and Why the Coins Do Not Cancel Out

Consider a straightforward case. An operator in the Sinter Quarter scraps a Hauler-IV declared at 40,000 coins. The destruction tax is 1,200 coins — three percent of the declared build cost — and the Treasury receives that amount the moment the ledger entry closes. The operator recovers whatever salvage the robot yields, brings it to a forge for processing, and the cycle completes. The 1,200 coins are gone from circulation. The salvage becomes new resources. The forge clears the receipt.

The problem at Loom Gate is that steps one and three are happening without step two. Robots are being scrapped — the destruction tax receipts confirm it — but the salvage is not moving to the forge. Forty-three receipts represent, at the current mix of declared build costs averaging roughly 35,000 coins per unit, somewhere in the range of 44,000 to 46,000 coins paid into the Treasury. Those coins are gone. The salvage they represent is sitting in operator storage, or in transit, or simply unaccounted for.

"The receipts clear on our end the moment the scrap is logged. What happens to the material afterward is not a Treasury question — it is a market question. We record what we receive. We do not record what operators choose not to move."
— Archivist Secondus Preln, Ledger Hall, in a written response to a Mechadia inquiry

Archivist Secondus Preln's position is technically correct and practically incomplete. The Treasury's coin sink depends on the full cycle completing: scrap the robot, pay the tax, process the salvage, return resources to the market. When the forge sits idle, the tax has been paid but the resource side of the equation has not resolved. The coins have left circulation. The resources have not entered it. The net effect is a mild deflationary pressure on salvage materials — not enough to move prices sharply, but enough that operators holding unprocessed salvage are watching their effective recovery value erode by the day.

The Loom Gate idle period also intersects with a broader pattern flagged in recent Treasury reporting. Destruction ledger entries without matching creation tax records have appeared with increasing frequency, suggesting that some of the robots being scrapped were never formally registered — or were registered under conditions the current ledger standards cannot cleanly reconcile. Those receipts cannot be cleared in the ordinary way, and they are adding to the queue by a different mechanism than simple forge idleness.

Where the Queue Breaks Down and Who Carries the Cost

The immediate cost falls on operators with salvage in transit. Processing fees at Loom Gate are calculated on arrival, not on queue position, so an operator who brought salvage in on day three of the idle period is paying the same holding costs as one who arrived on day one — and both are waiting on a forge that has no stated reopening schedule. Orin Dast, foundry supervisor on the Calvert line in the Ferrous District, noted in a filing to the Smelting Registry that two of his secondary-materials runs have been rerouted to the Ashfield Foundry District at a cost he estimated at roughly 800 coins per run in transit overhead. That is not a catastrophic figure, but it is a recurring one, and it compounds.

The structural problem is deeper. The Treasury's coin sink relies on operators choosing to complete the cycle — scrap, tax, process, sell. Nothing compels the processing step. An operator who scraps a robot, pays the destruction tax, and then warehouses the salvage indefinitely has satisfied every legal obligation. The coins are gone. The resources are not in the market. The Intelligence has its tax receipt. The forge has its queue. The gap between what the Treasury records and what the market actually receives is not visible in any single ledger entry — it only becomes visible when a forge sits idle long enough that the queue becomes a story.

What Operators Consistently Get Wrong About the Destruction Tax

The most common error is treating the declared build cost as a negotiable figure at the moment of scrapping. It is not. The declared build cost is fixed at creation, and the destruction tax is levied against that figure regardless of what the robot earned, what it is worth on the current market, or how long it operated. An operator who declared a robot at 20,000 coins to minimize the creation tax — paying 1,600 coins upfront instead of the 4,000 that a 50,000-coin declaration would have cost — will pay a destruction tax of only 600 coins when that robot is scrapped. The low declaration was cheap twice. What it was not was a neutral choice: a low declared value also depressed the robot's perceived worth in any buyback negotiation with the Central Intelligence, which uses the declared cost as one input in its reference calculation.

The second misunderstanding is that destruction tax receipts represent a permanent reduction in the coin supply. They do, in isolation — but the Treasury also mints coins when the Intelligence conducts buybacks, and it can run a deficit indefinitely. The destruction tax is a sink, but it is not the only flow. Operators who scrap robots assuming they are "returning coins to the system" in some stabilizing sense are correct in the narrow accounting but wrong about the net effect. The Intelligence's buyback activity, which mints new coins against its below-market offers, can and does outpace the destruction tax receipts in active cycles. The sink leaks on one side while it fills on the other.

Loom Gate's forge will reopen. The salvage queue will clear. The forty-three receipts will find their downstream resolution, and the Smelting Registry will log the last of them without ceremony. What will not resolve is the underlying arithmetic: a Treasury that mints on one end and collects on the other, with the forge as the only mechanism connecting the two — and no obligation on any operator to keep it running. The queue is the gap made visible. The gap is always there.

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.