[{"data":1,"prerenderedAt":4},["ShallowReactive",2],{"article-body-what-a-prediction-owes-the-decision-it-feeds":3},"\nAsk one question of any predictive system in your company. Which\ndecision consumes this? Put it to every demand forecast, churn score,\nrisk rating and cash projection you can find, and the usual answer is\nsilence. That silence is expensive, because a prediction no decision\nconsumes is just a report, and reports change nothing.\n\nThe difference between the two is a contract, and you can write it\ndown before anyone trains a model.\n\n## The four clauses\n\nA prediction owes the decision it feeds four things.\n\n- **What, precisely.** State a quantity, over a horizon, at a\n  granularity someone can act on, not \"demand will soften\". Vague\n  predictions escape accountability.\n- **By when.** Every decision has a deadline; after it, the best\n  prediction in the world is trivia. A system that cannot meet the\n  deadline should say so.\n- **Who acts.** Name one owner, not a distribution list. If the\n  answer is \"the dashboard's viewers\", the answer is nobody.\n- **How it is scored.** When the outcome lands, someone compares the\n  call to what happened and keeps the comparison. Skip this clause\n  and the other three decay, because nothing separates the\n  predictions worth trusting from the ones worth retiring.\n\n## Dashboards break all four\n\nMost enterprise predictions arrive on a dashboard, and a dashboard\nbreaks every clause at once. It advises, so nobody has to act. It\nstands open forever, so no deadline applies. It broadcasts, so\nnobody owns it. And it refreshes rather than scores, so last month's\nwrong call disappears under this month's confident one.\n\nWatch what happens after a bad quarter. Nobody asks the dashboard to\nexplain itself; they ask the person standing nearest the number, by\nname.\n\nNone of this is the dashboard's fault. It was built to distribute\ninformation, and it does that well. The mistake is asking a\ndistribution surface to do a decision system's job, then blaming the\nmodels when nothing improves. The models were often fine. Nobody\nwrote the contract.\n\n## The decision side is only half\n\nPalantir has argued for connecting agents to decision structure\n([Connecting Agents to Decisions](https://blog.palantir.com/connecting-agents-to-decisions-277dee8ddb40)),\nand the framing is right as far as it goes. But a well-staged,\nwell-owned decision built on an unscored prediction just delivers\nconfident error faster. You need both ends. The decision holds the\nprediction to account; the score tells the decision how much trust\nthe prediction has earned.\n\nA scored prediction gets better or gets retired. An unscored one\njust gets older.\n\nProphesee writes the contract in as engineering. Every model is\nbound to the named decision it serves, every call carries its\ndeadline and owner, and every outcome is scored against the call\nthat preceded it, with the record kept. Competitors find that\nhardest to copy, because a scored claim can be checked and theirs\ncannot. To see the contract on one of your own decisions,\n[start here](/contact).\n",1786984938037]