Completion

The reward system produces a specific signal when an open process closes.

The mind tracks open loops — tasks begun, projects underway, intentions declared but not yet executed. Each open loop occupies background processing capacity. The system maintains a partial model of each one, checking periodically: is this finished? The background processing is real and measurable — the cognitive load of unfinished tasks persists even when the one at the controls is focused elsewhere. The mind doesn’t stop tracking the open item just because attention has moved on.

Completion closes the loop. The background processing on that item stops. The cognitive load releases. The reward system fires a signal that feels disproportionate to the task’s importance — because the reward isn’t just for the task. It’s for the release of the processing load.

---

This mechanism explains two common patterns. First: why small completions can produce surprisingly large satisfaction. The task was minor. The processing load it was occupying was not. Closing it releases a disproportionate signal.

Second: why starting many things without finishing them produces a specific kind of exhaustion that rest doesn’t resolve. The fatigue isn’t physical. It’s cognitive — the processing budget is consumed by open loops, each one drawing background resources, none of them releasing. The system is tired not from working but from tracking.

The operational implication: finishing has a value independent of what’s being finished. The completion signal — the release of the loop — is its own reward. The organism that closes three small items often feels better than the organism that advances one large item, because three loops closed produce three release signals, while one loop advanced produces none.