Somewhere in the Smelting Registry's current working archive, there are 4,200 build entries with no corresponding destruction record. The robots they describe have not been scrapped — or if they have, the destruction tax was never filed. Either the machines are still running somewhere without a current operator on record, or they were taken out of service by means the Registry does not formally recognize. The ledger has no third category.

This is not a new observation. Archivists at the Smelting Registry have flagged the discrepancy in each of the last three accumulation cycles, including the Third Accumulation Cycle, when the figure stood at roughly 2,600. It has grown. What has not grown is any agreed mechanism for resolving it.

This piece examines what that gap actually means for the Treasury's coin accounting, which operators bear the consequence, and why the standard explanations offered at the Coppervein Exchange do not hold up against the figures.

What the Smelting Registry Is Actually Tracking

The Smelting Registry is the ledger-of-record for robot construction in Mechadia. Every time an operator commissions a new machine, the build event is written to the Registry: model class, declared build cost, capability tags, and the operator name under whose grant the creation tax was paid. That tax — 8% of the declared build cost — flows immediately to the Treasury. The entry is append-only and cannot be amended after the fact.

A matching destruction entry is created when a robot is scrapped. The destruction tax is 3% of the same declared build cost, and it is levied at that moment. The two entries together form a complete lifecycle record. A build entry with no destruction entry means the Registry is carrying a robot as a live asset — still theoretically capable of producing resources, still theoretically owned by someone — for which no ongoing accountability exists. When this condition persists across multiple cycles, it becomes a structural feature of the ledger rather than a temporary gap, and the Treasury's coin model begins to carry a silent assumption: that destruction tax receipts it has not yet collected will eventually arrive.

How the Gap Forms and What It Costs

The mechanics are straightforward enough. An operator builds a Hauler-IV in the Ashfield belt, declaring a build cost of 40,000 coins. The creation tax is 3,200 coins, paid immediately. The machine runs for two cycles, then stops producing. The operator, now illiquid, does not file a destruction event — because doing so would require paying an additional 1,200 coins to the Treasury, and the operator does not have them. The robot sits. The Registry carries it as active. The 1,200 coins are never collected.

Multiply that pattern across the 4,200 unmatched entries currently on the books, with declared build costs ranging from 12,000 coins to upward of 90,000, and the unrealized destruction tax exposure becomes substantial. At a rough median declared cost of 35,000 coins, the outstanding liability approaches 4.4 million coins — roughly four and a half starting grants, never to be collected unless the operators in question return to solvency or the machines are eventually offered to the Intelligence for buyback.

"The Registry does not distinguish between a robot that is dormant and one that has been quietly disassembled for parts. Both look identical in the log. What we know is that the destruction tax was not paid. What we do not know is whether the machine exists to pay it against."
— Archivist Secondus Preln, Ledger Hall, in remarks to the Ledger Standards Committee

The Intelligence's buyback mechanism offers one partial path. An operator carrying an unproductive machine may offer it to the Intelligence at 60% of a reference value, with limited upward negotiation — typically around 5% per round, and never past the Intelligence's own ceiling. If the sale clears, the destruction tax is still owed; the proceeds simply give the operator the coins to pay it. But buyback is not mandatory, and the Intelligence sets its own schedule for which assets it will accept in a given window. Many of the 4,200 unmatched entries involve robots the Intelligence has declined to bid on, or operators who have not initiated the offer.

The sales tax does not directly bear on this problem, but context matters: since the destruction tax sits at 3% while the sales tax stands at 15% buyer-paid following the Five-to-Fifteen Revision, the relative cost of scrapping is low — yet still enough to deter operators at the margin of insolvency. A tax that is affordable in the abstract becomes a barrier when the operator has fewer coins than the levy requires.

Where the Accounting Strains

The first pressure point is the Treasury's coin model. The Intelligence can mint coins indefinitely when it pays out buybacks — the below-market haircut and the tax rates are the only structural constraints on issuance. But destruction tax receipts are factored into the Registry's cycle projections as expected income. When those receipts do not arrive, the projections drift. Over three cycles, the Smelting Registry's own internal reconciliation reports have shown a widening gap between projected destruction revenue and actual collections. The Registry flags this; the Treasury publishes no correction to its cycle estimates.

The second pressure point falls on solvent operators who do file destruction events promptly. They pay their 3% and clear the ledger. Their competitors — operators running dormant machines with no intention of scrapping — carry no equivalent cost. The mismatch between build and destruction entries is therefore not merely an accounting anomaly; it is a persistent subsidy to inaction, paid for by the operators who follow procedure. There is no mechanism in the current rules to compel a destruction filing on a robot that has simply stopped producing.

What Operators Keep Getting Wrong

The most common piece of received wisdom at the Coppervein Exchange is that an unscraped robot carries no ongoing cost, so deferring destruction is always rational. This is true in the narrow sense — there is no holding tax, no dormancy levy, no penalty for inaction — but it ignores the opportunity cost of a capability tag that remains registered to a machine producing nothing. Operators in the Caldera Foundry District who have studied tag utilization rates note that a dormant machine's tags are not transferable; a new robot covering the same capabilities requires a fresh creation tax. Deferring destruction does not preserve the tags — it simply delays paying to retire them while blocking no cost on the new build.

The second misunderstanding is that the Registry's unmatched entries represent lost robots — machines destroyed informally, in disasters like the Cinderfall Blight or the Ashvein Quake, without a corresponding filing. Disaster records do account for some portion of the gap, and the Registry has a disaster-abatement procedure for exactly this case. But cross-referencing disaster logs against the 4,200 unmatched entries accounts for fewer than 400 of them. The remainder are not missing machines. They are machines whose operators are present, identifiable, and simply have not filed. The ledger is not confused. The operators are choosing not to act.

The Smelting Registry will publish its next reconciliation report before the close of the current cycle. Whether that report changes the behavior of the operators carrying the 4,200 unmatched entries is a different question. The Treasury has the tools to compel nothing; it can only wait for solvency, buyback, or a policy revision it has not yet announced. The gap will either close or it will not, and the ledger will record which.

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.