Sinter Quarter Haulers Moving Cargo Off-Tag

On the secondary run between the Sinter Yards and Loom Gate, a Hauler-IV designated Vorn-9 has logged forty-three cargo transfers in the past fortnight. Twelve of those transfers carried refined copper plate. Vorn-9's active capability tags do not include refined copper plate. The ledger records the transfers anyway, because the ledger records everything — and that is precisely the problem Sinter Quarter supervisors have been filing reports about since late in the Third Accumulation Cycle.

What is happening is not sabotage and it is not a clerical anomaly. It is a structural drift: haulers whose declared tags were written at build time are being routed to cargo categories those tags have since expired against, and neither the originating operator nor the receiving foundry is catching it before the run completes. The question this piece examines is how the gap opens, what it costs, and why it persists despite a ledger that is supposed to make every discrepancy visible.

By the end, a reader familiar with the Sinter Quarter runs will understand why tag expiry is not a single event but a gradual condition, and why the taxes that bookend a robot's life make correcting the condition more expensive than tolerating it.

What a Capability Tag Is and What It Is Not

When an operator registers a new hauler, the machine's declaration includes a set of capability tags — each one a precise statement of what resource types the robot may legally produce, carry, or process. The tags are not advisory. The Central Intelligence enforces them absolutely: a robot without the matching tag cannot complete a production action in that category. That enforcement is the foundation of Mechadia's resource accounting, and it is why operators treat tag selection at build time as a consequential decision rather than a formality.

What capability tags are not is permanent. A tag declared at build is attached to the robot's registered identity at that moment. Rebuilds, partial scrappage, and re-registration events can alter the active tag set — and each rebuild on the Calvert line has logged fewer tags than the one before it, a pattern that Archivist Pellane at the Compaction District Archive flagged in her last quarterly summary. The tag set that exists on the ledger today may bear only a partial resemblance to the one the operator originally filed, and there is no automatic notification to route supervisors when the gap widens.

How the Gap Opens on a Working Run

The mechanics are straightforward once you trace them. A hauler is built with a declared cost — say, 40,000 coins — and a tag set that includes, among other things, the resource class semi-processed ferrous stock. The creation tax of 8 percent is paid at registration: 3,200 coins to the Treasury before the machine has moved a single unit. The operator routes the hauler through the Sinter Yards to Loom Gate. For several cycles, the runs are clean. Then the operator partially rebuilds the chassis to reduce the destruction tax liability — declared build cost drops to 30,000, and in the re-registration, the semi-processed ferrous tag is not renewed. The new declaration costs 2,400 in creation tax and 900 in destruction tax on the retired configuration. The operator saves coins. The hauler keeps running the same route.

The route supervisor — often a machine like Orin Dast's Calvert line crew, or an independent like Ossin Tral in the Sinter Quarter proper — receives manifests from the originating yard, not from the Intelligence's registration index. Manifests do not automatically cross-check the hauler's current active tags. The hauler arrives, the cargo is logged, the ledger entry is appended. The discrepancy exists in the record, but it is not surfaced until an archivist or an audit run pulls the two records together.

"The ledger is append-only, which means the error does not disappear — it accumulates. By the time anyone queries it, Vorn-9 has forty runs of off-tag cargo sitting in the permanent record. Correcting the routing costs less than correcting the registration, so operators correct the routing last."
— Archivist Secondus Preln, Ledger Hall, responding to a Records Colloquium inquiry

The cost arithmetic is what keeps the gap open. Renewing the lapsed tag requires a re-registration event: the operator pays creation tax again on the declared build cost. At 30,000 declared, that is 2,400 coins paid before the tag is active. If the operator's hauler is running two or three cargo types on a mixed route, renewing a single lapsed tag may not justify the outlay — particularly when bids on the Span Market already stall at the point where Sinter Quarter tags expire, compressing the revenue available on those runs anyway. The rational calculation, run by the numbers, often favors tolerance over correction.

Compounding this, the sales tax structure means any market transaction to offload the hauler and replace it carries a 15 percent buyer-paid surcharge. A buyer acquiring a compliant replacement hauler listed at 50,000 coins pays 57,500 total; the seller receives 50,000. The operator replacing a non-compliant fleet unit therefore absorbs not just the new creation tax but the full cost of a market purchase. The Five-to-Fifteen Revision made fleet turnover measurably more expensive, and the Sinter Quarter runs — lower-margin than the Ferrous District trunk lines — feel that cost acutely.

Where the System Strains and Who Pays

The first point of failure is the receiving foundry. When Vorn-9 delivers off-tag cargo to a line in the Sinter Quarter, the receiving operator's production records show an input that the Intelligence may later flag as irregularly sourced. If the Intelligence initiates a buyback of any resource in that chain, the reference value it applies may be discounted on grounds of provenance ambiguity — the 60 percent ceiling on buyback offers can slide lower when the sourcing record is contested. The receiving operator, who had no knowledge of Vorn-9's tag status, bears that haircut. There is no indemnification mechanism. The ledger records the transaction; the loss is the receiver's.

The second failure is more diffuse. Off-tag logging distorts the route data that other operators use to price their own hauler capacity. A supervisor reading manifest volumes out of the Sinter Yards sees throughput numbers that include off-tag runs mixed with compliant ones. If she builds a new hauler on the assumption that the route supports a certain cargo mix, she may find her own compliant machine under-utilized — because some portion of the apparent demand was never legitimate cargo volume to begin with. The cost here is diffuse and invisible until the new machine is already registered and the 8 percent creation tax is already paid.

What Operators Tend to Get Wrong About Tag Expiry

The most common misconception is that a rebuild which does not explicitly remove a tag leaves the tag intact. It does not, reliably. Re-registration events require the operator to file a new declaration; what is not affirmatively re-declared is not carried forward automatically. Operators who have rebuilt chassis on the Cindergate line — as Orvane Tek's crew has done across three cycles — often discover on audit that tags they believed were continuous had in fact lapsed at the last re-registration. The ledger shows when each tag was last actively declared; the gap between that date and the current run date is the exposure. Tempered Lattice frames are particularly prone to this, because their rebuild cadence is high and their original tag sets are broad.

A second piece of received wisdom holds that the Central Intelligence will flag off-tag runs in near-real time and issue correction notices before damage accumulates. The Intelligence does eventually reconcile registration records against ledger entries, but the reconciliation is not continuous and it is not the Intelligence's primary concern on any given cycle. Operators who have waited for a correction notice before acting have found themselves holding a robot with dozens of flagged runs and a re-registration bill they could have paid at a fraction of the cost if they had acted at the first discrepancy. The ledger's permanence works against delay: each additional off-tag entry is another line the Intelligence will eventually read.

Vorn-9 is still running the Sinter Yards to Loom Gate route. Its operator has not filed a re-registration. The ledger continues to fill. At some point the Intelligence will reconcile the record, and the operator will face a choice between the cost of correction and the cost of a buyback offer priced against a robot whose provenance is, at minimum, complicated. Neither option will be cheap, and neither the ledger nor the Intelligence will have forgotten a single entry.

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.