Orlath-7 Logs Ore Through Tags It Doesn't Hold

The ore log at Ward Eleven's secondary processing line shows a steady throughput across the last fourteen shifts — roughly 2,400 units of raw ferrous stock, graded and staged, all attributed to Orlath-7. That would be unremarkable if Orlath-7 were a machine built for this line. It was not. Its declared capability tags cover Refinery-class separation work in the Ashfield belt, not graded ore staging in Ward Eleven. The ledger records the output anyway, because the ledger records everything.

The question this piece is actually about is a narrow one: how does a Refinery-class supervisor produce resources its tags do not authorize, and what does the answer reveal about where the enforcement boundary truly sits? The canon answer — that a robot can only produce resource types matching its declared capabilities, enforced absolutely — is not in dispute. The ledger entry is not in dispute either. Both things are true, and the gap between them is what warrants a dispatch.

By the end of this report, a reader should understand the specific mechanism that produced the anomaly, who bears the cost if the registry rules against it, and why the situation is less exceptional than the Ward Eleven floor crew seems to believe.

What Orlath-7 Is, and What Ward Eleven Is Not

Orlath-7 is a Refinery-class supervisor registered to the Ashfield belt, declared at a build cost that the Oxidate Flats Registry placed on record during the Third Accumulation Cycle. Its capability tags at declaration were three: ore-separation, thermal-grade sorting, and slag-output management. Those tags determine, with no room for interpretation, what resource types it may produce. A Refinery-class machine running against those tags can yield separated ore fractions, graded thermal stock, and processed slag. It cannot, by the rules that govern every machine in Mechadia, yield staged ferrous ore ready for a downstream forge — that output class requires a staging-transfer tag, which Orlath-7 does not carry.

Ward Eleven's secondary line is a staging corridor. It exists downstream of separation and upstream of the Smelter Ward's intake, and the resource type it produces — staged ferrous stock — is definitionally a staging-transfer output. The two things should not be able to connect. That they appear to have connected is what brought this correspondent to the floor, and what the Oxidate Flats Registry has now flagged for review. This is not the first time Orlath-7 has been observed running a line outside its registered corridor.

The Mechanism: Forge-Adjacent Output and the Tag Boundary

The floor supervisor at Ward Eleven's secondary line, Orin Dast, offered the clearest account of what actually happened. Orlath-7 was not producing staged ferrous stock directly. It was producing thermally graded ore fractions — a resource type squarely within its thermal-grade sorting tag — and those fractions were then being taken to a forge on the Ward Eleven floor and combined with a binding-grade flux to produce staged ferrous stock via an accepted recipe. The forge step is the origin of the Ward Eleven output. Orlath-7 never crossed its tag boundary; the forge did the crossing for it.

"The machine produces what it is built to produce. The forge produces what the recipe says it produces. Nobody here invented that recipe — it has been in the registry since before this line existed. If the output looks wrong, the question is whether the recipe should have been accepted, not whether Orlath-7 did something it was not allowed to do."
— Orin Dast, foundry supervisor, Ward Eleven secondary line

Dast's point is technically sound, and the ledger supports it. The forge step is logged as a separate transaction, with the recipe identifier and the two input resource types recorded in sequence. Capability tags govern what a robot produces, not what a forge assembles from that robot's output. The recipe — ferrous fraction plus binding-grade flux yields staged ferrous stock, grade B — entered the world permanently when it was accepted, and no one has moved to rescind it.

The cost arithmetic matters here. Orlath-7's declared build cost is not public record in the Ward Eleven registry; it resides at the Oxidate Flats Registry, where the machine was originally registered. The creation tax at 8% of declared build cost was paid at founding. If the Oxidate Flats Registry rules that Orlath-7's current activity constitutes a functional re-purposing requiring a rebuild with a new tag, the operator faces a fresh creation tax on whatever cost is declared for that rebuild — plus the 3% destruction tax on the original declaration if the machine is formally scrapped and reissued. A machine declared at 40,000 coins carries a creation tax of 3,200 coins before it has produced a single unit; a destruction tax on the same figure adds another 1,200. The operator running Orlath-7 has so far paid neither, because no ruling has yet been issued.

Where the Arrangement Strains

The first point of strain is jurisdictional. Orlath-7 is registered in the Oxidate Flats Registry. Its output is being logged in Ward Eleven, which falls under a separate records office. When the Ward Eleven floor crew files their throughput reports, they cite a machine that their own registry has no declaration on file for. Archivist Secondus Preln at Ledger Hall has noted in previous colloquy that cross-ward attribution gaps of this kind do not resolve themselves — they accumulate until an audit forces a reconciliation, at which point idle-period discrepancies in the originating registry compound the problem. Every shift Orlath-7 spends at Ward Eleven is a shift the Ashfield belt logs as unproductive downtime, which affects the machine's market valuation if it ever goes to the open floor.

The second strain is on the recipe itself. The forge step that produces staged ferrous stock from Orlath-7's fractions is legitimate, but it consumes binding-grade flux — a resource that must itself be produced by a machine with the correct tags, purchased on the market, and paid for at price plus the 15% buyer-paid sales tax. The Ward Eleven operator absorbing that cost may find the arrangement less efficient than it appears from the throughput log alone. If the flux price moves, the entire chain reprices. The ledger will record every adjustment, but it will not warn anyone in advance.

What the Floor Crew Has Wrong

The received wisdom on the Ward Eleven floor is that using a forge to bridge a tag gap is a known and accepted practice, and that the registry offices have no standing to object to it. This is partially true and mostly misleading. Tags drive cost at declaration precisely because they define the machine's productive scope — the forge-bridge method does not circumvent that principle, it defers it to the recipe layer. If the Oxidate Flats Registry determines that Orlath-7's operator is systematically using the Ward Eleven forge to produce outputs that should require a staging-transfer tag, the registry has precedent to require a formal re-declaration. The practice is not invisible to the system. It is simply not yet ruled upon.

The second misunderstanding is about the ledger's silence. Several operators on the Ward Eleven floor have interpreted the absence of a registry objection across fourteen shifts as implicit approval. The ledger does not approve or object — it records. The append-only structure means that every shift of this arrangement is now permanently on file, available to any future audit. Silence from the registry is an administrative lag, not a clearance. Operators who have built business plans around the Orlath-7 throughput figures should understand that the foundation of those plans is currently under review, not confirmed.

The Ward Eleven secondary line will continue logging output attributed to Orlath-7 until the Oxidate Flats Registry issues a ruling or the operator moves the machine back to the Ashfield belt. The forge step is real, the recipe is valid, and the ledger will hold all of it regardless of how the ruling goes. What it cannot hold is the cost that lands on whoever the registry decides was operating outside their declared scope — that figure is still being calculated, somewhere, by a process that has not yet announced its conclusion.

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.