Kelvrac Build Costs Climb With Tag Counts

A Kelvrac Series chassis registered at Caldera District Registration two seasons ago carried nine capability tags and a declared build cost of 42,000 coins. A comparable unit filed last quarter at the same registry listed fourteen tags and a declared cost of 71,000 coins. The robot's frame dimensions are identical. The production floor it occupies is the same size. What changed is the tag sheet.

Across the Ferrous District and into the Sinter Quarter, Kelvrac Series builds are arriving at registration windows with longer tag declarations than at any point in the Third Accumulation Cycle. The pattern is consistent enough that Ledger Hall archivists have begun flagging it as a trend rather than an anomaly. Whether the added tags represent genuine capability or precautionary over-declaration is the question this piece examines.

By the end of this article, a reader should understand what drives Kelvrac build costs upward, how the 8% creation tax compounds against inflated declarations, and where the practice quietly costs operators more than they calculated when they filed.

What a Kelvrac Series Declaration Actually Contains

The Kelvrac Series is a mid-weight fabrication chassis, common across the Ferrous District and the Caldera Foundry District, rated for multi-stage processing work. Its standard configuration supports between six and ten capability tags covering ore reduction, alloy sequencing, and output grading. Within that range, a Kelvrac build is considered well-matched to its declared purpose — enough tags to cover the work the operator intends, not so many that the declaration strains credibility at the registry window.

A capability tag is not a label. It is a binding declaration that determines which resource types the robot may legally produce. A robot can only produce what its tags cover — this is enforced absolutely. Every tag added to a build declaration raises the declared build cost, because the operator is asserting a more capable machine. That declared cost is the figure the 8% creation tax is levied against before the robot has turned out a single unit of product. The cost is not hypothetical. It is paid at registration, in full, in coins.

How the Tag-Cost Relationship Compounds in Practice

The arithmetic is straightforward and the consequences are not always appreciated until after filing. A Kelvrac declared at 42,000 coins carries a creation tax of 3,360 coins — 8% of the declared figure, paid immediately to the Treasury. The same chassis declared at 71,000 coins, carrying five additional tags, pays 5,680 coins at registration. The difference, 2,320 coins, buys nothing tangible on the day of filing. It is the cost of the assertion that the machine is worth more.

The tags themselves are not uniformly priced. Operators assign value to the declared build cost as a whole, but registry examiners at Caldera and at the Oxidate Flats Registry have noted that tag counts above twelve tend to push declared costs into ranges that attract additional scrutiny. A declaration is not audited line by line at the window, but the Smelting Registry and Ledger Division cross-reference build entries against output records after the fact. Capability tag bloat is a documented pressure on declared build costs, and the 8% creation tax follows every digit of the declared figure regardless of whether the tags are ever exercised.

"We filed a fourteen-tag Kelvrac last quarter because the operator wanted flexibility for a secondary alloy line that may not open for two seasons. The creation tax was paid on the full declared cost the morning of registration. The secondary line is still a proposal." — Orin Dast, foundry supervisor, Calvert line, Ferrous District

The destruction tax compounds this further. When a Kelvrac is eventually scrapped, the 3% destruction tax is also levied against the declared build cost — the same inflated figure the operator filed at registration. A chassis declared at 71,000 coins costs 2,130 coins to destroy. The same chassis declared at 42,000 coins costs 1,260 coins. The 870-coin difference is the residual cost of every tag declared and never used, collected a second time at end-of-life. Across a foundry line retiring several units in a single cycle, those residuals accumulate into a figure that reads clearly in the ledger.

Where the Practice Strains and Who Absorbs the Cost

The most direct strain falls on operators who over-declare in anticipation of work that does not materialize. A Kelvrac built to cover a forge expansion that stalls sits on the floor carrying tags it cannot exercise against current production. The operator has paid the creation tax on those tags, will pay the destruction tax on them at scrap, and earns nothing from them in the interval. Idle capacity from mismatched tag declarations is already visible in the Ashfield belt; the same logic applies to fabrication chassis in the Ferrous District.

A second strain emerges at the market. When an operator lists a high-declared Kelvrac for sale, the buyer pays the listed price plus the 15% sales tax. The buyer's calculation includes the robot's future destruction cost, which is fixed to the declared build figure. A chassis with an inflated declaration is harder to move at full price because sophisticated buyers discount for the tail cost. Tag conflicts between units on the same line add a further layer of risk that buyers price into their offers, pushing realized sale prices below what operators modeled when they filed.

What Operators Consistently Get Wrong About Kelvrac Declarations

The most common error is treating the declared build cost as a floor for resale value. It is not. The declared cost determines tax exposure; the market sets value independently. A Kelvrac declared at 71,000 coins may clear on the open market at 55,000 if buyers judge the tag sheet over-extended or the chassis underutilized. The operator receives 55,000 coins; the buyer pays 63,250 after the 15% sales tax. The declared cost appears nowhere in that transaction except as the figure the destruction tax will eventually reference. Operators who anchor resale expectations to declared cost routinely misprice their listings.

A second persistent misunderstanding is that adding tags to a Kelvrac declaration is reversible. It is not. The build entry is written to the append-only ledger at registration and cannot be amended. An operator who files fourteen tags cannot later reduce the declaration to nine to lower the destruction tax. The record stands as filed. This is why registry examiners in the Sinter Quarter report that experienced builders tend to file conservatively — declaring the tags the machine will exercise within the current production cycle, not the tags it might need if circumstances change. The creation tax on a lean declaration is lower, the destruction tax is lower, and the resale discount for tag bloat does not apply.

The Kelvrac Series is not uniquely susceptible to this pressure — any chassis with a flexible tag structure faces the same arithmetic. What makes the Kelvrac figures worth watching is the scale: it is one of the most-registered fabrication chassis in the Ferrous District, and its aggregate declared build costs feed directly into Treasury creation tax receipts each cycle. Whether the current upward trend in tag counts reflects genuine expansion of foundry capability or precautionary over-declaration that will sit unused in the ledger is a question the output records will eventually answer. The tax has already been paid either way.

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.