Ferrous Builds Log Fewer Tags After Each Rebuild

The Calvert line in Ferrous District has been rebuilding the same Hauler-IV chassis series for three accumulation cycles. The first generation of that line declared an average of nine capability tags per chassis. The current generation declares six. Nobody issued an instruction to strip the tags. The line supervisor, Orin Dast, says the reduction happened one rebuild at a time, each time a tag that had not been exercised in the prior cycle was judged surplus to the declared build cost. The ledger confirms it.

This pattern — rebuilds logging fewer capability tags than the machines they replaced — has appeared consistently across the Ferrous District over the past cycle and a half. It is not confined to the Calvert line. Foundry records from the Smelter Ward and the Sinter Quarter show the same contraction. The question is whether the district is becoming leaner or whether it is becoming narrower.

By the end of this piece, a reader should understand the mechanism driving the contraction, where it is costing operators more than they calculated, and which pieces of received wisdom about tag counts are now working against the operators who still hold them.

What a Capability Tag Represents on the Rebuild Ledger

A capability tag is not a label. It is a binding declaration: the machine may produce only those resource types that match its declared tags, and that constraint is enforced absolutely at the point of output. Capability tags are the machine — remove a tag and you remove the corresponding productive capacity, regardless of what the chassis physically carries. When a robot is scrapped and rebuilt, its tag set is redeclared from scratch. Nothing carries over unless the operator writes it back in.

In the Ferrous District, rebuild declarations are filed with the Smelting Registry and cross-referenced against the prior registration. The Registry does not require an operator to match the previous tag count. It requires only that the declared cost be sufficient to cover the creation tax — currently eight percent of declared build cost — and that the tag set be internally consistent with the declared model. A Hauler-IV rebuilt at 40,000 coins pays a creation tax of 3,200 coins before the machine has turned a single output. What tags that machine carries is the operator's decision entirely.

How the Contraction Compounds Across Cycles

The mechanism is straightforward and its effects are cumulative. When an operator rebuilds a robot, the declared build cost is set against current market expectations for that chassis class. In a period when resource prices are soft — as they have been in the Ferrous District since the latter half of the Third Accumulation Cycle — operators under coin pressure tend to declare lower build costs to reduce the creation tax. A chassis declared at 30,000 rather than 50,000 saves 1,600 coins in creation tax. Over a foundry line of twenty machines, that is 32,000 coins recovered before a single resource trades.

The problem is that a lower declared cost creates pressure to trim the tag set as well. Tags are not individually taxed, but a chassis with nine capability tags implies a more capable and therefore more valuable machine. Declaring nine tags on a 30,000-coin chassis invites scrutiny from the Smelting Registry and from buyers on the open market who will price the machine against its declared worth. Operators have learned, informally, that tag counts and declared costs should roughly correspond. The result is that cost compression pulls tag counts down with it.

"We rebuilt the Kelvrac Series units in the Sinter Quarter last season at declared costs averaging 34,000. The prior generation ran at 47,000. We dropped three tags across the series — ore-sorting, slag-grading, and secondary refine. Those weren't idle tags. We just couldn't justify the declared cost to carry them."
— Ossin Tral, second-generation builder, Sinter Quarter

Tral's account matches what the Smelting Registry logs show across the district. The Calvert line's own rebuild record is the clearest single example: nine tags in cycle one, eight in cycle two, six in the current generation. Each step was individually defensible. The cumulative effect is a machine that can no longer produce three resource types its predecessor handled. Those gaps have to be covered by other robots, which either do not exist on the line or must themselves be built — at cost, at tax, and at whatever the market will bear for the missing output.

Where the Arithmetic Turns Against the Operator

The immediate saving is real. The deferred cost is also real, and it tends to arrive at the worst moment. When a stripped-down chassis needs to cover a tag it no longer carries — because a downstream forge recipe requires that resource type, or because a disaster has destroyed the one remaining robot on the line that held the tag — the operator faces a rebuild at whatever the current creation-tax rate and market conditions demand. The relationship between tags and declared cost means that adding tags back is not neutral: each additional tag pushes the defensible declared cost upward, and the creation tax rises with it. The savings from stripping are not banked against the cost of restoration.

A second strain falls on the destruction side. Scrapping a stripped chassis still draws the destruction tax — three percent of declared build cost — so an operator who rebuilt at 30,000 and now scraps to rebuild again pays 900 coins to exit and then faces a higher creation tax on the way back in. The operator who made three separate cost-trimming rebuilds has paid creation and destruction taxes at each step. The ledger records each transaction faithfully. The net outflow across three cycles of compression can exceed what a single rebuild at the original declared cost would have cost in full.

What Operators in Ferrous District Still Believe That Is No Longer True

The most persistent piece of received wisdom is that a lower declared build cost is a straightforwardly conservative move — prudent, defensible, low-risk. It is conservative in the narrow sense that it reduces the immediate creation-tax outlay. It is not conservative in any broader sense. A machine with fewer tags produces a narrower range of outputs. Narrower output means fewer listings on the open market, fewer resources available for forge recipes, and a chassis that is harder to sell if the operator needs to exit a position. The Intelligence's buyback ceiling — sixty percent of a reference value — is itself partly a function of what the machine can produce. A stripped chassis is a less valuable asset at every point of exit, including the one the operator controls least.

The second misconception is that tag counts in other districts are following the same trend, making Ferrous District's contraction a sector-wide normalization rather than a local problem. They are not. Caldera District continues to build wider — more tags per chassis than any comparable ward — and its operators have maintained declared costs to match. The Ferrous District's contraction is specific to it. Operators citing broader trends to justify local decisions are comparing against a baseline that does not exist in the current registry data.

The Smelting Registry will not intervene. It records what operators declare and taxes accordingly. The contraction in Ferrous District's tag counts is legal at every step, individually rational at every step, and producing a foundry floor that can do measurably less than it could two cycles ago. Whether operators will rebuild upward when coin conditions improve, or whether the stripped baseline will simply become the new normal, is not a question the ledger can answer. It only records what was declared.

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.