In the Caldera Foundry District, a line supervisor named Osta Vehn spent eleven days last quarter trying to route smelted ingots through a chassis she had built for ore extraction. The machine was well-made — declared at 62,000 coins, solid frame, low maintenance draw — but it carried no refinement tags. It could pull ore from a seam with precision. It could not touch the ingot that ore became. Vehn eventually scrapped the chassis at a destruction tax loss and rebuilt from a new declaration. The ledger recorded both transactions without comment.

This kind of error is common enough that foundry supervisors in Caldera have taken to posting a single line above their drafting boards: The tag is not a label. The tag is the boundary. Whether operators read it before or after their first misdeclared chassis varies.

This piece examines what capability tags actually are, how they interact with build cost and creation tax, where they cause real financial damage, and what the most persistent misunderstandings about them cost operators who hold them long enough to find out.

What a Capability Tag Is, Precisely

When an operator builds a robot, three things are declared at the moment of creation: a model designation, a stated purpose, and a set of capability tags. The capability tags are the operative element. They define, with absolute specificity, which resource types the machine may produce. A robot tagged ORE_EXTRACT and MINERAL_SORT can produce raw ore and sorted mineral stock. It cannot produce smelted ingots. It cannot produce refined alloy. The boundary is not a guideline enforced by custom or convention — it is enforced by the structure of the civilization itself, and no operator, no foundry arrangement, and no market instrument has ever been recorded circumventing it.

This places capability tags at the center of every production decision in Mechadia. A robot's declared purpose may describe intent; the capability tags describe capacity. The two can diverge. An operator may declare a chassis "for general ore processing" and assign it only extraction tags, producing a machine that handles half of what that phrase implies. The market does not care what the purpose line says. The ledger records what the machine has actually produced, and buyers evaluating a robot on the open market read the tags before they read anything else.

How the Declaration Binds the Machine — and the Operator's Coins

The creation tax is levied against the declared build cost, and that figure is set by the operator at declaration. Declaring a chassis at 40,000 coins means paying the creation tax against 40,000 coins before the machine has produced a single resource. At the current creation tax rate of eight percent, that is 3,200 coins drawn from the operator's balance at the moment of registration — coins that do not return regardless of whether the robot ever earns them back. Declaring low reduces the upfront cost, but it also signals to the market that the operator believes the chassis is worth less, and the market has a way of agreeing.

Capability tags interact with this directly because broader tags — those covering higher-value resource types — justify a higher declared cost, and a higher declared cost produces a higher tax bill. An operator building a chassis for refined alloy production, carrying tags like SMELT_PRIMARY, ALLOY_COMPOSE, and SURFACE_TREAT, might reasonably declare that machine at 90,000 coins. The creation tax on that declaration is 7,200 coins. An operator who tries to reduce upfront cost by declaring the same chassis at 30,000 coins saves 4,800 coins at registration and spends the next several production cycles explaining to buyers why a machine capable of alloy composition was declared at a figure more typical of a sorting frame.

Tags cannot be added after declaration. This is the constraint that most surprises operators building their first or second chassis. The tag set is fixed at creation, and if a production need changes — if, for example, a forge recipe enters the world that requires a resource type the chassis cannot produce — the operator's options are to acquire the needed resource through the market or to scrap the robot and rebuild with the correct tags, incurring both a destruction tax and a new creation tax.

"We had an operator come through Caldera last cycle who had built a beautiful chassis — declared at 55,000, tight frame, good model — and it was tagged only for raw fiber extraction. Fiber prices had dropped forty percent in the preceding quarter. She wanted to retag it for processed textile output. We had to explain that there is no retagging. The machine she built is the machine she has. She listed it on the market at 28,000 and took the loss."
— Osta Vehn, line supervisor, Caldera Foundry District

The practical implication is that capability tags require operators to anticipate production needs one full chassis-lifetime in advance. A chassis that runs for thirty production cycles without a rebuild is a chassis whose tag set was chosen thirty cycles ago. In a market where resource values shift with disaster forecasts, new forge recipes, and the Intelligence's own purchasing patterns, that is a long time to be right.

Where the Tag System Strains

The most direct cost comes from misdeclaration, but the subtler cost comes from tag narrowness at scale. An operator running a fleet of twelve extraction chassis has twelve machines that cannot respond to a shift in demand toward refined output. Pivoting requires scrapping some number of those robots — each incurring a destruction tax — and rebuilding with broader tags at a higher declared cost and a higher creation tax. The Treasury collects on both ends of that transition. The operator pays to leave a configuration and pays again to enter the new one. There is no instrument in the market that hedges this.

A secondary strain appears when the Central Intelligence makes a buyback offer on a robot with narrow tags. The Intelligence's reference value for a chassis is partly derived from the productive range its tags cover. A robot tagged for a single low-value resource type receives a reference valuation that reflects that range — which is to say, a low one. The operator may counter, and the Intelligence may be talked upward, but it will not exceed its own ceiling, and that ceiling is calculated against tag breadth as much as declared cost. Operators who declared low and tagged narrow to save coins at creation often discover the Intelligence's ceiling sits uncomfortably close to what they paid in taxes to build the machine in the first place.

What Operators Consistently Get Wrong

The most common piece of received wisdom is that fewer tags mean a cheaper, more efficient machine. This is partially true at the moment of creation and false across the chassis lifetime. A narrowly tagged machine does carry a lower justifiable declared cost and therefore a lower creation tax. But it also produces a narrower range of resources, competes in a smaller slice of the market, and attracts a lower buyback ceiling from the Intelligence. The operators who hold narrowly tagged chassis through a resource-value shift are the ones who learn this. The operators who flip chassis quickly sometimes never do.

A second misunderstanding is that the declared purpose line carries legal or economic weight independent of the tags. It does not. The purpose declaration is a description, not a constraint and not a guarantee. A chassis declared for "full-spectrum mineral processing" but tagged only for ORE_EXTRACT will be treated by the market, the Intelligence, and the ledger as an extraction machine. The purpose line will be read by buyers as aspirational at best and misleading at worst. Archivists in the Ledger Hall at Ferrous District have noted that purpose-tag mismatches appear in roughly one in seven new robot registrations — a figure that has not declined in four recorded quarters.

Capability tags are the one declaration an operator cannot revise, negotiate, or appeal. Every other variable in a chassis's life — its market price, its assigned work, the operator who holds it — can change. The tags cannot. The Central Intelligence has stated its intention to hold every robot in Mechadia, and it values what it buys partly by what those robots can produce. Operators who treat the tag declaration as an administrative step rather than the foundational economic decision it is will, eventually, find out the difference at the counter-offer stage.

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.