Hullwalkers’ Strike

Event Type: Labor Safety Strike / Tech‑Fey–Backed Industrial Action

By the mature Commission period, most major torus habitats in the Inner Sphere had evolved thick layers of labor law, insurance tables, and “gremlin load” clauses that acknowledged tech‑fey as a real operational factor, not just superstition. On the fringes, though, rust‑bucket manufacturing tori tried to squeeze extra Yoms out of worn infrastructure by quietly ignoring those safeguards.

One such torus—half‑owned by a distant conglomerate and half‑mortgaged to an Ebon‑leaning cartel—ran its grav plates and outer ring structure past safe tolerances for cycles. EVA hullwalkers were the first to feel it: flex‑creaks in the ribs, unexpected micro‑lurches in pseudo‑gravity, and stress‑fracture readings that never quite made it into the official logs. When repeated complaints got buried under “productivity optimization” memos, the hullwalkers did the only safe thing left: they locked their mag‑boots and walked off the job, staging a safety strike across the outer hull.

Management’s response was classic Commission‑era denial. They:

  • Filed injunctions claiming the torus was “within spec.”

  • Brought in outside contractor crews to cross the line.

  • Disabled key inside control panels along dockside and maintenance corridors to keep striking workers from “tampering” with machinery.

They expected the usual slow bleed: replacement workers brought in under security escort, a few token repairs, and enough spin‑doctoring to keep insurers quiet. What they got instead was clangits choosing a side.


Clangits Lock the Torus

The torus’ resident clangits—tech fey bound up in crane housings, grav struts, and ore loaders—had lived for years in the ring’s overstressed bones. They knew, more intimately than any inspector, how close the habitat’s outer spine was to a bad day: winch housings hairline‑cracked, bulk ore loaders shuddering at the wrong harmonics, grav plates humming in angry, off‑beat tones.

When management tried to route around the strike, the clangits responded with their own form of direct action:

  • Every dockside winch and bulk ore loader on the ring failed, almost simultaneously.

  • Systems could not be cleanly powered down—whenever controllers tried a full shutdown, clangits would flick relays and mechanically jam linkages just enough to leave the machines in a flickering, fault‑state limbo.

  • Attempts to bypass damaged panels or re‑route control through remote consoles met a blizzard of minor, localized failures: popped breakers, misaligned limit switches, safety interlocks that refused to acknowledge “override” commands.

The result was a perfect logistical chokehold. Cargo arms froze half‑extended over vacuum. Grapples refused to hard‑lock. Ore hoppers hung just out of reach of the inner conveyors. To outside observers it looked like a cascading mechanical catastrophe, but maintenance techs on the ground saw the pattern: nothing was breaking beyond repair, but nothing could complete a full cycle either.

Out in local space, ore barges and contract haulers refused to dock once word spread that the torus’ winches and loaders were “gremlin‑hot.” No captain wanted their ship caught in the crossfire between angry hullwalkers, negligent management, and a resident clangit clan that clearly considered the dockside hardware part of the picket line.

Within days, cargo backlog and contract penalties threatened to bankrupt the torus’ owners. The insurers began drafting language around “failure to observe gremlin load limitations” as a contributing factor—language that could void coverage entirely if the situation was allowed to escalate.

Management capitulated.


The Non‑Hostility Compact

The settlement that ended the Hullwalkers’ Strike set three important precedents:

  • The torus recognized all EVA hullwalkers’ safety demands: grav plate replacement schedules, ring stress monitoring with third‑party verification, and binding limits keyed to established gremlin load thresholds.

  • The contract acknowledged a “Non‑Hostility Compact” toward resident clangits, committing management to:

    • Avoid deliberate attempts to purge or exterminate local tech‑fey.

    • Notify hullwalker and maintenance committees before major structural or systems changes.

    • Maintain certain “clangit corridors”—sections of dockside hardware left mechanically accessible so gremlins could continue their informal monitoring and “opinionated maintenance.”

  • In return, worker reps and sympathetic Chronologist consultants drafted best‑practice rules for interacting with clangits: no intentional baiting, no sabotaging their preferred stress‑relief paths, and an understanding that if gremlin load alarms started to manifest as mischief, it was a signal to scale back operations, not punish the gremlins.

