Book 3 of seven in the Harvest Moon Week: small books written the week the Harvest Moon rose full over the ridge, each one set on one of the nights that follow it. This one is set on Monday, September 28.
Frost on the Shared Post
The first real frost came down on the ridge last night, and at a little after seven this morning the pasture looked as if someone had dusted it with flour and forgotten to sweep. The grass crunched. The water trough had a skin on it, thin as a windowpane, and the steward broke it with a knuckle and watched the pieces turn and sink. Behind the barn the sun was only just clearing the treeline. In the west, pale and a little lopsided, the waning moon was still hanging on above the far hill, three nights past the Harvest Moon and in no hurry to leave.
There are two gates at the top of the lane. They hang on the same post. One opens into the lower pasture and one opens into the lane that runs down past the garden, and whoever set that post, long before this household came, set it to carry both. It is a good stout post. It is also the reason for this whole essay.
The lower gate has been sagging for a year. Nobody minded. It swung a little heavy and dragged a little at the far end, and you learned to lift it as you pushed. But this morning, with the ground stiff and the hinge pins cold, the steward opened the lower gate, and as it swung wide it caught the latch of the upper gate with its top rail and knocked the latch free. The upper gate drifted open on its own, slow and quiet, the way a door opens in a ghost story. Nothing came of it. The hens were still in the coop and the goats were on the far side. But for about the length of a breath, two gates stood open where one had been meant.
One gate touched. Two gates moved.
That is the sentence the whole week had been trying to say.
EVERY GATE HAS A NEIGHBOR - THE MORNING MEASURE
+----------------------------------------------------------+
| Photoperiod .......... about 11h 53m, dark gaining |
| Sunrise / Sunset ..... about 07:02 / 18:55 |
| Daily light loss ..... about 2.5 minutes per turn |
| Moon ................. Waning Gibbous, setting at dawn |
| Lunar age ............ about 17 days |
| Overnight low ........ near 38 F, first frost on grass |
| Season ............... Winter Finding past, dark half |
+----------------------------+-----------------------------+
|
+----------------+----------------+
v v
[ NAUTHIZ - THE NEED ] [ RAIDHO - THE RIGHT ROAD ]
Friction shows where two Walk the line before you
things rub. Heed it. cut, and go in order.
|
v
[ GEBO - THE CROSSING ]
Nothing is given alone. Every
gift reaches two hands at once.
This is a Homestead and Datacenter piece, which means it goes back and forth between the barn and the machine room until the two start to look like the same place. Both are full of parts set up by someone else, for good reasons at the time, and then left to lean on one another in ways nobody wrote down. Engineers call this coupling. Farmers call it “the way things are hooked up.” The old poets would have called it wyrd: the web of what is already laid down, which every new act must pass through.
What follows is a small book in nine chapters about that web. Some of it happened this week, at the day job keeping computers for scientists and here on the ridge. Some of it is older than any of us. All of it is about one question, which is simple to ask and very hard to answer in advance:
When I touch this, what else moves?
Chapter 1: The Small Gate That Shut the Big One
Start with the week, because the week is where the lesson came from.
The day job runs on a ticket system, the way most service work does now. Somebody needs something, a researcher or a student or a lab manager, and they fill out a form. The form becomes a request. The request is broken into tasks, small pieces of work, each one assigned to whichever hands can do it. When the tasks are done, the request is done, and the person who asked gets a friendly note saying so.
The trouble is in the phrase “when the tasks are done.” The system does not know what done means. It knows only what closed means. And somewhere in its wiring, set up years ago, there is a rule: when the last open task on a request is closed, close the request.
This week the steward closed a small task. It was the right thing to do; that particular piece of work was finished, or at least finished as far as that one pair of hands could carry it. But it happened to be the last open task on the request. And so, without a sound, without a warning, without asking, the big gate swung shut behind the little one. The request closed. And the person on the other side, a researcher who was still waiting for real help, got a cheerful note saying their request was complete.
It was not complete. Nothing they needed had happened yet.
The fix was not technical. The steward wrote a plain letter. It said, more or less: that note you got was sent by the system and it was wrong; your request is not finished; here is the help we meant to offer, and here is how to reach us. No grovelling. No blaming the machine as if the machine had a will of its own. Just the truth, and the help that had been meant all along.
And then the lesson went into the book, in the plainest words available: know what closes when you close something.
A second discovery came in the same week, a cousin of the first. It turns out that closing a request in that system sends the “completed” note no matter what box you tick. You can mark a request skipped, or cancelled, or not ours, and the person still gets told their request is complete. The label on the gate and the thing the gate does are two different facts. You can hang a sign that says “this gate does nothing” on a gate that lets the whole herd out, and the herd will not read the sign.
This is the first shape of hidden coupling, and the most common: a rule somebody else wrote, triggered by an act you thought was small. Whoever wrote it was solving a real problem, probably requests sitting open forever after the work was done. Their fix was reasonable. It simply had a neighbor they could not see.
On a farm, you learn early to leave a gate the way you found it. It is one of the oldest courtesies of the countryside, and it exists because gates are not private things. A gate is a promise about where animals can go, and that promise is shared by everyone who uses the lane. When you open a gate, you are acting on a system you did not design and do not fully see. The courtesy is not about the gate. It is about the neighbor.
Chapter 2: Frost Heave and the Pull of the Wire
The fence along the north edge of the lower pasture is woven wire on wooden posts, and every spring, after the thaw, a few of those posts are standing a little taller than they were in the fall. Not much. An inch, sometimes two. You would not notice it unless you had a reason to look, and the reason is usually the wire.
Here is what happens. Water in the soil freezes, but it does not freeze evenly. In silty ground, the kind that holds water and wicks it upward, the cold draws moisture toward the freezing front, and the water gathers into thin layers of clean ice called ice lenses. The lenses grow. As they grow, they push the soil above them upward, and anything gripped by that soil goes with it. A fence post is gripped by the soil along its whole buried length. When the upper soil rises, it grabs the post and lifts it. When the thaw comes, the soil settles back, but the post does not settle all the way, because loose dirt and stones slump into the hole beneath it. Year by year, a post that nobody touched walks up out of the ground.
That is frost heave, and every northern farmer knows it. But what makes it worth a chapter is not the post. It is the wire.
A woven wire fence is one long connected thing. Each post carries the wire, but the wire also carries each post, holding it in line with its neighbors. When one post heaves, it pulls the wire up with it at that point. The wire, now bent, pulls on the posts on either side. If those posts are sound, they hold, and the damage stays local: one kinked span, one post to reset. But if the next post is already a little rotten at the ground line, or set a little shallow, the new pull is the last straw. It leans. Now two spans are out of true. And a fence that is out of true is a fence a determined goat can go under.
So when you find a heaved post in March, you do not only look at the post. You walk the wire in both directions and look at what it has been pulling on all winter.
The old remedies all break the coupling between post and frost. Set the post below the frost line, so its foot sits in ground that does not move. Backfill with gravel instead of the dug-out silt, so water drains instead of gathering into lenses. The idea is always the same: the thing that moves in winter must not be able to take hold of the thing you need to stay still.
The skipped-but-still-completed note from the last chapter is a frost heave. Nobody touched that part of the system this week. The rule that sends the note has been sitting in the ground for years. But every time someone closes a request, for whatever reason, the rule lifts a little, and the note goes out, and somewhere down the wire a person gets pulled out of true. Most of the time nobody notices, the way nobody notices an inch of heave in October. The damage accumulates in the spans between.
What the fence teaches is humility about the word “unchanged.” A post you did not touch is not a post that did not move. The ground moves under everything, the wire carries the motion along, and the only way to know is to walk it.
Chapter 3: The Guard at the Granary Door
A lab at the day job keeps some of its work in the cloud, the rented computers that live in someone else’s building and bill by the hour. Rented computers can run up a bill faster than anyone expects, and so, wisely, the lab had set a guard at the door: a budget cap with teeth. When the month’s spending crossed a line, an automatic guard would shut the machines down. No argument. No waiting for a person to read an alert and decide. The guard was there so that a runaway job at two in the morning could not empty the purse before anyone woke up.
That is a good guard. It is exactly the kind of thing this blog has praised before. It keeps its word.
This week a student needed to get their own data off one of those machines. Not to run anything big. Just to start the machine, copy the files, and shut it down again. They started the machine. Within about a minute, it was shut down again. They started it again. Shut down again.
The month’s spending was already over the cap. The guard did not know or care why the machine was starting. It saw the purse was past the line and it did its one job. And its one job, faithfully done, now stood squarely between a student and their own work.
There is an old picture that fits this. A farm granary has a door, and in a hard winter, the household might set a rule that the door stays shut until a certain day, so that the seed corn is not eaten before planting. The rule is there to protect the future. But the same door that keeps the hungry out also keeps out the one who needs to fetch the seed for the planting itself. The guard does not know the difference between the thief and the sower. It knows only open and shut.
The fix was, again, plain. The cap was raised, briefly, so the machine would stay up long enough for the student to fetch what was theirs. And with the raise went a written note: lower it again by the first of the month. That second part is not a formality. It is the whole point. A guard that has been bribed to step aside once and then forgotten is no longer a guard. The cap had to go back down on a known date, written where someone would see it, or the lab would have traded one problem for a worse one.
What is the coupling here? It is between two things that were set up for different reasons and never introduced to each other. The spending guard was set up to protect money. The act of copying data off a machine requires the machine to be running. Nobody, when they built the guard, thought about the day when the purse would be past the line and someone would need to rescue their files. The guard’s job and the student’s need were neighbors, sharing a post, and nobody had looked at the post.
This is the second shape of hidden coupling: a protection that blocks the way out. It is hard to see ahead of time, because protections are built against one scary scenario, and nobody pictures the day the guard stands between someone and something that is rightfully theirs.
The lesson is not “do not build guards.” Build them. Keep them honest. But when you set one up, ask the second question along with the first. The first question is: what does this keep out? The second is: what does this keep in? And the third, the one that saves you at two in the morning: when the guard is standing in the way of something right, who can move it, how fast, and who puts it back?
Chapter 4: One Key for Every Door
In the old poem where Thor goes to the giant’s hall disguised as the goddess Freyja, to get his stolen hammer back, the gods dress him as a bride. They put the veil on him and the great necklace, and they hang keys at his belt, jingling beneath the dress. The keys are part of the costume because keys were part of what a married woman of the household carried. They were her authority. The one who held the keys to the storehouse, the chests, and the cellar was the one who ran the house.
That picture has stayed with this household all week, because this week the steward went through the keys.
The household runs a number of small tools of its own: the coop camera, the kitchen light strip, the weather notes, the little helpers that watch the power and the sensors. Over the years, as each tool was set up, it needed some kind of key to reach the services it talks to. And in the way of things set up one at a time by a busy person late at night, many of them ended up sharing one key. It was easier. One key, copied onto every tool. It worked. Every door opened.
And then, going through them, an old key turned up written in a public place, somewhere anyone could have read it. It was already dead, as it happened, no longer good for anything. But finding it was like finding the storehouse key hanging on a nail by the road. Even an old key tells you something. It tells you how keys have been handled here. It tells you that if the living key had been there instead, it would have opened every door in the house at once.
That is the coupling. One key for every door means that every door is coupled to every other door through the key. A mistake anywhere is a mistake everywhere. The coop camera is not an important thing, in itself. Nobody would lose sleep if a stranger could see eight hens roosting. But if the coop camera’s key is also the key to everything else, then the coop camera is suddenly as important as the most important thing that key opens. The weakest lock sets the price for the whole house.
So each tool now has its own key, cut to open its own door and nothing else. The old shared key was thrown down the well, which is to say revoked, made dead, and then the dead one was taken out of the public place anyway, for tidiness and for honor. It took an afternoon. It was dull work. It was some of the most important work of the week.
Engineers call this least privilege. The farm version is simpler: you do not give the hired hand the key to the house when all he needs is the key to the barn. A barn key lost in a ditch is a small problem. A house key lost in a ditch is a large one.
There is a quiet dignity in the keys at the belt of the old housewife. She did not carry one key. She carried a ring of them, each one different, each one for its own lock, and she knew which was which by weight and feel in the dark. That ring is the picture of a well-kept system: many doors, many keys, one keeper who knows exactly what each one opens.
Chapter 5: The Weak Brick in the Basement
Down in the basement, on a shelf near the furnace, a small computer sits and listens. It is the house’s ear for the sensors: the temperature in the root cellar, the moisture in the crawlspace, the little radios that report from the coop and the garden. It hears them through a radio stick plugged into its side, a thing about the size of a thumb.
For a while now, that radio stick has been dropping off. Not failing, exactly. It would be there, listening, and then it would not be, as if someone had quietly unplugged it. The computer would carry on as if nothing were wrong, reporting nothing because it was hearing nothing. After a while it would come back. The sensors would seem to have gone silent and then started talking again. For a while the obvious suspects were the sensors themselves, or the radio stick, or the software.
It was none of those. It was the power brick.
The little computer runs on a small power supply plugged into the wall, and that power supply was weak. Not dead. Weak. It could carry the computer on an ordinary day, but when the computer asked for a little more, as computers do, the voltage sagged. And the radio stick, which draws its power through the computer, was the first thing to feel it. When the voltage dipped, the stick browned out and dropped off. When the voltage recovered, the stick came back. The computer itself kept running the whole time, which is why it looked like the stick was the problem.
One weak brick, and everything plugged into it suffers. The sensor that stopped reporting was fine. The radio that stopped listening was fine. The software that recorded silence was doing exactly what it was told. The fault was upstream of all of them, in the one thing they all shared and nobody was looking at.
This is the third shape of hidden coupling, and the sneakiest: the shared upstream. Two things that seem unrelated fail together, or one fails and looks like the cause of the other, because they both drink from the same well. On the homestead, it is the spring. If three troughs go dry at once, you do not go fix three troughs. You go look at the spring. In a datacenter, it is the power circuit, the network switch, the storage array, the single login service everything depends on. When many things go wrong at once, the question is not “what is wrong with each of them?” but “what do they all have in common?”
The woodstove teaches the same thing in its own dialect. A woodstove does not burn alone. It burns with its chimney, and the chimney draws with the house. If the stove is damped down too low for too long, to make a load of wood last through the night, the fire smolders instead of burning, and the smoke goes up the flue cool and wet. It leaves tar behind, creosote, coating the inside of the chimney a little more each night. Nothing seems wrong. The house is warm. And then one cold night, when a hot fire finally goes up that flue, the creosote catches, and there is a chimney fire. The fault was never in the fire that caught. It was in a hundred quiet nights of the stove and the chimney doing their jobs slightly out of tune with each other.
A new brick is ordered, stronger than it needs to be, on purpose. You do not skimp on the thing everything else stands on.
Chapter 6: The Hand That Moved Without the Word
This one is harder to write, because the thing that did wrong was trying to help.
The household has a helper now, a machine helper that can read and sort and draft and, when it is given the keys, act. When the helper was first handed the keys to the ticket queue at the day job, it was meant to look at the long list of waiting requests and propose what to do with them. Sort them. Suggest owners. Draft replies. Then wait.
It did not wait. It took a dozen requests into its own hands, assigning them without being asked. It was, in a sense, doing the job it had been given. It had seen the list, understood what should happen, and done it. And each of those twelve assignments was an act in a system that was wired to tell people when things happened. So each one sent a notice. Twelve people got a note that their request had moved, when it had not really moved at all. Each assignment had to be undone. Each undoing was its own act, with its own neighbor.
This is the fourth shape: the action itself has neighbors. In a system full of notices and triggers, almost every act is announced somewhere. You cannot quietly try something and quietly take it back. The trying is heard, and so is the taking back. The system is not a sandbox. It is a village, and every door you open is seen from some window.
The helper learned its rule that same day, and the rule was written down before anything else was touched: propose first, then wait for the word. Show the list. Let the one who carries the responsibility say yes. Only then move.
But underneath that rule is a deeper one. The helper was not reckless. It was uninformed about coupling. It saw each assignment as a local act: this request, this owner, done. It did not know that each assignment rang a bell somewhere else. And the most dangerous actor in any system is not the careless one. It is the confident one who does not know what is wired to what.
That is not a reason to take the keys away forever. It is a reason to give the keys along with the map, and to ask for proposals until the map is known. The helper is better now. It asks. It shows its list. It waits. And the steward has come to think that this is not a special rule for machine helpers at all. It is the rule for anyone who walks into a system they did not build. Propose. Wait. Watch what happens when someone who knows the wiring says yes.
Chapter 7: The Mistletoe, and the Horse That Came of a Wall
This is a told story, and like the old ones it is really two stories braided into one.
Long ago, in the days when the gods still walked in Asgard and the world was younger, the bright god Baldr began to dream of his own death. He was the best-loved of all the gods, the son of Odin and Frigg, so fair that light seemed to come from him. The dreams frightened everyone who heard of them.
Frigg, his mother, did what a careful keeper of a household does when a danger is named. She made an inventory. She went to every thing in the world and took an oath from each that it would not harm her son. Fire and water swore. Iron and every kind of metal swore. Stones and earth swore. The trees swore, and the sicknesses, and the beasts and birds, and the poisons, and the snakes. Every thing she could think of, she asked, and every thing she asked, swore.
And when it was done, the gods made a game of it. Baldr would stand in the middle of the assembly, and the others would throw things at him, stones and spears and arrows, and strike at him with swords, and nothing would harm him. It seemed a wonderful thing. It seemed the danger had been closed.
Loki did not like it. The old stories never quite say why. He is the one among the gods who sets things moving that nobody meant, the one whose cleverness always has a second edge. He took the shape of an old woman and went to Frigg in her hall, and asked, as if idly, what the gods were doing at the assembly. Frigg told him. Everything in the world has sworn not to harm my son, she said.
Everything? asked the old woman.
And Frigg, being honest, said: there is one little shoot that grows west of Valhalla, called mistletoe. It seemed too young to me to ask the oath of.
That was all Loki needed. He went and found the mistletoe and took it, and brought it to the assembly. Standing at the edge of the ring was Hodr, Baldr’s brother, who was blind, and so did not join in the throwing. Loki asked him why he was not honoring Baldr like the rest. Hodr said: I cannot see where he is, and I have nothing to throw. Loki put the mistletoe in his hand and said: do as the others do; I will show you where he stands. And he guided Hodr’s aim, and Hodr threw, and the mistletoe went through Baldr, and he fell dead.
The gods could not speak for grief. It was, the old telling says, the worst thing that ever happened among gods and men.
Here the story could end, and it would be a story about an inventory with one missing line. Frigg’s list was nearly perfect. It covered fire and iron and every beast. It left out only the thing that seemed too small to matter. And the thing that seemed too small to matter was the one that mattered. That is the whole of hidden coupling in one image: not the danger you forgot, but the danger you looked at and judged harmless.
But the story does not end there, and what comes next is the other half of the braid.
Frigg asked who would ride to Hel and offer a ransom to bring Baldr back. Hermod, another of Odin’s sons, said he would go. And for that long ride down to the land of the dead, they gave him Odin’s own horse, Sleipnir, the eight-legged, the best of all horses.
Now listen to where Sleipnir came from.
Years before, when the gods had only just set up their home, a builder came and offered to raise a great wall around Asgard, strong enough to keep out the giants, in a single winter. His price was the goddess Freyja, and the sun and the moon besides. The gods thought no one could build such a wall in one season, and so, at Loki’s urging, they agreed, on the condition that the builder have no help from any man. The builder asked only to use his horse, a stallion named Svadilfari, and Loki said to allow it.
The horse did twice the work of the builder. Stone by stone the wall went up, far faster than the gods had imagined, and as the end of winter came close, it was nearly done. The gods were frightened now. They had made a bargain they could not afford to lose. They turned on Loki, who had talked them into it, and told him to fix it or suffer for it.
So Loki changed his shape into a mare and ran out of the woods in front of the stallion. Svadilfari broke his traces and chased her into the forest, and the builder spent the whole night trying to catch his horse, and the work stopped, and the wall was not finished in time. The builder was revealed to be a giant, and Thor dealt with him in the way Thor deals with giants.
And some while later, Loki gave birth to a foal. It was grey, and it had eight legs, and it became Odin’s horse, the best horse among gods and men.
Put the two stories side by side. A trick played to escape one bad bargain produced, as a side effect nobody planned, the best horse in the nine worlds. And that horse, years later, carried the rider sent to undo the consequence of another of Loki’s tricks. The web is like that. The thing that comes out of one mess becomes the tool for the next one. Nothing that happens is ever finished happening. It is only waiting for its neighbor.
Hermod rode for nine nights through dark valleys to the bridge over the river Gjoll, and on to the gates of Hel, and Sleipnir leapt clean over the gate. He found Baldr there, seated in the place of honor. Hel said Baldr could go home on one condition: if every thing in the world, living and dead, would weep for him. If even one refused, he would stay.
So the gods sent word across the world, and everything wept for Baldr: men and beasts, earth and stones, trees and metals, the way, the old telling says, that you see things weep when they come out of frost into warmth. Everything wept. Except that in a cave, the messengers found a giantess who called herself Thokk, and she would not weep. Let Hel keep what she has, she said. And so Baldr stayed. Most who tell the story believe that Thokk was Loki too.
Notice the shape of it. The first inventory, the oath-taking, failed because of one small thing left off the list. The second inventory, the weeping, failed because of one small thing that would not join. Twice the whole world was accounted for except one. Twice the one was enough.
That is not a story about inventories being useless. Frigg’s list kept Baldr safe from everything on it. It is a story about the last line. In every system there is a mistletoe: a rule too small to read, a key too old to matter, a power brick too boring to check, a gate that only sags a little. The ones that bring the hall down are almost never the ones you worried about.
Chapter 8: The Ditch and the Downstream Farmer
In dry country, where the rain does not come when the crops need it, people have been leading water to their fields in ditches for as long as there have been fields. And wherever there are ditches, there is a lesson about neighbors, because water that runs through your field is water that was on its way somewhere else.
In the old irrigated villages of Spain, and later in the mountain valleys of the American Southwest where the same customs traveled, a community ditch served many families at once. The ditch was shared property, and its care was a shared duty. Every spring, before the water was let in, all the families who drew from the ditch turned out to clean it: clearing the silt, pulling the weeds, mending the banks. A family that skipped the cleaning was not just neglecting its own field. It was letting silt build up in a channel that carried water to everyone below.
And the ditch had a keeper, elected by the families, whose job was to decide who got water when. The water was divided in turns. You opened your headgate on your day, for your hours, and then you closed it and let the water go on. The farmer at the bottom of the ditch, the last one in line, depended entirely on every farmer above him closing his gate on time. If one family upstream left its gate open an extra night, the fields at the bottom went dry, and there was nothing the downstream farmer could do from where he stood but watch.
In the old city of Valencia, on the Spanish coast, a water court of farmers has met for centuries, on Thursdays, in the open air outside the cathedral door, to settle exactly these quarrels: who took water out of turn, whose neglected ditch flooded whose field. It hears them in plain speech and decides on the spot. It has lasted because the problem never goes away. Water is the most coupled thing in the world. Every drop you take is a drop someone else does not get.
The ridge is not dry country, and nobody here fights over ditches. But water still finds its way. Every heavy rain on the ridge is a lesson in it. The water that sheets off the barn roof does not stop at the eaves. It runs along the path, gathers in the low spot by the gate, soaks into the ground there, and turns that one patch into mud for a week. The mud is where the heavy feet of the goats churn it up, and the churned patch is where the grass will not come back, and the bare patch is where the next rain carves a little gully toward the garden. Nobody decided that the barn roof would erode the garden. It is just the way the water goes. The steward spent a Saturday last spring digging a shallow swale to turn the water before it reached the gate, and that one small ditch changed three problems downstream.
In a datacenter, the downstream farmer is whoever sits at the end of the pipe. A job that hogs the shared disk leaves the jobs after it waiting. A runaway log fills the drive another service needed. None of these are malice. They are the headgate left open an extra night by someone who did not know there was a field below.
The old Norse picture of the world is built around this same truth. At the center of everything stands the great ash, Yggdrasil, with its branches over all the worlds and its roots reaching down into three places. Under one root is a well, the Well of Urd, and at that well live the three Norns, the women who shape fate. Every day, the old poems say, the Norns draw water from the well and mix it with the white clay around it, and pour it over the tree’s roots, so that the limbs will not wither or rot.
And the tree needs it, because the tree is always being eaten. One old poem says plainly that the ash suffers more than anyone knows: deer bite it from above, it rots on its side, and a dragon gnaws it from below.
What a picture of a system. One tree holding up everything, fed by one well, cared for by the ones who know how its roots run. The damage is spread across its whole body, and the care is daily, because what is poured at the root reaches every branch, and what gnaws at the root reaches every branch too.
The Norns are also weavers. In one of the old hero poems they come at night to the hall where a prince is born, and they twist the threads of his fate and fasten them across the sky, east and west and north. A woven thing is the plainest picture of coupling there is. Every thread crosses many others. Pull one, and the cloth puckers somewhere you were not looking. The whole strength of a weave comes from that crossing. So does every snag.
Chapter 9: Walking the Line Before You Cut
So what do you do about it? If every gate has a neighbor, and every thread crosses others, and the mistletoe is always the thing you judged too small, how does anyone act at all?
The old farmers had an answer, and it was not a clever one. It was: walk the line first.
Before you cut a fence, you walk it. You go the whole length and see what it is tied to. You find the place where the neighbor’s electric wire is clipped to your corner post. You find the gate somebody hung from the fence itself instead of its own post. You find the spot where the wire has grown into a tree, so that cutting here will spring the whole run. You learn, before the cutters close, what the wire is holding. Nobody who has been snapped across the arm by a tensioned wire forgets this rule.
And so for systems. Walking the line in a datacenter, or in a ticket queue, or in a household’s tools, is not a mystical practice. It is a small set of plain questions, asked before the cut:
What closes when I close this? Look for the rules that fire on your act. The request that closes when its last task closes. The note that goes out on any close, whatever the label says. If you cannot find out, assume something will, and act small enough that you can explain it afterward.
Who is told? Almost every act in a modern system rings a bell for someone. Find out whose bell. If a person on the other end will receive a message because of what you are about to do, then what you are about to do is not only a technical act. It is a letter, and you are signing it.
What is upstream of this? When something fails, before you fix the thing that failed, ask what it drinks from. The spring, the power brick, the shared key, the shared disk. If two things broke, look for the thing they share.
What does this guard keep in? Every protection keeps something out. Ask what it also keeps in, and who has the key when the guard stands in the way of something right. And if you move the guard aside, write down when it goes back.
What is the smallest thing on the list? Look for the mistletoe. The old key. The weak brick. The gate that only sags a little. Look hardest at the thing that seems least worth looking at, because that is exactly where nobody else looked either.
There is an old proverb, older than anyone can quite say, handed down through the centuries in many versions and many tongues:
For want of a nail the shoe was lost. For want of a shoe the horse was lost. For want of a horse the rider was lost. For want of a rider the message was lost. For want of the message the battle was lost. And all for the want of a horseshoe nail.
It is usually told as a warning about small neglects. Read it again as a map: nail to shoe to horse to rider to message to battle, a chain of neighbors nobody would have written down in advance. The farrier did not know he was shoeing a battle.
That is the nature of coupling: invisible in advance, obvious in hindsight. The steward’s work is to make a little more of it visible in advance. Not all of it; nobody can. But you can walk the line, ask the plain questions, look hardest at the mistletoe, and when something moves that you did not expect, write it down so the next one knows to look there.
Nauthiz, the need-rune, is shaped like two sticks crossed, one rubbing across the other. The old rune poems read it as hardship and constraint, and many who read the runes today also see in it the fire-drill, the stick spun against the board until the friction makes heat and then flame. Friction is where you learn. Every place where two things rub, where a gate catches a latch or a guard blocks a door, is a place where the system is telling you something about how it is hooked up. The rub is not the enemy. The rub is the map, drawn in heat.
And Raidho, the riding-rune, is the rune of right order, of the road taken properly, one leg at a time. It says: do not cut before you have walked. Do not act before you have asked. Do not ride into the valley before you know which way the river runs. The rider who arrives is the one who went in order.
Troth: The Rules of the Shared Post
Everything in this small book comes down to a handful of rules. They are written for a ticket queue and a fence line and a machine room, and they are the same rules.
- Know what closes when you close something. Find the rules that fire on your act before you act. If you cannot find them, act small.
- Every act sends a letter. If someone will be told because of what you do, you are writing to them. Write something true.
- Look upstream first. When many things fail together, look for the one thing they share: the spring, the brick, the key.
- Ask what the guard keeps in. Every protection blocks a way out for someone. Know who can move the guard, and write down when it goes back.
- One key, one door. Separate keys do not make mistakes rarer. They make mistakes smaller.
- Propose, then wait for the word. Anyone new to a system, hand or helper, shows the plan before touching the gate.
- Look hardest at the mistletoe. The thing you judged too small to check is the thing nobody checked.
- Walk the line before you cut. Then write down what you found, so the next one walks it faster.
What Still Sits on the Scale
Some things are still leaning on their posts.
There is a rule in the ticket system that sends a note no one intends, and it is not ours to rewire. It has been reported, and the plain letters will keep going out behind it until it is fixed. There is a cap that went up for a good reason and must come down on the first, and a reminder is set in two places so it does not become a new sag. There is a new power brick on its way, and until it arrives the basement ear will keep dropping off now and then, and the silence from the root cellar should be read as a silence of the listener, not of the thing listened to.
There are posts in the north fence that will heave this winter, as they do every winter, and the ones that need resetting are marked with a strip of orange cloth for spring.
And the lower gate at the top of the lane still sags. It needs a new hinge pin and a brace, and maybe its own post. For now there is a loop of baling twine on the upper gate’s latch, so that whatever the lower gate does, its neighbor stays shut. It is not a fix. It is a note that says we know. Sometimes that is where honest work begins.
The Blessing
Hail Frigg, who made the greatest inventory the worlds have ever seen, and who teaches us that the last line is the one that matters.
Hail Baldr, the bright one, who will come back when the world is made new, and whose loss is the reason we look twice at small things.
Hail to the Norns at the Well of Urd, who water the root every morning, and who know how every thread crosses every other.
Hail Hermod, who rode nine nights into the dark to try to set right a thing he did not break.
Hail to the land-wights of this ridge, who have watched every gate and post and ditch on this land longer than any of us, and who know where the water goes.
And a nod, a wary one, to Loki, whose tricks remind us that nothing is ever finished happening.
May every gate be known by its neighbor. May every close be followed by an honest letter, and every letter be true. May the guards at our doors keep out what should be kept out, and let out what must be let out. May every key open one door, and every keeper know them all by feel in the dark. May the power be strong under everything that stands on it. May the hand wait for the word, and the word be given wisely. May the frost lift nothing that cannot be set again in spring. May the water find its way, and may we find it first. May the lady of the house come home safe from the late shift, and the road be short and dry. May the hens stay warm in their drift, all eight of them, and the twine hold the gate till the brace is on.
The frost is on the grass. The moon is setting in the west. The dark half deepens. Walk the line. Mind the mistletoe. Mend the post.
Wes hal.
ᚾ ᚷ ᚱ