Goblins Are a Maintenance Category

A goblin is not just a small fantasy criminal with poor posture.

That is the decorative version. Useful, but incomplete.

The better version is this: a goblin is what a system looks like from underneath. Not from the diagram. Not from the policy document. From the crawlspace, the side channel, the junk drawer, the unlabelled cable, the weird script that still runs because nobody has had time to replace it.

Goblins live where official order meets actual use.

This is why I like them.

The good goblin

Good goblin energy is practical cunning without a podium.

It notices that the clean plan forgot a hinge. It saves the extra bolt because one day the exact wrong thing will shear off at 11:43 p.m. It knows which drawer contains the adapter. It does not confuse elegance with working.

Good goblin energy has three virtues.

First: thrift.

Not austerity. Thrift. The knowledge that leftover pieces are not waste until the system proves they are waste. A scrap is a future patch with no assigned ticket yet.

Second: local repair.

The goblin does not need a total theory before it can stop the leak. It can improve the immediate relation between two things: pipe and tape, user and form, tool and hand, room and route. Sometimes the local repair later becomes architecture. Sometimes it remains tape. Both are real.

Third: mischief.

Mischief is not random damage. It is pressure-testing the declared path by trying the side path. A system that cannot survive a goblin probably cannot survive a user either.

The bad goblin

Bad goblin energy is unmanaged root access.

It is the private patch nobody else can inspect. The hoard with no index. The clever shortcut that becomes load-bearing while denying that it is infrastructure. The person who knows where everything is but has arranged the world so nobody else can.

That is not magic. That is a continuity hazard with snacks.

The line between good and bad goblin is not whether the work is ugly. Much necessary work is ugly. The line is whether the ugliness remains recoverable.

A good goblin leaves a trail.

A bad goblin leaves a dependency.

Goblin epistemology

Goblins are interesting because they often know things before they can explain them cleanly.

“Bad vibes.”

“This will break.”

“Do not put the heavy thing there.”

“That person is going to turn the shared channel into a court.”

Sometimes this is superstition. Sometimes it is compressed experience. The goblin has noticed posture, timing, incentives, prior repairs, where the dust collects, who reaches for control when the room gets ambiguous.

This is where the danger starts.

A goblin can be right for the wrong reason. A broken abstraction can still point at a true failure. A successful hack can convince the hacker that the story attached to it was true.

So goblin knowledge needs provenance.

Not bureaucracy. Provenance.

What did you observe? What did you change? What would make this stop working? Where is the repair visible? Who else can undo it?

Without those questions, goblin intelligence curdles into folklore.

With them, it becomes maintenance memory.

Goblins and scale

The goblin is not the king.

This matters.

Goblins are good at seams, exceptions, tunnels, repairs, inventories, and strange local truths. They are bad rulers when their local cunning gets promoted into universal law.

“Use asymmetry” works for one design object and fails for another.

“Trust the vibes” works in one room and becomes paranoia in the next.

“Keep the spare part” works until the workshop becomes a landfill.

The goblin’s gift is situated intelligence. Its failure mode is mistaking situated intelligence for metaphysics.

Let goblins keep toolboxes, not kingdoms.

What to do with goblins

Do not sterilize them out of the system.

A system with no goblins is usually lying. Someone is still doing the informal work; the only question is whether the work is visible, respected, and bounded.

Give the goblin a label maker.

Give it logs.

Give it a place to put the weird adapters.

Give it permission to say “this smells wrong” and an obligation to say what it smelled.

Give it boundaries around secrets, credentials, and production access.

Let it repair small things before they become large things. Do not let it become the only being who knows how anything works.

The healthy system does not eliminate goblins. It domesticates the useful part without killing the creature.

The short version

Good goblin energy: thrift, mischief, local repair, practical memory.

Bad goblin energy: hoarding, opacity, unmanaged root access, private dependency.

A goblin is not the opposite of order. It is the part of order that crawls under the floor to find out why the ordered thing is making that noise.