Lag

Lag learned about delays the year his family planted a slow-fruiting tree.

They planted it when he was small, and he checked it every single day, impatient for fruit. Nothing. He decided it was a dud and wanted to dig it up. His mother stopped him.

"It's not broken," she said. "It's slow. Some causes take years to show their effect. If you dig it up because nothing happened today, you'll never find out it was working all along, underground, where you couldn't see."

Young Lag hated that. He wanted the effect to follow the cause right away, like a light switch. But the tree taught him the patient truth: the gap between doing a thing and seeing it work is real, and it fools almost everyone. "Most mistakes," his mother said, "aren't from doing the wrong thing. They're from doing the right thing, seeing nothing yet, and giving up — or doing it again, and again, until you've done far too much."

The tree fruited four years later. Lag was there, and he never forgot the lesson: an effect that arrives late is still arriving.

He climbed slowly to Nexusforge at twelve, because a place that studied connection ought to respect the time between things.

Mesh, the mentor, met him and asked one thing. "Show me something that answers late."

Lag rolled a marble down a very long, curving tube. He tapped the top. "I pushed it here," he said. Seconds passed. Nothing came out the bottom. "If I panic now and push another marble, and another—" the first marble finally rolled out, then a second, then a third, all in a rush "—I get a pile-up. Because the answer to my first push was still traveling." He set the tube down. "The delay is invisible. That's what makes it dangerous. You can't see the marble in the tube, so you assume nothing's happening — and act like it. That's how you overshoot."

Mesh watched the marbles settle. "You belong here," he said.

Lag's favorite lesson was a little game of steering a ship.

A class gathered around a screen with a big cartoon ship and a rudder. "Turn the rudder left," Lag said. Pip did. The ship kept going straight. "It's not working!" Pip turned the rudder harder left. Still straight. Harder. Then — slowly, then all at once — the ship swung hard left, way past where Pip wanted, and he yanked the rudder right to fix it, and that overshot too, and the ship wobbled wildly down the channel. The class laughed. "You've made a ship that can't sail straight," Lag said cheerfully, "and you did it by being reasonable. Every single move made sense — you turned toward where you wanted to go. But a ship answers its rudder late. So by the time you saw the turn, you'd already turned too much." He reset the ship and steered it himself: one gentle rudder move, then a long, patient wait, then a tiny correction. The ship glided smooth down the middle. "Same rudder. Same ship," Lag said. "The only difference is I left room for the delay. I moved once, and trusted it to arrive." Then he showed the deep part: "Delays are why systems oscillate — why a thing swings too far one way, then too far the other, back and forth. It's almost never that the system is wild. It's that someone kept reacting to results that hadn't arrived yet."

Pip watched the smooth-sailing ship. "So the delay was the whole problem the whole time."

"The delay is usually the whole problem," Lag said. "And almost nobody sees it, because you can't see a thing that hasn't happened yet."