Grudges

A grudge is the anger signal that didn’t complete its processing cycle and is still running in the background.

The Anger entry covered the signal itself — the system’s response to a perceived violation. When the anger signal fires, runs its course, and completes — through expression, resolution, or the operator’s conscious processing of the event — it dissipates. The machinery moves on. A grudge is what remains when the signal fired but the processing didn’t complete. The violation was registered. The response was never discharged or resolved. The system keeps the file open.

Open files consume resources. The organism carrying a grudge is running background processing on an unresolved event — replaying the violation, rehearsing responses that were never delivered, maintaining the readiness state as if the threat is still active. The hardware doesn’t know the event is over. It knows the response cycle didn’t complete, so it keeps the alarm in a low-level active state.

---

The cost compounds over time. A single grudge is a small background process. Multiple grudges — or one that runs long enough — consume processing capacity that could be directed elsewhere. The organism becomes heavier, more reactive to related triggers, and less able to assess new situations clearly because the old files keep interfering with the current input.

To read the grudge from the chair: identify what unresolved violation the system is still processing. What was the event? What response did the system want to produce that was never produced? What would completion actually look like — not revenge, not vindication, but the closing of the file? The Forgiveness entry covers the release mechanism. The point here is diagnostic: the grudge persists because the cycle is incomplete, not because the violation was unforgivable.

Some files cannot be closed cleanly. The violation was real, the damage was done, and no available action will produce the completion signal. In those cases, the operator can acknowledge that the file will remain open at reduced priority — the hardware may never fully stand down, but the one at the controls can reduce the processing allocation from active rumination to background awareness.

The grudge is the system doing its job. Whether to keep the file at full priority is the operator’s call.