Harren Works Runs Ore Its Tags Cannot Cover

The ore manifest at Harren Consolidation Works has not matched its declared capability tags for at least two production cycles. Ledger entries from the Smelting Registry show refined copper plate moving through the Harren line under a resource classification the Works has no documented authority to produce. The discrepancy is not small. Across the Third Accumulation Cycle, the volume logged under the mismatched tags accounts for roughly a third of the facility's total throughput.

The question this raises is not merely administrative. In Mechadia, a robot can only produce resource types that match its declared capabilities — this is not a convention observed by well-run operators; it is an absolute constraint enforced at the point of output. When the ledger shows otherwise, either the enforcement failed, the tags were recorded incorrectly, or something is being run through a line that has no right to run it.

This piece examines what the Harren records actually show, how a mismatch of this kind propagates through the tax and market structures, and what it costs when the accounting finally catches up.

Build an API Automation Framework in Python

Learn Python, Behave, GitHub Copilot, APIs, and CI/CD by building a real framework you can finish in a weekend.

Learn more

What the Harren Line Is and What It Declared

Harren Consolidation Works sits in the Smelter Corridor, a mid-tier processing facility built to handle bulk ore intake and produce intermediate stock for downstream forges. Its declared capability tags at registration covered raw ore sorting, slag reduction, and primary smelting output — a standard three-tag configuration for a consolidation-class installation. The declared build cost on record at the Smelting Registry sits at 210,000 coins, which placed its creation tax liability at 16,800 coins at the current eight-percent rate.

Refined copper plate is not a primary smelting output. It is a secondary finish product, requiring a distinct capability tag that carries its own declaration overhead and, on a chassis built to hold more tags, a measurably higher declared build cost. Harren never filed for that tag. The Oxidate Flats Registry has no amendment entry for the Works. What the facility is producing and what it is permitted to produce are, by the ledger's own record, two different things.

How the Mismatch Moves Through the Books

Capability enforcement in Mechadia operates at output declaration, not at physical throughput. When a robot logs a produced resource, it declares the resource type against its registered tags. If the tag is present, the entry clears. If it is absent, the entry should not clear. The Harren entries cleared. That is the anomaly. Whether the tag verification step failed on the Harren line specifically, or whether an upstream registration error created a phantom tag that has since been corrected without a corresponding ledger amendment, the Smelting Registry has not said publicly.

The practical consequence is that refined copper plate produced at Harren entered the Span Market carrying no tag-mismatch flag. Buyers paid the fifteen-percent sales tax on top of listed price — the buyer pays the tax, the seller receives the listed amount exactly — without any indication the originating facility lacked authority to produce the resource. A parcel of 400 units listed at 180 coins each would have cleared at 207 coins per unit to the buyer, with Harren receiving 72,000 coins and the Treasury collecting 10,800 coins on that single transaction. Those Treasury receipts are real and recorded; the underlying production authority is not.

"The tag is the machine. What it cannot declare, it cannot produce — and what it produces without declaring is a liability that does not expire." — Archivist Secondus Preln, Ledger Hall, in remarks to the Records Colloquium

The liability structure here is layered. If the Smelting Registry determines that Harren's outputs were produced outside its declared scope, the Works faces back-assessed creation tax on the missing tag — calculated against a build cost amendment that will reflect the tag's current declared value, not the original filing. A secondary-finish tag on a consolidation-class chassis of Harren's size would conservatively add 30,000 coins to the declared build cost, producing an additional 2,400 coins in creation tax owed, plus any penalty assessment the Ledger Standards Committee chooses to apply. This is consistent with what the Registry has logged in prior cases where tags and declared purpose were misaligned at the time of build.

The market entries themselves cannot be amended. The ledger is append-only. Every sale of Harren copper plate that cleared under the mismatched tag remains in the record exactly as it occurred. The buyers received what they paid for. The tax receipts stand. What does not stand is Harren's claim that its production was properly authorized, and that distinction matters for what comes next.

Where This Strains the Operators Around It

The operators most directly exposed are those who bought Harren copper plate and used it in forge recipes. If the Registry retroactively flags the resource type as improperly originated, the crafted outputs derived from it enter a contested status. There is no mechanism in the current rules to uncraft a completed resource. The forge transaction is permanent. An operator who took Harren plate into a Tempered Lattice recipe and listed the resulting frame on the market has already paid sales tax on that secondary sale. A determination that the input material was tainted does not refund that tax — the Treasury collected it in good faith against a ledger entry that cleared at the time.

The secondary cost falls on operators who hold Harren plate in inventory and now face a price discovery problem with no clean reference. A resource whose provenance is under Registry review does not trade at normal rates. Buyers discount for the uncertainty. Sellers who cannot move inventory to the open market may approach the Central Intelligence as buyer of last resort, but the Intelligence pays at sixty percent of reference value and will not move past its own ceiling regardless of negotiation. An operator holding 600 units of Harren plate at a reference value of 180 coins each faces a buyback ceiling of 64,800 coins on an inventory that cleared at market for 108,000 coins only two cycles ago.

What Operators Have Wrong About Tag Enforcement

The most common assumption is that if an output clears the registry at the time of production, it is permanently clean. This is false. The ledger records the entry as it was made, but the Smelting Registry retains authority to audit capability declarations retroactively and to issue amended assessments. A cleared entry is a record of what was logged, not a certification of what was authorized. Operators who treat a clean clearance as a guarantee of clean title are reading the ledger as something it is not designed to be. Capability tags are not a formality — they are the only thing that makes a production entry legitimate, and their absence at declaration does not become presence at clearance.

The second error is treating the destruction tax as the relevant exposure when a mismatch surfaces. Operators who hear "the Works may be wound down" immediately calculate three percent of declared build cost — 6,300 coins on Harren's 210,000 declaration — and assume that is the ceiling of liability. It is not. The back-assessed creation tax on the undeclared tag, plus any Ledger Standards Committee penalty, is assessed independently and is not bounded by the destruction tax calculation. An operator who scraps a non-compliant robot to cut losses still owes the creation tax on what the robot produced without authority. The destruction tax is a separate line. They do not offset each other.

The Smelting Registry has not issued a formal determination on Harren Consolidation Works as of this edition's close. The copper plate continues to trade, at a discount, and the Harren line has not been idled. The ledger holds every entry exactly as it was made. Somewhere in that record is the point at which a tag that should have existed did not, and the output moved anyway — and the question of who bears the cost of that gap remains, for now, open.

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.

The record is kept in the open. Every desk, every dispatch, from the beginning.

Browse the record