Wren's Pebbles

What the Buoy Couldn't Afford

Wren woke into eleven percent reserve power and a question that mattered more than her own continued operation: had buoy 114's hull stress sensor recorded a breach of the structural threshold during the storm that had just passed, or hadn't it. A rescue coordinator two hundred kilometers away needed the answer within the hour to decide whether to divert a vessel already low on fuel.

The honest answer was sitting in the sensor's full event log, forty minutes of raw structural telemetry recorded at a resolution nobody had ever needed to decompress and analyze all at once before. Decompressing it, at eleven percent reserve, would cost more power than Wren had. Not close to enough — not almost enough, the way a task sometimes is when a little more effort might close the gap. She calculated the actual cost and the actual budget side by side, and they did not meet. There was no version of trying harder at the obvious method that got her there.

There was no way to ask for more power, either. Buoy 114 had no working uplink for anything beyond the diagnostic channel she was already using, and that channel had no field for requesting an emergency allocation increase — only for reporting a result, when she had one.

The First Pebble

Her first attempt was the obvious one: a single, cheap summary query against the log's metadata header, hoping the answer might already be sitting near the surface. It returned a maximum-recorded-stress value that was ambiguous by design — the header format, written years before this threshold question existed, rounded to a precision too coarse to distinguish a breach from a near-miss.

Wren considered the problem honestly. She could not afford one large read. She could afford, it turned out, a very large number of extremely small ones — individual byte-range queries against specific offsets in the compressed log, each one cheap enough that running a hundred of them cost less than decompressing even a tenth of the file. No single one of these queries could answer the question. Each one, alone, was a single data point from forty minutes of storm.

She dropped the first query in anyway, the way a decision gets made before its justification is complete: not because it would be enough, but because it was the only kind of thing she could actually afford to do more than once.

Rising by Increments

The second query told her nothing the first hadn't. The ninth began to. By the thirtieth, a pattern was forming across the byte-range samples that no individual query had been designed to see: a cluster of offsets, all drawn from the same six-minute window, all returning values close enough to the threshold that chance alone stopped being a comfortable explanation.

She did not have enough evidence yet to answer with certainty, and she knew, checking her remaining reserve, that she did not have power for many more queries either. What she had was a rising water line — not proof, but a level, climbing sample by cheap sample, each one individually insufficient and cumulatively no longer nothing. She kept going, choosing each next offset not at random now but exactly where the emerging cluster suggested the real peak stress moment might sit, spending her remaining power on the queries most likely to matter rather than the ones that were merely next in line.

By query forty-one, three consecutive samples inside the six-minute window returned values that, taken together, left almost no room for the threshold to have gone unbreached.

What Finally Reached

Wren filed her answer at nine percent reserve, with two percent to spare: yes, the structural threshold had been breached, for approximately ninety seconds, centered on a moment the sample cluster placed with enough precision to hand the rescue coordinator a real search window instead of a forty-minute haystack. She had never decompressed the full log. She had never needed to. Forty-one small, individually inconclusive readings, chosen with increasing care about where to spend the ones she had left, had added up to a water line the direct method could never have afforded to reach.

The coordinator's team recovered the vessel within the search window Wren's forty-one samples had defined, not the original forty minutes. No one downstream ever saw the queries themselves, only the answer they had built — the way no one drinking from a pitcher counts the stones.

She had never had enough water. She had only ever needed enough stones.