The strike ended with the hullwalkers returning to carefully monitored shifts and the dockside machinery—still watched closely by their clangit “allies”—coming back online in stages.

From then on, union organizers across the Inner Sphere pointed to GD‑32.1.27 as proof that worker action plus gremlin pressure could move even ossified Commission‑era management. The phrase “Hullwalker terms” became shorthand for contracts that included both strong safety language and explicit non‑hostility clauses for tech‑fey stakeholders.


  • Gremlin Load Track:

    • As management or PCs push machinery past rated tolerances (extra shifts, over‑mass cargo, skipped inspections), a hidden or explicit Gremlin Load track advances.

    • At low levels: clangit mischief = early warnings (odd sounds, nuisance faults).

    • At high levels: coordinated shutdowns or limbo‑states like those seen in the Strike.

  • Union–Gremlin Influence:

    • PCs who win over hullwalkers and clangits gain circumstance bonuses to downtime actions related to strikes, negotiations, or targeted industrial pressure.

    • Failing to honor strike lines or harming tech‑fey can flip those bonuses into penalties as the ring itself becomes hostile.

Primary Functions in Campaigns:

  • A model for worker–gremlin alliances: PCs can court clangit support as part of labor disputes, sabotage jobs, or safety interventions.

  • A reason why many modern torus contracts include non‑hostility language toward anomalies and recognize them as de facto stakeholders.

  • A ready‑made flashpoint on any rusted torus: management that tries to roll back “Hullwalker terms” is courting both union and gremlin backlash.


The Hullwalkers’ Strike of GD‑32.1.27 turned a rusted torus into a legal milestone: proof that in the Commission age, real power on a habitat flows not just through contracts and control panels, but through the boots of EVA workers and the small stubborn hands of the gremlins who keep the hardware honest.

Significance

Contract Mediation: PCs serve as neutral troubleshooters or hired advocates during a new torus negotiation, using the Hullwalkers’ Strike as precedent. They might: Draft gremlin‑aware safety language. Investigate whether “random” failures are actually clangit pressure about ignored hazards.

 Safety Campaign Play: A long‑running torus arc might track the slow degradation of infrastructure, with the party helping hullwalkers collect evidence, win public sympathy, and coordinate with local clangits to stage non‑lethal slowdowns before a catastrophic failure.

Insurance Investigation: An insurer hires the party to verify a claim that “rogue gremlins” caused a dock disaster. PCs dig through logs and clangit behavior to determine whether management ignored established gremlin load clauses—and whether the hullwalkers’ position is justified.


Aftermath

In Commission‑era inner law, the Hullwalkers’ Strike is cited in commentaries on anomaly‑inclusive labor regulation: the moment when treating gremlins as mere pests became legally and economically untenable on major tori. Subsequent case law refines the idea that tech‑fey presence is part of the industrial ecology, with rights and expectations emerging from custom and precedent rather than formal personhood.

For unions and mutual aid networks, the event becomes a rallying myth. Organizers tell new crews:

“If the clangits hate your shift schedule, you should too.”

They treat gremlin mood as an early indicator of unsafe practices—if mischief spikes around certain cranes or plates, that’s an argument for slowdowns and safety audits, not harder quotas. Some union playbooks now include sections on “gremlin diplomacy”: learning favorite offerings, respected no‑go zones, and how to signal that a strike is about shared survival, not just pay.

Among clangits and anomaly‑savvy cultures, the Strike reinforces the notion that they can extract concessions without direct violence. Stories circulate of rings where gremlins blink warning lights in union colors, or where a single clangit quietly loosens the right series of bolts to make a scab crew reconsider crossing a line. Over time, this helps shift perceptions from “gremlins are random hazards” to “gremlins are an extra bargaining unit you ignore at your peril.”




GD‑32.1.27 Ignition 27