← Research Research · Applied

Uncertainty Has an Invoice.

Claude Shannon proved uncertainty is a quantity, not a feeling. Once you see a prompt that way, the cost of talking to an AI stops being a mystery and starts being arithmetic you can lower.

Andrew MerschNVS AutomateJuly 20267 min read

Most people treat uncertainty as a feeling. Shannon proved it is a quantity, with a unit, a price, and a hard floor. Read it as a ledger, and the cost of not knowing what you want stops being invisible.

Uncertainty · Ledger the running cost of not knowing what you want
01
You pay in · bits to specify the answer

Uncertainty is a quantity.

Shannon entropy is the number of bits it takes to pin down an outcome. Many equally likely outcomes means high entropy and a large payload; one near-certain outcome collapses it toward zero. Information is just the reduction of that uncertainty, so a message is worth exactly as many bits as it removes.

// entropy of a source X H(X) = − Σ p(x) · log₂ p(x) (bits)
high H → low H
02
You pay in · turns spent guessing

Every conversation is entropy reduction.

A task carries entropy: the bits needed to single out the exact output you want. Each turn exchanges some of them until the uncertainty drops low enough to land the right thing. Being unsure stretches the session. The real skill is bits per turn: an expert resolves in one prompt what a novice takes ten turns to reach, because the first message is a denser, lower-noise signal.

turns ≈ task entropy / bits per turn
THE ANSWER expert 1 · novice 10
03
You pay in · tokens, every session

This is where it touches your bill.

The context window is bandwidth. Tokens are the encoding. A high-entropy task costs more to specify and more to resolve, so cost tracks entropy closely enough to read off an invoice. The cheapest compression anyone owns is reducing your own uncertainty before you prompt: a clear spec is source coding you do once, for free, instead of paying per token forever.

// what you actually pay for cost ≈ tokens ≈ bits transmitted
VAGUE SPEC cost ≈ tokens ≈ bits
04
You pay in · answers it invents

Hallucination is unspecified entropy.

If a task carries H bits and your prompt carries fewer, the model fills the gap by sampling from what is left. That sampling is hallucination. It is not malfunctioning, it invents in exact proportion to the bits your prompt failed to supply. The cure is more mutual information: context and retrieval are extra channels that inject bits and drive the guessing down.

// bits the prompt + your files pin down I(A ; P,C) = H(A) − H(A | P,C)
WHAT THE ANSWER NEEDS PROMPT THE GAP IT FILLS it fills what you left out
05
You pay in · a premium model in the wrong place

Automate the structure. Spend intelligence at the floor.

Every process is redundant, predictable structure sitting on a floor of genuine decisions. Code absorbs the structure for free; intelligence belongs at the floor, and nowhere else. Spraying an expensive model across a whole workflow is paying premium rates to resolve uncertainty that was already near zero. The elegant build puts the smallest, best-placed intelligence exactly where the entropy sits.

DETERMINISTIC INTELLIGENCE spend it only at the hotspot
Σ
Total

AnalogyA business drifts toward disorder on its own. Automation is the pump that spends energy to hold it at low entropy against that drift. An automation studio is not in the business of moving data. It is in the business of importing order.

Uncertainty is not a feeling. It is a payload, and you pay for it in tokens, turns, and time.

The theory underneath
How Shannon's whole framework maps onto what NVS builds.
The Shannon Logic of Automation →

If your operation is paying that invoice by hand, we can show you where.