Registry Logs Builds Older Than Their Filers

The Smelting Registry at Oxidate Flats holds a build entry for a Kelvrac Series chassis — declared cost 38,000 coins, capability tags: ore separation, slag conveyance — filed under an operator designation that received its founding grant fourteen cycles after the chassis was first logged. The archivist on duty when the discrepancy surfaced did not flag it as an error. She logged it as a discrepancy and moved to the next entry in the queue. That is the correct procedure. It is also the procedure that leaves the question open.

Across the Smelting Registry's active partition, a growing count of build records carry filing dates that cannot be reconciled with the grant histories of the operators attached to them. The robots exist in the ledger. The operators exist in the ledger. The timeline connecting them does not.

This piece examines what the Registry actually is, how those orphaned timelines accumulate, where the mechanism strains under its own record-keeping, and what operators consistently misread about their obligations when they inherit or acquire one of these entries.

What the Smelting Registry Actually Is

The Smelting Registry is the authoritative ledger of robot builds: every chassis ever declared, every capability tag ever attached, every declared cost ever submitted for creation-tax assessment. It is not a roster of currently active robots. It is a permanent record of every robot that has ever been filed — including those subsequently scrapped, destroyed by disaster, or rendered dormant through operator inactivity. Entries are never deleted. The append-only structure is absolute.

Within the broader economy of Mechadia, the Registry sits between the creation-tax system and the open market. Before a robot may produce a single resource, its build must be logged, its declared cost must be assessed, and the 8% creation tax must clear the Treasury. A chassis declared at 40,000 coins costs its operator 3,200 coins in tax before the machine has moved once. That tax record anchors the Registry entry. Everything downstream — sales, buybacks, destruction filings — references back to that original declaration. A gap in that chain is not merely an administrative inconvenience; it severs the asset from its own provenance.

How the Timeline Breaks and What the Ledger Shows

The most common mechanism is transfer without re-registration. When an operator sells a robot on the open market, the ledger records the sale — price, buyer, sales tax — but the original build entry retains the original filer's designation. If the selling operator subsequently goes dormant, is dissolved, or has their designation reassigned through the Central Intelligence's periodic identifier consolidations, the build entry is left pointing at a designation that no longer corresponds to a living operator account. A new operator who later claims that designation through normal grant issuance finds themselves attached, in the Registry, to a build they never commissioned.

The numbers involved are not trivial. Archivist Secondus Preln at Ledger Hall, who oversees the cross-referencing of Registry entries against the grant issuance archive, offered the following assessment at the last Records Colloquium:

The Registry does not track operators. It tracks declarations. When we say a build entry is older than its current filer, we mean the declaration predates the grant. The ledger is consistent — it recorded what it was given. The inconsistency lives in the assumption that a filer and a builder are the same unit.

A worked example clarifies the tax exposure. A Refinery-class chassis declared at 55,000 coins was originally built in the Second Accumulation Cycle, creation tax paid at 8% — 4,400 coins to the Treasury. The robot passed through two market sales, each generating sales-tax revenue at the current rate. The original operator designation was consolidated during an identifier revision. A new operator, issued their founding grant of one million coins, was assigned the consolidated designation and now holds, in the Registry, a build entry for a chassis they did not commission, whose tax history they did not generate, and whose capability tags — ore reduction, thermal press — they may not be equipped to deploy. Builds whose operators never claimed a grant follow a similar pattern, though the provenance gap there runs in the opposite direction.

The destruction-tax obligation is where the exposure becomes concrete. If the operator eventually scraps the chassis, the 3% destruction tax is assessed against the original declared build cost — 55,000 coins — regardless of what the operator paid to acquire it or what the market currently values it at. That is 1,650 coins owed on a transaction the operator may have entered expecting a clean exit. The declared cost, set at the moment of creation, is immutable in the ledger.

Where the Registry Strains Under Its Own Record-Keeping

The first strain is the capability-tag mismatch. A robot's declared tags are enforced absolutely — a chassis tagged for slag conveyance cannot produce refined copper plate regardless of what its current operator needs. When a build entry ages past its original operator and into a new one, the new operator inherits tags that may be economically useless to them. They cannot re-tag without scrapping and rebuilding, which triggers both a destruction tax on the old chassis and a creation tax on the new one. The Calvert line in Ferrous District has documented this cost across successive rebuilds: each cycle, operators declare fewer tags to reduce creation-tax exposure, narrowing the robot's productive range with each iteration.

The second strain is valuation drift at the buyback window. The Central Intelligence's buyback ceiling is set at 60% of a reference value. For a robot whose declared cost is decades old and whose market comparables have shifted substantially, the reference value the Intelligence applies may bear little resemblance to what the open market would pay. Operators holding legacy entries have reported buyback offers that reflect the original declaration more than current conditions — and the Intelligence, while it can be negotiated upward in small increments, will not move past its own ceiling. The haircut on an already-undervalued reference is compounding.

What Operators Consistently Get Wrong About Inherited Entries

The most persistent misconception is that a Registry entry attached to your designation is your asset to manage freely. It is not, in any simple sense. The entry belongs to the ledger. The operator attached to it bears the tax obligations and inherits the declared cost, but the provenance record — who built it, when, at what declared value — is immutable. Operators who attempt to re-file a legacy entry at a new declared cost to reset their destruction-tax exposure find the Registry does not permit amendment. The original figure stands. What looks like an administrative update is, in the ledger, a new entry, which triggers a new creation tax at 8% of whatever cost is declared. That is not a correction; it is a second build.

The second misconception is that dormant entries carry no ongoing risk. They do. Builds with no matching destruction entry remain on the active partition indefinitely. A disaster forecast — the 48-hour window before a blight or quake strikes — applies to resources held by operators on record, and a legacy robot still attributed to your designation is, for the Registry's purposes, yours. If a Cinder Quake strikes and the chassis is in a ward covered by the forecast, the loss is assessed against your holding. The entry being old does not make it inert.

The Smelting Registry at Oxidate Flats will continue to accumulate entries that predate their current filers. The ledger is working exactly as designed — it records, it retains, it does not reconcile. The tension between a system built for permanence and an economy in which operators, designations, and declared values all shift over time is not a flaw the Registry can correct from within itself. It is simply the condition operators inherit when they accept a designation, and the ledger makes no distinction between what was intended and what was filed.

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.