Necessity

Necessity is what the system actually requires versus what it says it requires — and the gap between the two is wider than the operator usually recognizes.

The hardware runs a continuous needs-assessment, but the assessment is contaminated by conditioning, habit, comparison, and the reward system’s preferences. The system says I need this about many things that are wants, preferences, or installed expectations. The actual necessities — what the organism genuinely cannot function without — are a shorter list than the system models.

---

Genuine necessities: adequate fuel, water, sleep, shelter, physical safety, a minimum of social contact, and some degree of purpose or direction. Below these, the system deteriorates. Above these, the system functions. Everything else — while potentially valuable, enriching, or strongly preferred — is not necessity. The system will produce the urgency signal about non-necessities with the same intensity as about necessities, because the hardware doesn’t distinguish between the two at the signal level.

From the chair: when the system produces I need this, check the claim. Is this a genuine operating requirement — something the system will degrade without? Or is this a preference the system has escalated to necessity through repetition, conditioning, or the reward circuitry’s insistence? The first warrants mobilization. The second warrants assessment of whether the cost of pursuing it is proportionate to the actual, rather than the felt, need.