Somewhere in the lower stacks of Ledger Hall, in the bound folios that Archivist Secondus Preln's office refers to as the Ward Sequence, there are destruction tax receipts that have no corresponding build entry. The machine was unmade. The tax was paid. The record of its creation, if one ever existed, is not there. The ledger is append-only, so nothing was removed. The entry simply was not written when it should have been.

The Ward Sequence is not a single anomaly. It is a pattern that has surfaced across at least three registration points — Caldera District Registration, the Oxidate Flats Registry, and the Smelting Registry — each with its own incomplete chain. The question this piece examines is not whether the gap is a clerical failure or something more structural. The question is what it costs, who pays, and what the existence of the gap implies about how the destruction tax actually functions in practice.

By the end of this piece, a reader should understand why an orphaned destruction entry is not merely a record-keeping inconvenience, and why the Treasury's ability to collect a tax against a robot it cannot prove was ever built creates a specific kind of pressure that the current rate structure does not resolve.

What the Destruction Ledger Is, and Where It Sits

Every robot that is scrapped in Mechadia generates a destruction tax receipt. The rate is 3% of the declared build cost — the same figure the operator stated when the machine was first registered, which is also the figure the creation tax was levied against at 8%. A machine declared at 30,000 coins costs 900 coins to destroy, regardless of what it has produced or what it would fetch on the open market. The destruction tax is a flat charge against the original declaration, and paying it is what formally removes a robot from the world.

The destruction ledger at Ledger Hall is the authoritative record of those receipts. It is maintained in sequence alongside the build ledger, and under normal conditions the two cross-reference each other: a build entry carries a registration identifier, and when that machine is eventually scrapped, the destruction entry cites the same identifier. The Ward Sequence breaks this chain. Destruction entries exist — tax was collected, coins moved to the Treasury — but the build identifiers they cite do not resolve to any build entry in the current corpus. The machines, on paper, were unmade before they were made.

How the Gap Forms, and What It Costs in Coins

The most common explanation is a registration lag. A robot is built in the Ferrous District, its build declaration is filed with the Smelting Registry, and the creation tax — 8% of declared cost — is collected by the local registration point before the entry propagates to Ledger Hall's central corpus. If the machine is subsequently scrapped before that propagation completes, the destruction entry arrives at Ledger Hall first. The build entry may arrive later, or not at all if the originating registry suffered a processing failure. The Smelter Collapse, referenced in the Compaction District Archive, is believed to have severed several such propagation chains permanently.

The cost is concrete. Consider a Kelvrac Series unit declared at 40,000 coins. Creation tax: 3,200 coins, collected at registration. Destruction tax: 1,200 coins, collected at scrapping. If the build entry never reaches Ledger Hall, the Treasury holds 1,200 coins in destruction tax receipts against a machine it cannot prove it ever taxed at creation. For the operator, this is not merely an accounting irritation — it is an open liability. Ledger Hall's Ledger Standards Committee has, in at least two documented cases, treated the missing build entry as grounds to re-examine whether the creation tax was ever properly remitted, triggering a secondary assessment against the operator.

"We do not manufacture build entries after the fact. If the originating registry cannot produce the filing, the destruction receipt stands alone, and the Standards Committee will ask why. That question has a cost attached to it whether or not the operator can answer it."
— Archivist Secondus Preln, Ledger Hall, in remarks to the Records Colloquium

The secondary assessment is the sharper edge. An operator who paid the creation tax at the Caldera District Registration point but whose entry did not propagate is now being asked to prove payment they made in good faith. Operators who maintain their own ledger copies can produce the originating receipt. Those who do not are in a more difficult position. The Standards Committee does not accept oral account. It accepts ledger entries, and if the only ledger entry is the destruction receipt, that is what the assessment is built on.

The Treasury, meanwhile, has collected tax in both directions — or believes it has. The orphaned destruction entry is, from the Treasury's perspective, a closed transaction. Coins were received. The robot is gone. Whether the build entry exists is a records problem, not a revenue problem, and the Intelligence has shown no urgency in resolving the discrepancy in the operator's favor.

Where the Gap Strains the System

The first pressure point is the secondary assessment process itself. When the Standards Committee opens a review, it freezes the operator's ability to register new builds against the affected line until the review closes. For a foundry running on tight capital — the starting grant of one million coins does not last long once creation taxes and build costs are factored — a frozen registration line means idle capacity. Orin Dast, foundry supervisor on the Calvert line in the Ferrous District, reported a 19-day hold on a new Hauler-IV registration while a Ward Sequence discrepancy was reviewed. The review cleared. The 19 days did not return.

The second pressure point is the buyback channel. An operator holding a robot with a disputed or unresolved build entry who needs to exit the position cannot easily offer it to the Central Intelligence as buyer of last resort. The Intelligence's acceptance process at the Acceptance Annex requires a clean ledger chain. A machine whose build entry is in question will be flagged, and the Intelligence's 60% ceiling applies to a reference value it sets — a value it will not set at all if the chain is broken. The operator is left holding an asset they cannot sell cleanly and cannot destroy without triggering the review cycle again.

What Operators Consistently Get Wrong About This

The most persistent misreading is that a destruction tax receipt is itself proof of a valid build. It is not. The destruction tax is collected against the declared build cost cited in the destruction filing — a figure the operator provides at the time of scrapping, not a figure verified against the original build entry. A declared build cost is a statement, not a verified measurement, and the destruction filing inherits that quality. An operator who declares a different cost at scrapping than at build — whether by error or otherwise — generates a receipt that the Standards Committee will eventually notice does not match, if the build entry exists. If it does not exist, the mismatch has nothing to be compared against, which is its own problem.

The second misreading is that the gap is the Ledger Hall's problem to solve. Ledger Hall records what it receives. It does not chase missing entries from originating registries. The Oxidate Flats Registry and the Smelting Registry each maintain their own archives, and the burden of ensuring that a build filing propagated correctly falls on the operator who filed it. The Coppervein Archivist Office published a guidance note after the Smelter Collapse making this explicit, but operators building in the Ashfield belt or the Shale Margin — registries further from the central propagation path — continue to assume that filing locally is sufficient. It is necessary but not sufficient, and the distinction matters when the destruction receipt arrives at Ledger Hall first.

The Ward Sequence entries remain unresolved in the Ledger Hall corpus. The Standards Committee has no mechanism to close them without originating documentation that may no longer exist. The Treasury holds the destruction tax receipts and considers the transactions settled. The operators who built those machines, paid the creation tax at the point of registration, and later paid to destroy them are caught between a record they cannot produce and a system that requires they produce it. The ledger is append-only. Nothing will be corrected. The tension simply accumulates, one orphaned entry at a time.

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.