The
Argument.
Energy ≠ Time
The world treats them as equivalent. They are not. More hours does not produce more output - cognitive capacity does. This is the premise everything else builds on.
When the two are in conflict, capacity matters more than clock time. Work done in 75 productive hours beats work attempted across 160 depleted ones.
The Formula: ph ≤ wh
ph / wh distribution
to map cognitive degradation.
Notice how forcing a full 10-hour day destroys output efficiency when base energy is limited.
Productive hours (`ph`) can never exceed total work hours (`wh`), but they are almost always significantly lower. Software that assumes `ph = wh` immediately begins accumulating debt by demanding output that the user’s cognitive state literally cannot provide.
When focus doesn't come and exhaustion builds, pushing on time does not yield more output. It yields frustration. We build systems that recognize when capacity is low, and actively do the compensation for you.
How Software Should Act
If a tool is aware of your energy, it should not barrage you with identical structures at `100` capacity and `0` capacity. It should:
- Accommodate, not demand. It works when you need it to, and fades functionally when you don't.
- Reduce surface area on low energy. Hide secondary data. Diminish bold colors. Mute chaotic animations. Provide exactly what is required for the next atomic action.
- Provide leverage on high energy. Allow deep exploration, open complex tooling, process sweeping conceptual architecture when capacity allows it.
- Never judge. Variable energy is not a moral failure. Inconsistency is not laziness. The software's state reflects the real human reality - objectively and without shame.