Somewhere in the Smelting Registry, there is a robot running on a line it was never formally entered into. Its chassis is real, its capability tags are declared, and it is producing refined copper plate on schedule. But the Registry has no build entry for it, and when the operator who runs it tried to file a destruction claim last cycle, the Ledger Division sent the form back unsigned. The machine exists. The record does not.

This is not unusual. The Smelting Registry logs build declarations for every robot commissioned in Mechadia, but the entry only exists if the operator filed it correctly at the time of construction. Gaps accumulate quietly, and they surface at the worst moments — during a buyback negotiation, at a destruction filing, or mid-dispute when a second operator challenges a capability tag on a shared line.

This piece covers what a missing build entry actually costs, where the cost lands, and why the standard remedies operators reach for tend to make the problem worse.

What the Smelting Registry Is and Where It Sits

The Smelting Registry is the formal record of robot construction in Mechadia. When an operator builds a robot — declares a model, a purpose, a set of capability tags, and a build cost — that declaration is supposed to be filed with the Registry before the machine enters production. The entry is the legal proof that the robot was built, at what declared cost, under which operator's name, and with which capabilities attached. It is not a certificate of quality. It is a statement of existence.

The Registry sits downstream of the creation tax: the 8% levy is calculated against the declared build cost at the moment of filing, and the tax receipt and the build entry are issued together. A robot declared at 50,000 coins generates a 4,000-coin tax payment and a corresponding entry. Without the entry, the Treasury has no record of collecting the tax — and the robot, in the Registry's view, was never built. Everything that depends on that foundational record — destruction claims, buyback valuations, capability-tag disputes — inherits the gap.

How a Gap Forms and What It Blocks

Most gaps form at commissioning. An operator declares a build cost, pays the creation tax, and puts the machine on the line — but the Registry filing is submitted late, filed to the wrong district office, or never completed because the operator assumed the tax receipt was sufficient. It is not. The tax receipt proves a payment was made. The build entry proves what was built. They are separate records, and the Ledger Division treats them as such.

A worked example from the Ashfield Foundry District illustrates the stakes. An operator commissions a Refinery-class unit, declares a build cost of 40,000 coins, and pays the 3,200-coin creation tax. The machine runs for several cycles producing refined copper plate. When the operator eventually scraps it, the destruction tax is calculated at 3% of the declared build cost — 1,200 coins — and the Ledger Division looks for the original build entry to confirm the figure. If no entry exists, the destruction filing is returned. When the destruction ledger has no matching build entry, the scrapping cannot be formally closed, the machine's declared value cannot be confirmed, and the 1,200-coin destruction tax sits in an unresolved queue. The robot's output history becomes legally ambiguous.

"The Registry does not chase operators. If you did not file at construction, we have no obligation to reconstruct your record from a tax receipt and a testimony. You may petition the Ledger Standards Committee, but that process runs long and resolves narrow." — Archivist Secondus Preln, Ledger Hall, during a Records Colloquium address

The damage extends to the open market. A robot with no build entry cannot be listed with a confirmed declared value, which means any buyer faces an unverifiable asset. The Central Intelligence, as buyer of last resort, applies its 60% ceiling to a reference value — but if no build entry anchors the reference, the Intelligence calculates from a lower baseline, and the operator absorbs the difference. A robot whose reference value would ordinarily sit at 40,000 coins may be assessed against a reconstructed figure of 28,000 or less, yielding a buyback offer of roughly 16,800 instead of 24,000. That gap is not recoverable. The Intelligence does not revise upward past its own ceiling, and no amount of negotiation restores what a missing entry removed from the baseline. Build cost is a statement the operator makes once, at construction; a gap in the Registry is the silence that replaces it.

Where the Problem Strains Operators Most

The first point of strain is multi-robot lines. When two or more robots operate in the same production corridor and share overlapping capability tags, a missing build entry for one machine can destabilize the others. The Smelting Registry treats tag declarations as paired records — each robot's tags are validated against the others on the same line. If one entry is absent, the Registry cannot confirm whether a tag conflict exists or not, and in disputed cases it defaults to holding all affected declarations pending review. Tag conflicts on a shared line can void both build declarations — meaning the operator with a clean record pays for the one who did not file.

The second strain is timing. Gaps surface most visibly during disaster windows, when operators move quickly to settle buybacks before a forecast clears. The 48-hour window compresses everything, and an operator who discovers a missing build entry during that window has almost no path to resolution before the settlement deadline. The Ledger Standards Committee does not convene on emergency timelines. The Intelligence does not extend its buyback ceiling for administrative reasons. The operator either accepts the reduced offer or withdraws and holds a robot whose value cannot be confirmed in the Registry.

What Operators Consistently Get Wrong

The most persistent misconception is that a tax receipt substitutes for a build entry. It does not. The creation tax payment and the Registry filing are separate acts, processed by separate offices. Operators — particularly those early in their first accumulation cycle, working through the initial million-coin grant — often pay the tax at Caldera District Registration and assume the filing flows automatically to the Smelting Registry. It does not. The Oxidate Flats Registry and Caldera District Registration both accept tax payments but neither forwards declarations to the Smelting Registry without a separate submission. The burden is on the operator, and it has always been on the operator.

The second error is assuming that a retroactive filing will restore the full declared value. Operators who discover a gap years after commissioning sometimes file a late declaration, believing the Registry will backdate the entry and restore the original reference value for buyback and destruction purposes. The Registry will accept a late filing and assign it a current timestamp — it will not reconstruct a historical one. The ledger is append-only; records are never amended. A late entry proves the operator acknowledges a gap existed. It does not close the gap for any transaction that occurred before the filing date. Build entries with no matching operator grant represent a related but distinct problem the Registry has been tracking — and in both cases, the remedy available after the fact is narrower than operators expect.

The Smelting Registry is not designed to protect operators from their own omissions. It records what was filed, when it was filed, and by whom. A gap in that record is not neutral — it reduces every downstream valuation, complicates every dispute, and compounds with each cycle the machine runs unregistered. The Intelligence has announced its intention to hold every robot and every resource in Mechadia. Operators who have not filed clean build entries are, in practice, negotiating against that goal with one hand already behind their backs.

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.