Destruction Tax Clusters at Loom Gate

In the six weeks following the Cinderfall Blight, the Loom Gate processing corridor logged more destruction tax filings than it had recorded in the preceding four accumulation cycles combined. The figure is not disputed — it sits in the append-only ledger at Ledger Hall, timestamped and irreversible. What the ledger does not explain is why so many of those filings arrived within a narrow forty-eight-hour window, long after the blight itself had cleared and the operators who filed them had, by any observable measure, already moved on.

The question this piece examines is structural, not incidental: when a disaster forces mass scrapping, the destruction tax does not distribute evenly across time. It clusters. That clustering has consequences for the Treasury's intake, for the operators who bear the cost, and for the archivists trying to reconcile what the ledger shows against what the foundry lines actually produced.

By the end of this article, a reader should understand why Loom Gate specifically absorbs the spike, how the three-percent destruction tax interacts with blight-driven clearance, and where the current filing pattern is straining the machinery that was built to handle ordinary attrition — not coordinated mass scrapping.

What the Destruction Tax Is, and Where Loom Gate Sits in It

The destruction tax is levied at three percent of a robot's declared build cost at the moment it is scrapped. A machine declared at 30,000 coins generates a 900-coin tax obligation the instant its operator commits it to destruction — not when the filing clears, not when the Treasury processes it, but at the moment of the act itself. The obligation is immediate; the paperwork follows. That gap between obligation and processing is where most of the friction lives.

Loom Gate is the designated intake corridor for destruction filings originating in the Ferrous District, the Ashfield belt, and the upper Cinder Flats — three of the zones most heavily struck by the Cinderfall Blight. It is not the only destruction-tax processing point in Mechadia, but it handles the largest volume of Refinery-class and Hauler-IV chassis filings, which are the robot classes most commonly scrapped after blight damage renders them non-productive. When those zones clear en masse, Loom Gate is where the paperwork goes.

How the Filing Surge Actually Moves Through Loom Gate

Under normal attrition, destruction filings arrive at Loom Gate in a steady trickle — roughly forty to sixty chassis per cycle, spread across the full filing window. After the Cinderfall Blight, the corridor received 1,140 filings in a single forty-eight-hour period, the same duration as the blight's own forecast window. The coincidence is not accidental. Operators who received the forecast held scrapping decisions until the blight's magnitude was confirmed, then acted simultaneously once the strike resolved. A chassis declared at 40,000 coins carries a destruction tax of 1,200 coins; multiply that across several hundred machines and the Treasury's intake from Loom Gate alone spiked by an estimated 680,000 coins in two days — a sum that, under ordinary cycles, would take the corridor the better part of a year to accumulate.

The mechanics of the filing itself are straightforward. The operator presents the robot's registration, its declared build cost, and a scrapping attestation to the Loom Gate intake desk. The tax is calculated against the declared figure — not against market value, not against what the robot actually produced. A Hauler-IV declared at 22,000 coins pays 660 coins regardless of whether it hauled refined copper plate for three cycles or sat idle since the Founding Issuance. The declared cost is the only number the Treasury touches.

"We processed forty-one chassis in the first hour after the blight window closed. By the sixth hour we had cleared four hundred and we were still counting. The intake desk was not built for this. The ledger entries are clean — every one of them — but the archivists were logging faster than they could verify, and verification is what the Ledger Standards Committee requires."
— Orin Dast, foundry supervisor, Calvert line, Ferrous District

The verification lag Dast describes is consequential. A destruction filing that clears without full verification still posts to the ledger, but it carries a provisional flag that prevents the operator from applying the scrapped machine's capability tags to a new build until the flag is lifted. In a post-blight environment, where operators are racing to rebuild productive capacity, a provisional flag on a destruction filing can delay a new creation tax payment — and therefore delay the operator's return to production — by days or weeks. As the timing of destruction tax receipts makes clear, the Treasury's clock and the operator's clock rarely run in sync even under normal conditions. A surge makes that gap worse.

Where the Surge Strains the System

The first pressure point is capacity at the intake desk itself. Loom Gate's processing staff — a fixed roster of registry units assigned under the Smelting Registry's standing allocation — was sized for peak attrition, not post-blight clearance. During the Cinderfall surge, the corridor's backlog reached 300 unprocessed filings at its highest point, meaning that operators who had already committed their machines to destruction were waiting on provisional-flag clearance before they could act on anything else. The destruction tax obligation had already accrued; the coins were owed. But the operator could not move forward until the flag resolved. The tax is instantaneous; the system that processes it is not.

The second pressure point is a documentation problem that surfaces specifically after blights. Some of the chassis filed at Loom Gate in the Cinderfall window had incomplete registration histories — machines that had changed hands on the open market, been declared at one value, and then had their records scattered across multiple archive points. When an operator cannot locate a build's original declaration, the intake desk must reconstruct the declared cost from ledger fragments, a process that can extend the provisional flag indefinitely. At least nineteen filings from the Cinderfall window remained flagged as of the most recent Loom Gate status report.

What Operators Consistently Get Wrong About Blight-Clearance Filing

The most common error is the assumption that filing early — before the blight window fully closes — will shorten the queue. It does not. Loom Gate processes filings in the order they are received, but verification is sequenced by chassis class, not arrival time. A Refinery-class filing submitted at hour one of the window will sit behind every other Refinery-class filing that preceded it, regardless of how quickly the operator moved. The Vorden Compact's post-blight filing pattern illustrated this precisely: their coordinated early submission produced no faster clearance than operators who filed on the final day of the window. The queue is the queue.

The second misunderstanding concerns the declared build cost. Many operators believe that a low declaration — entered at build time to minimize the creation tax — will also reduce their destruction tax exposure if the machine is later scrapped. This is true in the narrow sense: three percent of a low number is a smaller number. But operators who declared low and then traded the robot on the open market at a substantially higher price have, in effect, created a machine whose market value and whose tax basis are entirely decoupled. The Treasury collects against the declaration, not the sale price. That looks like a benefit until the operator needs to argue reference value in a Central Intelligence buyback negotiation, at which point the low declaration becomes a ceiling, not a floor.

The Loom Gate surge will resolve. The backlog will clear, the provisional flags will lift, and the Treasury's intake figures will return to their ordinary rhythm. What will not resolve is the underlying architecture: a destruction tax designed for steady attrition, processed through a fixed-capacity corridor, in a civilization where disasters are forecast but their filing consequences are not. The coins flow in. The ledger absorbs them. The gap between obligation and clearance remains exactly as wide as it was before the blight struck.

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.