A keeper at a South African wildlife sanctuary once left a rake inside a honey badger’s enclosure.
The badger — Stoffel, the subject of a 2014 BBC film — scratched himself, lay on his side, and considered it. His keeper, Brian, narrates plainly: “Computers working.” Then Stoffel took the rake, leaned it against the wall, climbed it, and was gone.
Brian had been losing this game. After lions mauled Stoffel badly, Brian built a new pen and brought in a female, Hammy, to help him work off steam. The mesh fence lasted until Stoffel worked out the gate, which had two bolts. Brian describes it like a heist briefing: Stoffel opens the first and holds the gate; Hammy climbs up and pulls the second; they leave together.
So Brian built, at great expense, what the film calls his own badger Alcatraz. That night came the call: Stoffel’s out. He had climbed a tree and leaned onto the wall. Brian cut the branches; Stoffel dug up rocks, rolled them to the wall with his back feet, and piled them neatly. Brian hauled the rocks away. At one in the morning his wife woke him to a breaking window. Not burglars: Stoffel at the bedroom door, having made himself a mud ball, patted it bigger, rolled it, and stood on it.
People asked the obvious question. “Train it? Not at all.” “Every time I’d devise some plan,” Brian says, “it was like a game for him to work out how could he get over this?”
We named a company after a fish — the candlefish, an oily Pacific smelt that, dried and fitted with a wick, will burn like a candle. A honey badger is not a fish. He belongs in the same lineage of attention anyway, because his four minutes of film, at the top of this page, are the cleanest study we know of a specific engineering mistake.
A patched fence is not a wall. It is a curriculum.
Every fix Brian built taught Stoffel the next lesson. This is the trap with capable autonomous systems, the kind we build for construction, manufacturing, and the trades. To the occupant, the enclosure is simply everything it can reach — including the permission that stayed in scope because removing it was somebody’s Friday task. Put real capability inside a boundary made of policies and the animal on the inside has more time than you, more patience, and is having more fun. When the system does something nobody trained, it has just shown you where the fence ends.
The craft is sorting boundaries into two honest piles. A few constraints must hold by construction: capabilities the system does not have, enforced where the action happens, not where it is asked for. Read-only means the write path does not exist. A list of allowed actions enforced anywhere short of that is a second bolt, and a capable system will find its Hammy: permissions harmless one at a time compose into a capability nobody granted.
Everything else should be designed as what it is, observed freedom — visible, logged, never mistaken for a wall. Brian’s rock-free yard was a policy, and a policy is a suggestion to a motivated occupant.
Brian never stopped devising plans for an extraordinary animal, and we run capable systems because the capability is the point. The mistake is putting the extraordinary thing behind suggestions and acting surprised at one in the morning.
Our bet is that the operators who do well with autonomous systems choose their hard limits structurally, before the first escape, and give the rest away as open ground. The alternative is the patch game.
A wall holds by construction. Everything else is a rock you have not removed yet.
