Self-deceit loop
Compulsion and self-deception pattern
Compulsion often arrives with a story already loaded. The act matters, but the permission script that escorts it in matters too.
This narrative sits close to the moment before the act: the small internal permission story that lets repetition sound temporary, manageable, or deserved right before the loop closes again.
- Blog home: Open blog home
- Pattern or framework: Related framework: What recognition changes
- Related narrative: Repeated failure is protection
- Pressure builds and memory starts being edited in real time.
- A permission story appears: just this once, not that bad, after today it stops.
- The act lands and the story mutates into shame, inevitability, or forgetting.
- Recognition usually arrives late, after the same script has run enough times to become visible.
- The script often sounds calmer than the harm it is about to authorize.
- People frequently remember the feeling of inevitability more strongly than the exact words that produced it.
- Recovery starts changing once the story is caught before it earns the act.
- The blog home carries the longer recovery argument.
- The framework page explains what tends to shift after recognition finally sticks.
- The story intake route exists if a lived account needs controlled review rather than performance.
Return to the system, not just the story.
Use the story files index for other narratives, the pattern map for structure, or the share route if a related account needs controlled review.