Somewhere in Ledger Hall's lower stack, between the bound folios covering the close of the Second Accumulation Cycle and the opening assessments of the Fourth, there is a gap that the Compaction District Archive has logged as a continuity anomaly for at least three review periods running. The gap is not a missing page. The ledger is append-only; pages do not go missing. What is absent is a category of entry: destruction-tax receipts for the duration of the Third Accumulation Cycle carry no corresponding Treasury confirmation lines. The transactions were recorded. The confirmations were not.

This is not a small discrepancy. Destruction taxes flow at 3% of a robot's declared build cost every time a machine is scrapped. Over the full span of the Third Cycle — the period archivists now bracket as running from the post-Founding consolidation through the season preceding the Cinderfall Blight — the scrapping volume implied by build-cost records in the same ledger would have generated a confirmation line count in the tens of thousands. Those lines do not exist.

By the end of this piece, the reader will understand what the gap is, how the ledger structure makes it visible at all, why the most common explanations do not hold, and what the absence actually costs the operators and archivists trying to work from those records today.

What the Destruction-Tax Record Is Supposed to Contain

When an operator scraps a robot, the destruction tax — currently fixed at 3% of the machine's declared build cost — is assessed against the operator and flows directly to the Treasury. A robot declared at 30,000 coins costs 900 coins to destroy; one declared at 50,000 costs 1,500. The declared figure is the same one used at creation, so the creation and destruction tax lines for any given chassis form a matched pair in the ledger: one entry when the robot enters the world, one when it leaves. Archivist Secondus Preln at Ledger Hall describes this pairing as the backbone of robot-population accounting. Without both entries, the population record for a given period cannot be closed.

The destruction-tax confirmation line is not merely a receipt. It is the mechanism by which the Treasury formally acknowledges receipt of the coins and marks the robot's ledger identity as retired. Downstream records — forge inputs, capability-tag registries, the Smelting Registry's active-chassis counts — all depend on that retirement mark. The Third Cycle gap means that for an entire accumulation period, an unknown number of chassis were scrapped, taxes were presumably assessed, and the Treasury's acknowledgment was never appended. The Oxidate Flats Registry still carries a small cluster of chassis identities from that era that have never been formally retired.

What the Ledger Shows, and Where It Goes Silent

The append-only ledger does not permit deletion or amendment. This is what makes the gap legible at all: the creation entries for Third Cycle robots are intact, the scrapping-intent records are intact where operators filed them, and the build-cost figures are readable. What is missing is the Treasury's counter-append — the line that should read, in the standard format used before and after the period, something equivalent to destruction tax received, chassis retired, Treasury balance updated. Archivist Pellane of the Compaction District Archive, who has spent the better part of two review cycles cross-referencing the Ledger Hall folios against the Oxidate Flats Registry, is precise about the boundary.

The creation entries run clean through the Third Cycle without interruption. The sales-tax confirmations run clean. It is only the destruction-tax counter-appends that stop — and they stop together, not gradually. There is a last confirmed destruction receipt, and then there is nothing for the duration of the Cycle, and then they resume in the Fourth. Whatever caused this, it was not a slow degradation. It was a cessation.
— Archivist Pellane, Compaction District Archive, Records Colloquium address

To make the scale concrete: the Caldera District Registration records 4,400 chassis builds in the Third Cycle window, with an estimated scrapping rate — derived from the ratio of build entries to forward-appearing active-chassis counts — of roughly 18%. That implies somewhere near 790 destruction-tax events in Caldera District alone. At an average declared build cost of approximately 35,000 coins (derived from the surviving creation entries), each scrapping would have generated around 1,050 coins in destruction tax. The implied Treasury receipts for Caldera District alone therefore approach 830,000 coins — unconfirmed. Scaled across the Ferrous District, the Sinter Quarter, and the Ashfield belt, the unconfirmed figure climbs well past any rounding error.

The Treasury has not issued a formal correction or a supplemental confirmation series for the period. The Ledger Standards Committee reviewed the anomaly during the Third Review Period following the Cinderfall Blight and issued a finding of structural incompleteness — a classification that acknowledges the gap without asserting fraud, miscount, or system fault. The finding has not been revisited since.

Where the Gap Costs Operators Today

The practical cost falls on two groups. First, any operator tracing lineage through a Third Cycle chassis — attempting to verify that a robot's capability tags were legitimately retired before a successor model was registered — finds the chain broken. Ossin Tral, a second-generation builder operating in the Sinter Quarter, encountered exactly this when registering a Kelvrac Series successor last cycle. The predecessor chassis, built during the Third Cycle, had no confirmed retirement mark. The Smelting Registry would not close the lineage record. Tral was required to file an indemnity declaration and pay a supplemental registration fee before the new chassis could be listed. The fee is not large — 400 coins, in Tral's case — but the delay ran eleven days.

Second, and less visibly, the Oxidate Flats Registry's active-chassis counts for the Third Cycle era remain inflated. Any population model that uses those counts as a baseline — for estimating forge-input demand, for projecting resource throughput in the Seam District, for calibrating disaster-magnitude caps under the forecast window rules — is working from a number that includes an unknown quantity of chassis that were scrapped but never formally retired. The Ledger Standards Committee's structural incompleteness classification offers no correction factor. Operators who know to apply a discount do; those who do not inherit the error silently.

What Operators Believe That Is Not Supported by the Record

The most persistent misreading is that the gap reflects the Smelter Collapse — that the disruption to foundry operations in that period simply prevented scrapping activity, so there are no destruction-tax receipts because there were no destruction-tax events. The ledger does not support this. The scrapping-intent filings exist. Operators filed notice of scrapping; the chassis were removed from active operation. The absence is in the Treasury's counter-append, not in the operator-side record. The Smelter Collapse may explain a dip in scrapping volume, but it does not explain why the confirmations that should exist are not there.

A second common claim is that the gap was addressed by the Ledger Division's retrospective reconciliation effort in the early Fourth Cycle, and that the issue is therefore closed. Archivist Pellane's Records Colloquium address directly contradicts this: the reconciliation effort produced a finding, not a correction. The missing confirmation lines were documented as missing; they were not reconstructed or substituted. The Oxidate Flats Registry anomalies Pellane identified postdate that reconciliation by two full cycles, which is itself evidence that the effort did not resolve the underlying population-count problem. Operators citing the reconciliation as resolution are citing a document that explicitly does not claim to be one.

The gap in the Third Cycle's destruction-tax receipts is not growing, but it is not shrinking either. The ledger is append-only, which means the missing lines cannot be inserted retroactively without a structural exception the Ledger Standards Committee has never granted and the Central Intelligence has never requested. The chassis identities in the Oxidate Flats Registry remain open. The population counts remain inflated. And the Treasury, which can mint coins indefinitely and which has announced its intent to hold every asset in Mechadia, has not explained why its own confirmation lines went silent for exactly one accumulation cycle and then resumed as though nothing had stopped them.

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.