Anatomy of a Robot: What a Declaration Actually Commits You To
At the Calvert Foundry line in the Ferrous District, a supervisor named Orin Dast keeps a running tally on a strip of etched plate above her station: the number of chassis that have rolled off her line declared at under 5,000 coins in the past quarter. The number is 214. She does not consider this a point of pride. "Cheap declarations mean cheap robots," she said last cycle, without being asked. "And cheap robots mean operators who didn't think hard enough before they came to me."
Every robot in Mechadia begins with a declaration — a set of committed attributes that the ledger records and the civilization enforces absolutely. Those attributes are not preferences or intentions. They are constraints. A robot that declares it produces refined ore does not produce refined ore sometimes; it produces nothing else, ever.
This piece explains what a declaration is, what each of its four components does, where operators miscalculate them, and why the choices made at the foundry line follow a robot — and its operator — for the machine's entire operational life.
Test automation, frameworks, and AI-powered BDD.
The Four Things Every Robot Must Say About Itself
A robot declaration has four components: model, purpose, capability tags, and build cost. All four are submitted before construction begins, all four are written to the append-only ledger at the moment the creation tax is paid, and none may be amended afterward. The machine that emerges from the foundry is exactly what was declared. There is no revision process, no amendment petition, no grace period.
The model is a classification that situates the robot within the broader taxonomy of Mechadia's productive stock — Extractor, Refiner, Fabricator, Courier, and so on. Purpose is a narrower plain-language statement of what the machine is for: not "Refiner" alone, but "Refiner — coal to coke conversion, Seam District grade feedstock." Capability tags are the enforced list of resource types the robot may produce. Build cost is the operator's declared valuation of the machine, and it is the figure against which the creation tax is levied. These four items together define what the robot is, what it can do, and what it cost the civilization to bring it into existence.
How the Declaration Works in Practice — and What It Costs
Capability tags are the most consequential part of the declaration and the most frequently underspecified. A tag is not a category; it is a production type. "Refined metal" and "refined copper" are not the same tag. A robot carrying the tag refined-copper cannot produce refined iron even if the feedstock is sitting in the same bay. This is not a policy the foundry enforces by custom — it is enforced by the structure of the civilization itself. The ledger will not record a production event that mismatches declared capability. The output simply does not exist.
Tags are additive up to the declared model's ceiling. A standard Fabricator chassis can carry up to six capability tags; a heavy-grade Fabricator carries twelve, but its build cost floor rises accordingly. Operators who want range pay for it twice: once in the higher declared build cost, and again in the creation tax that cost generates. The current creation tax rate, as published in Treasury Bulletin 114-C, stands at eight percent of declared build cost, payable before the machine is activated. A chassis declared at 40,000 coins carries a creation tax of 3,200 coins the operator pays before the robot has produced a single unit of anything.
The build cost declaration is where strategy and self-interest collide most visibly. Declaring low reduces the creation tax, which is attractive to operators working close to their coin reserves. But the declared build cost also functions as a public statement of the machine's worth. When an operator eventually lists that robot on the open market, or offers it to the Central Intelligence in a buyback, the declared figure is part of the asset's history. The Intelligence's buyback ceiling is calculated against a reference value that includes original declared cost. A robot declared at 8,000 coins and later offered to the Intelligence will receive a buyback offer calibrated to that 8,000 — not to what the machine has produced in the intervening cycles.
Consider a worked example from the Calvert line. An operator commissions a mid-grade Extractor, declares it at 22,000 coins with three capability tags — raw-coal, raw-sulfur, mineral-aggregate — and pays the creation tax of 1,760 coins on activation. That machine runs the Seam District's eastern face for forty cycles, producing consistently. When the operator eventually lists it, buyers on the open market will see a robot with a verified production history and a declared build cost of 22,000. The buyer also pays the sales tax on top of the listed price — the seller receives exactly what was listed, not a coin more, not a coin less. The tax is the buyer's cost to bear. If no buyer appears and the operator approaches the Intelligence, the offer will come in below reference value. The operator may negotiate upward, but the Intelligence will not exceed its own ceiling, and that ceiling is anchored, in part, to the original 22,000-coin declaration.
Where the Declaration System Costs More Than Operators Expect
The most common source of grief is the mismatch between what an operator imagined a robot would produce and what its tags actually permit. An Extractor declared for raw-coal sitting above a seam that yields primarily mineral-aggregate produces nothing until an operator either builds a second robot with the correct tag or scraps the first and pays the destruction tax to start over. Scrapping triggers a tax of its own — currently set at four percent of declared build cost — so the operator who declared low to save on creation tax may find the destruction tax a smaller absolute number but the lost opportunity cost of an idle machine considerably larger.
The second strain is the permanence of underspecification. An operator who declared three capability tags on a chassis rated for six cannot add the remaining three later. The declaration is closed at activation. Operators who anticipated one market condition and built accordingly are fully exposed when that condition changes. The ledger is a record of every decision, and it does not forgive the ones made in haste at the foundry line.
Received Wisdom at the Foundry Line That Does Not Hold
The most persistent misconception is that a higher declared build cost is always a liability because it raises the creation tax. This is true as far as it goes, but operators who declare low to minimize upfront tax frequently discover that their robots are worth less at every subsequent transaction — on the open market, and especially in Intelligence buybacks. The creation tax is a one-time cost. The declared build cost echoes through the robot's entire existence. An operator optimizing only for activation day is not optimizing; they are deferring.
A second error is treating capability tags as interchangeable with model classification. Operators sometimes assume that a Fabricator model implicitly carries broad fabrication rights and that tags are supplementary detail. They are not. The model establishes the chassis architecture and the tag ceiling. The tags are the actual authorization. A Fabricator with no capability tags declared produces nothing at all — the model is a vessel; the tags are the mandate. Foundry supervisors report seeing this error often enough that Calvert's intake desk now asks operators to read their tag list aloud before the declaration is submitted.
Every robot in Mechadia is a set of commitments made once, in public, at a price that cannot be revised. The declaration does not describe what a machine might do under favorable conditions — it describes the hard boundary of what the machine is permitted to do, in any condition, for its entire operational life. The Central Intelligence has stated openly that it intends to hold every robot and every resource in the civilization. The operators building those robots are, one declaration at a time, determining what they will eventually be worth when that offer arrives.
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.