Directory · O
New here? Start with the premise →
Obligation
1 min read · 221 words
Obligation is the system’s production of must from a source the operator hasn’t verified.
The hardware produces the obligation signal — the felt sense that an action is required, non-optional, owed — through multiple channels. Genuine commitment (the operator made a promise and the integrity code requires follow-through). Social pressure (the group’s expectations produce a compliance signal). Installed code (the family, culture, or conditioning says this must be done). Guilt manipulation (another operator has activated the guilt mechanism to produce compliance).
The signal feels identical regardless of the source. The I must of genuine commitment and the I must of unexamined conditioning produce the same weight in the body, the same urgency in the mind. The operator who treats every obligation signal as equally valid is running obligations they chose alongside obligations that were installed without their consent.
From the chair: when the obligation signal fires, check the source. Did the one at the controls actually commit to this? Does the operator genuinely endorse this requirement? Or is the system running compliance code from a source the operator hasn’t reviewed — the family’s expectations, the culture’s demands, another operator’s manipulation?
The first warrants honoring. The second warrants assessment. The third warrants the Boundaries entry’s limit-setting.