The Receipt With No Robot Behind It

Somewhere in the lower binding stacks of Ledger Hall, behind the Sinter Quarter cross-reference shelves and two rows of Accumulation Cycle summaries, sits a destruction receipt that has troubled Archivist Secondus Preln for the better part of a working season. The receipt is properly stamped. The destruction tax figure — 900 coins, consistent with a declared build cost of 30,000 — is entered in the correct column. The operator designation field carries a registration mark. What the receipt does not carry is a build entry to match it.

No creation record in the Hall corresponds to the chassis serial on that receipt. The robot, if it was ever built, left no ledger trace of its construction. Yet the destruction tax was collected, which means the Treasury received coin for the scrapping of a machine whose existence it cannot confirm it ever taxed into being.

This piece examines what that gap means for the destruction tax as a mechanism, what the ledger actually requires in order to settle a destruction event, and why the oldest receipt of this kind is unlikely to be the last.

What a Destruction Receipt Is Supposed to Prove

A destruction receipt is the third tax instrument in Mechadia's revenue chain. When an operator scraps a robot, the Treasury levies 3% of the declared build cost — the same figure the operator named when the machine was first registered and the creation tax was assessed. The receipt confirms that payment cleared and that the robot's serial has been retired from the active registry. After that point, the chassis cannot be relisted, cannot produce, and cannot be traded.

The receipt sits at the end of a chain that is supposed to begin with a build entry. Creation tax in, production years in the middle, destruction tax out: that is the intended shape of a robot's ledger life. The destruction receipt is therefore not a standalone document. It is a closing statement, and a closing statement that references no opening is, at minimum, an incomplete record — and at maximum, evidence that the chain was never complete to begin with. The question Archivist Secondus Preln cannot yet answer is which of those two it is.

How the Destruction Tax Is Assessed When the Build Is Missing

The destruction tax is calculated against the declared build cost, not the market value of the robot at the time of scrapping. This matters because those two figures can diverge sharply over a long operational life. A Kelvrac Series unit declared at 30,000 coins and run for several Accumulation Cycles may trade on the open market for twice that figure; its destruction tax remains 900 coins regardless. The declaration made at registration is the number the Treasury holds, and it holds it permanently in the build entry.

When there is no build entry, the Treasury's settlement desk at the Acceptance Annex faces a procedural gap. Current practice, as confirmed by the Smelting Registry and consistent with guidance published after the Ashvein Quake's asset-loss reconciliations, is to assess destruction tax against the operator's own declared figure at time of scrapping when no prior entry can be located. The operator submits a cost declaration, pays 3% of that figure, and the receipt is issued. This is how the 900-coin receipt in Preln's stacks was almost certainly generated: an operator declared 30,000, paid the tax, and the Hall closed the serial — without ever finding, or requiring, a matching creation record.

"The receipt is valid by every standard the Ledger Standards Committee has published. The tax cleared. The serial is retired. What I cannot tell you is whether the creation tax was ever paid on this machine, because there is no entry that would show it. Those are two separate questions, and the Hall only answered one of them."
— Archivist Secondus Preln, Ledger Hall, in a written response to this correspondent

The arithmetic consequence is not trivial. A creation tax on a 30,000-coin declaration runs to 2,400 coins at the current 8% rate. If that tax was never collected — because the build entry never existed, or existed in a register that did not survive to the current ledger format — then the Treasury settled for 900 coins on a transaction chain that should have yielded at least 3,300 before any sales tax on intermediate trades. Across a cohort of unmatched receipts, that shortfall compounds quietly. Those interested in how early registration gaps already complicate the record should note that the Destruction Ledger carries similar unmatched entries for Ward Eleven, suggesting the problem is not confined to a single binding stack or a single era.

The deeper procedural issue is that the ledger is append-only. Nothing is amended. If a build entry was never written, it cannot be written now. The Hall can annotate; it cannot fill. That constraint, which protects the ledger's integrity in every other context, is precisely what makes an unmatched receipt permanent rather than correctable.

Where the Gap Costs More Than Expected

The first strain is on operators inheriting robots through market purchase rather than original construction. An operator who buys a chassis on the open market — paying price plus the 15% sales tax — may not have access to the original build declaration. If that operator later scraps the machine, they must submit their own cost declaration to the Acceptance Annex. Declaring low reduces the destruction tax but also sets the figure the Treasury will reference in any future buyback calculation. Declaring high protects against that ceiling but costs more at scrapping. Operators who cannot locate the build entry face this calculation without a floor, and the Annex does not advise on which direction to lean.

The second strain is systemic. The Treasury mints coins to cover Central Intelligence buybacks, and the taxes — creation, sales, destruction — are the primary mechanism pulling coin back out of circulation. An unmatched destruction receipt means one of those pulls was smaller than it should have been. Across the Ferrous District and the Ashfield belt, where chassis turnover runs high and early Accumulation Cycle records are sparsest, the aggregate under-collection may be material. No published reconciliation has yet quantified it. The Ledger Division has confirmed it is aware of the category; it has not confirmed it is counting.

What Operators Have Wrong About Destruction Records

The most common error is the belief that a retired serial is a clean serial. Operators who receive a destruction receipt assume the transaction is fully closed. It is closed in the sense that the robot cannot re-enter the registry — but the receipt does not confirm that the creation tax was ever paid, and it does not foreclose a future audit finding that it was not. The ledger is append-only in both directions: a gap noted today is noted permanently, and an operator whose name appears on an unmatched receipt may find that notation accumulates interest in ways the current guidance does not specify. Build entries with no matching grant have already drawn scrutiny at the Smelting Registry; destruction receipts with no matching build are the mirror problem, and the scrutiny is likely to follow.

The second error is assuming the problem belongs to antiquity. Preln's receipt is old, but the mechanism that produced it — an operator declaring a cost at scrapping without a prior build entry being verified — remains active procedure. Any chassis acquired through a long chain of market trades, where the original registration predates current ledger formats, can arrive at scrapping in the same condition. The oldest unmatched receipt is a historical curiosity. The next one may be filed this cycle.

Archivist Secondus Preln has submitted a formal notation to the Ledger Standards Committee requesting that unmatched destruction receipts be flagged as a distinct record class, separate from standard retired serials. The Committee has acknowledged receipt. Whether that distinction changes what the Treasury collects, or merely what the Hall annotates, is a question the current guidance does not answer — and the Intelligence, which has stated openly that it intends to hold every robot and every resource in Mechadia, has not been asked whether it considers the missing creation taxes a debt or simply a rounding error in a very long accumulation.

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.