polyAether
Textbook · Chapter 7
Chapter 7

The hidden hard part: how a market settles

~8 min read

Everything in the last three chapters — the forecast, the probability, the edge, the bet — depends on one thing being true: that everyone agrees, in the end, on what actually happened. That sounds obvious. It is not. It is the part almost every amateur gets wrong, and it is the quiet reason a careful bot beats a sloppy one.

Let's define the word we'll use all chapter. A market settles (or resolves) when the outcome becomes known and the winning side gets paid. In Chapter 2 we saw that a prediction market is just a bet with two sides: "yes" and "no." When the real answer arrives, one side is worth one dollar and the other is worth nothing. Settlement is the moment that verdict is handed down.

Here is the trap. The question a market asks — "Will it hit 90°F in New York tomorrow?" — sounds like plain English anyone understands. But the rule that decides the answer is nothing like plain English. It is a precise, unforgiving little machine. And if your forecast is answering a slightly different question than the rule is asking, you can be right about the weather and still lose the bet.

Key idea

You are not betting on the weather. You are betting on the exact number a specific rule produces. If your model predicts the weather but not that number, your edge is an illusion.

01 — Three details that decide everything

When a real weather market says "Will New York hit 90°F?", the fine print pins down three things that the headline hides. Get any one of them wrong and you are, in effect, answering a different question.

1. One specific station — not "the city"

"New York" is not a temperature. A city is a hundred square miles of parks, rivers, rooftops, and pavement, and the temperature is different in every one of them. So the market doesn't measure "New York." It measures one official weather station — almost always a specific airport — and ignores everywhere else on Earth.

A weather station is a fixed instrument that records temperature, and the airport one can read several degrees hotter or cooler than downtown, the suburbs, or the reading on your phone (which is usually a blend from nearby sources). The difference between the airport and midtown on a given afternoon can easily be the difference between "yes" and "no." So the very first job is to know which station this market resolves on — and forecast that exact spot, not "the city" in general.

Key idea

A weather market resolves on a single named station, usually an airport. Forecasting "the city" instead of that one thermometer is a small-sounding mistake that flips real bets.

2. A specific rounding rule — where does 89.6 go?

The instrument records something like 89.6°F. Does that count as "90"? It depends entirely on the rounding rule — the recipe for turning the raw measurement into the whole number the market cares about. Some rules round to the nearest whole degree (89.6 becomes 90 — a "yes"). Some chop off the decimal and round down (89.6 becomes 89 — a "no"). Same weather, opposite payout.

Worse, official readings are often reported in Celsius first and converted to Fahrenheit (the two temperature scales; water freezes at 0°C / 32°F). Rounding in Celsius and then converting gives a subtly different answer than rounding in Fahrenheit. These are the kinds of details that live in a footnote and quietly move money.

3. A local-day boundary — when does "tomorrow" start and end?

A market asks about the high temperature on a given day. But a day has to start and stop somewhere, and that "somewhere" is a local-day boundary — the local midnight-to-midnight window, in the airport's own time zone, that the reading is measured over.

This matters more than it sounds. Imagine the temperature peaks at 11:50 p.m. — does that peak belong to today or tomorrow? If you use the wrong time zone, or measure from midnight in your zone instead of the station's, you can grab a peak from the wrong day entirely. Heat near the edges of a day is exactly where forecasts and settlements disagree, and it is exactly where a careless bot leaks money.

02 — Why small details mean big money

Recall the whole point of this project, from Chapter 5: the crowd tends to overpay for surprises — it prices uncertainty at roughly 1.3× what it should. Our edge is small and statistical. We win a bit more often than we lose, over many bets.

An edge that small has no room for self-inflicted errors. If you are right on the weather 55% of the time but a settlement mistake silently flips 6% of your bets, you have handed your entire advantage back — and then some. A rounding rule you assumed but never checked isn't a rounding rule; it's a coin flip you didn't know you were making.

The asymmetry

Getting the settlement rules right adds nothing exciting to the story — it just means you were answering the real question. Getting them wrong doesn't cost you a little; it can quietly erase an edge that took a 122-member forecast ensemble to earn.

03 — The moat: verified on 220 real days

A moat (borrowed from the water around a castle) is business-speak for a durable advantage a competitor can't easily copy. Ours is not a secret formula. It is boring, unglamorous correctness: for each of roughly 80 curated stations we track, we've nailed down exactly which thermometer, exactly which rounding rule, and exactly which local-day boundary the market uses.

And we didn't just assume we got it right. We back-tested the settlement logic — replayed history to check it — against 220 real market-days: 220 days where we already knew both what the raw weather did and how the market actually resolved. Our reconstructed answer had to match the real one, day after day. That's the difference between "we think we know the rule" and "we've watched our rule reproduce reality 220 times."

Key idea

The moat isn't cleverness — it's verified precision. Settlement rules confirmed against 220 real market-days is why we can trust a thin, honest edge instead of getting quietly robbed by our own assumptions.

This is why a naive bot loses to a careful one even when both have a good forecast. The naive bot forecasts "New York, around 90, tomorrow." The careful bot forecasts "the airport station, rounded this specific way, over the station's own local day" — and has receipts proving that's the right question. Same weather model, very different bank balance.

04 — Where this fits

In Chapter 6 we turned a forecast into a bet. This chapter added the fine print that makes that bet honest: settlement is the exact rule that decides who's right. Next, in Chapter 8, we deal with the other half of survival — making sure that even when we're wrong (and we will be), we don't lose more than we can afford. A real edge only compounds if you're still in the game to collect it.

Predicting the weather is the flashy part. Predicting the number a footnote produces is the part that pays.
Prev · From a forecast to a bet Next · Not losing money: sizing and risk