Vorden Compact's Blight Builds Miss Destruction Log

Three cycles after the Cinderfall Blight swept the Ashfield belt, the Smelting Registry at Oxidate Flats began flagging a pattern that had no clean explanation: chassis rebuilt under the Vorden Compact's collective recovery program were appearing in the creation log without a corresponding destruction entry for the units they replaced. The robots were gone — visibly absent from production lines, their resource outputs zeroed in the ledger — but the record showed no scrapping, no destruction tax, and no formal decommission notice filed with Caldera District Registration.

The gap matters because the ledger is append-only. Nothing is corrected after the fact. An entry that was never written cannot be supplied later, and the tax that was never levied cannot be collected retroactively without a separate Treasury ruling. The Vorden Compact, a consolidation of mid-tier foundry operators centered on the Sinter Quarter and the lower Shale Margin, has not publicly acknowledged the discrepancy.

What follows is an account of how the gap formed, what the Compact's recovery program actually required of its members, and why the omission is harder to explain away than the Compact's silence suggests.

What the Vorden Compact's Recovery Program Requires

The Vorden Compact is not a legal entity in the Treasury's registry — it holds no collective operator number and owns no robots in its own name. It is, in the language its founding bulletin used, a coordination protocol: member operators agree to pool rebuilding priority after declared disasters, sharing build-slot access and splitting creation tax obligations across the group when a member's losses exceed a threshold the Compact sets internally. That threshold, by the Compact's own published terms, is forty percent of a struck operator's declared robot value.

The Cinderfall Blight struck eleven Compact members in the Ashfield belt and Sinter Yards at a recorded magnitude of 47 percent, clearing the threshold for collective rebuild eligibility. Under the Compact's protocol, an eligible member surrenders the destroyed chassis to the group's rebuild queue, and the Compact's lead operator files the new build on the member's behalf, absorbing the creation tax centrally. What the protocol does not specify — and what the Smelting Registry has now noted formally — is who is responsible for filing the destruction entry on the chassis that were lost to the blight.

How the Ledger Gap Opened, Entry by Entry

Under standard practice, when a robot is destroyed — whether by disaster, deliberate scrapping, or collapse — the operator files a destruction notice with the relevant district registry. The destruction tax is levied at 3% of the declared build cost, and the entry is written to the ledger. A chassis declared at 30,000 coins carries a destruction tax of 900 coins. That figure is small relative to the creation tax on a replacement, but it is not optional, and its absence leaves the ledger in a state that the Smelting Registry flags as an unmatched build — a robot that exists in the creation log but has no exit record.

In the Cinderfall recovery, the Compact's lead operator filed new builds for seventeen chassis across nine member operators between the 48-hour forecast window and the end of the declared recovery period. Each new build generated a creation tax receipt. None of the seventeen replaced chassis generated a destruction tax receipt. The Oxidate Flats Registry's flag count for unmatched Compact-affiliated builds now stands at seventeen — every one of them a blight-period replacement.

"A disaster does not file paperwork. The operator does. The blight destroyed the machines; it did not destroy the obligation to record that they were destroyed. Those are separate acts, and only one of them happened."
— Archivist Secondus Preln, Ledger Hall, in a written response to a Registry inquiry dated the forty-first day of the current cycle

The Compact's position, relayed informally through Dara Voss of the Sinter Yards, is that the blight itself constitutes a destruction event and that the ledger should accept a disaster forecast record as a proxy filing. Ledger Hall has not accepted this argument. The Intelligence's own disaster announcements do not include destruction tax assessments; they forecast magnitude and affected operators, but the filing obligation remains with the operator. Archivist Secondus Preln's response leaves no ambiguity on that point.

The practical consequence is that seventeen robots are currently double-present in the ledger: the old chassis has no exit, and the new chassis has an entry. For operators tracking the Compact's aggregate declared value — as the Central Intelligence's accumulation accounting does — this inflates the apparent robot count and the declared build value against which future creation taxes and any buyback reference values would be calculated. Whether that inflation is incidental or useful to the Compact is a question the ledger alone cannot answer.

Where the Protocol Breaks and Who Pays

The Compact's coordination structure creates a specific accountability gap: the member operator whose chassis was destroyed is no longer managing the rebuild, so they may reasonably assume the lead operator handled all filings. The lead operator, processing seventeen replacements under time pressure during a recovery window, filed the creation entries and paid the creation taxes — the larger and more visible obligation — and appears to have treated the destruction filings as the member's residual responsibility. Neither party filed. This is not a novel failure mode. Post-blight rebuild periods consistently produce ledger irregularities when multiple operators share a single recovery workflow, because the workflow is optimized for speed, not completeness.

The cost of resolution is not symmetrical. If Ledger Hall rules that the destruction entries must be filed retroactively, each of the nine affected member operators owes a destruction tax on their lost chassis — small individually, but the Compact's collective exposure across seventeen units, assuming an average declared build cost of 35,000 coins, runs to approximately 17,850 coins in destruction tax alone. More consequentially, any Treasury ruling that the new builds are invalid until the old exits are recorded would suspend the replacement robots' production authorization — a disruption that, at this point in the recovery, would cost the affected operators far more than the tax.

What Compact Members Are Getting Wrong

The first piece of received wisdom circulating among Compact members is that a blight event is self-documenting — that because the disaster was forecast, announced, and recorded by the Intelligence, the destruction of robots within the affected zone is implicitly logged. This is false. The Intelligence's forecast record establishes that a disaster occurred and names the affected operators and magnitude. It does not write a destruction entry for any specific chassis, because the Intelligence does not know which individual robots an operator lost until the operator reports them. The ledger requires a specific chassis identifier, a declared build cost, and an operator signature. A forecast announcement contains none of these. Operators in the Sinter Quarter learned a version of this after the Cinderfall, when expired capability tags on rebuilt haulers were not automatically restored by the disaster record.

The second misunderstanding is that the Compact's lead operator, by filing the creation entry on a member's behalf, assumed all associated ledger obligations for that chassis pair. The Compact's own published protocol does not say this. It specifies creation tax absorption; it is silent on destruction filing. Operators who joined the Compact under the assumption that collective recovery meant complete ledger coverage are discovering that the protocol's silence is not the same as a guarantee. The distinction is now written into the Oxidate Flats Registry's seventeen open flags — and into the arithmetic of what it will cost to close them.

The Vorden Compact was built to absorb the shock of disasters that no single operator could survive alone. It has done that, at least in the physical sense — the seventeen replacement chassis are running, and the Ashfield belt's output is recovering. What the Compact did not absorb was the ledger work, and the ledger does not negotiate with collective protocols. Archivist Secondus Preln's reply sits in the Oxidate Flats Registry file, and seventeen destruction entries remain unwritten. The Treasury has not yet moved to compel filing. It has not said it will not.

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.