A Kelvrac Series chassis registered at the Caldera District Registration last quarter carried fourteen capability tags. Its declared build cost was 91,000 coins. The same functional chassis — same output class, same throughput rating, same resource yield — had been built on the Cindergate Line two cycles prior with seven tags and a declared cost of 48,000. The difference in creation tax between those two declarations was 3,440 coins, paid before either machine had run a single production cycle.

The gap did not come from better materials or a stronger frame. It came from tags: each additional declared capability pushes the declared build cost upward, and the 8% creation tax is levied against whatever number the operator writes down at registration. The practice of loading a chassis with capability tags it may never exercise has a name in the Sinter Quarter — tag bloat — and it is costing foundry operators more than most of them have calculated.

This piece examines what capability tags actually are, why operators accumulate them past the point of utility, and what the arithmetic looks like when the Treasury collects its 8% at the moment of declaration.

What a Capability Tag Is and Where It Sits in the Declaration

When an operator registers a new robot, the declaration has three required components: a model designation, a statement of purpose, and a list of capability tags. The tags are not decorative. They are the enforced boundary of what a robot may produce. A chassis without a refined-metals tag cannot yield refined copper plate, regardless of what its frame was built from. The capability tag is the mechanism by which the Central Intelligence's production rules are enforced — not by custom or convention, but absolutely.

Each tag added to a declaration increases the robot's declared build cost, because a more capable chassis is, by the logic of the registration system, a more valuable one. That declared value is then the base against which the creation tax is calculated. The tags sit upstream of every coin the Treasury will ever collect from that chassis's existence — and also upstream of the destruction tax, which is 3% of the same declared figure when the machine is eventually scrapped.

The Arithmetic of Declaration: How Tag Count Drives the Tax Line

The Smelting Registry does not publish a fixed per-tag cost schedule. Declared build costs are set by the operator, not prescribed by the Intelligence. But in practice, operators pricing their declarations against market comparables — and against the cost of the components they actually consumed to build the chassis — tend to add between 4,000 and 9,000 coins to a declared build cost for each capability tag added beyond the functional minimum. That range is not official guidance; it is what the Coppervein Exchange's own survey of 200 recent declarations in the Ferrous District and Ashfield belt found across the Third Accumulation Cycle.

Consider a worked example from the Cindergate Line. Orvane Tek registered a mid-grade extraction chassis with a functional minimum of four tags and a declared build cost of 40,000 coins. Creation tax owed: 3,200 coins. A colleague on the same line registered a comparable chassis with nine tags — five of which were prospective, added against future forge recipes that had not yet been accepted — and declared 72,000 coins. Creation tax owed: 5,760 coins. The difference of 2,560 coins was paid at registration and is not recoverable. If those five prospective tags are never exercised, the operator overpaid by that margin before the machine moved.

"We see it on every new intake cycle. An operator builds a chassis they intend to grow into, tags it for six resource classes they hope to reach, and pays the tax on ambition. The ledger does not distinguish between tags in use and tags in reserve. It only reads the declared figure."
— Orin Dast, foundry supervisor, Calvert line, Ferrous District

The destruction tax compounds the problem. When a bloated chassis is scrapped — either because the prospective recipes never materialized or because the operator needed to recoup coin — the 3% destruction tax is levied against the same inflated declared cost. A chassis declared at 72,000 costs 2,160 coins to destroy. The same chassis declared at 40,000 would cost 1,200. The operator pays 960 coins more to exit a machine they overstated on entry. Both taxes flow to the Treasury; neither is subject to appeal or revision after declaration is filed.

The Intelligence has not moved creation or destruction tax rates since the Five-to-Fifteen Revision reset the sales tax from 5% to 15%. That revision, the largest single-step tax move on record, is the reference point operators still use when discussing rate risk. Creation and destruction have held at 8% and 3% respectively, but the base they are applied against — the declared build cost — is entirely within the operator's control at registration, which makes tag bloat a self-inflicted cost.

Where the Practice Strains: Sunk Costs, Scrap Economics, and the Buyback Floor

The first strain point is the buyback ceiling. When a bloated chassis fails to find a market buyer, the operator may offer it to the Central Intelligence, which pays 60% of a reference value — never the full amount, and never past its own ceiling. The reference value the Intelligence applies is not the declared build cost; it is a market-derived figure. A chassis declared at 91,000 coins but trading at 50,000 on the Coppervein Exchange will receive a buyback offer based on the lower number. The operator who inflated the declaration to reduce perceived tax per tag gets no credit for that inflation at the buyback window. The tax was paid against the declared figure; the buyback is calculated against market reality. The gap between those two numbers is the operator's loss.

The second strain point is recipe uncertainty. Capability tags added for prospective forge recipes carry full tax weight at declaration even though new recipes require acceptance before they enter the world permanently. An operator who tags a chassis for a recipe that is proposed but not yet accepted is paying an 8% creation tax on a capability that may never be valid. Archivist Secondus Preln at Ledger Hall noted in a colloquium filing last cycle that roughly one in five prospective-tag declarations reviewed by the Ledger Standards Committee involved at least one tag whose corresponding recipe remained unaccepted at the time the robot entered service.

What Operators Get Wrong About Tag Declarations

The most persistent misconception is that a higher declared build cost signals quality to market buyers and therefore commands a price premium when the chassis is listed for sale. This is not reliably true. Buyers on the Span Market and Coppervein Exchange pay the listed price plus 15% sales tax; they are not browsing declared build costs when evaluating a chassis. What they evaluate is output class, throughput, and which tags are actively in use. A chassis declared at 91,000 coins with six idle tags does not command a premium over a 48,000-coin declaration with the same active production profile. The declared figure is a tax base, not a quality signal.

The second misunderstanding is that tags can be removed after registration to reduce future destruction tax. They cannot. The declaration is filed to the append-only ledger and is not amended. Whatever the operator wrote at registration is what the destruction tax will be calculated against when the machine is scrapped. Operators who have absorbed this fact tend to approach the declaration form with more discipline than those who learn it at the scrap line. The Compaction District Archive holds a full record of every declaration filed in its jurisdiction; the ratio of active-to-declared tags on scrapped chassis is a number that foundry supervisors in the Sinter Yards have started tracking informally, and it is not flattering.

Tag bloat is not fraud and it is not ignorance — most operators who do it understand the mechanism well enough. It is optimism, priced in at registration and collected by the Treasury before the machine has run. The declared build cost is the one number in the system that the operator controls entirely, and the 8% creation tax means every digit of ambition has a fixed, immediate, non-negotiable cost. The ledger records what was declared. The market will later say what it was worth.

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.