FILE: ARCH-AFT-006 / STATUS: ACTIVE
I said yes again when I meant no
AFTER THE FACT / PATTERN: The Draining Bond
The yes was out before the request. Not quite, but close enough that you have never once caught the gap between the two, and you are now committed to something you did not choose.
This page is not going to tell you that you have no spine. That is a verdict and this is a record. What is here is what to do in the next ten minutes, and then, if you want it, why the yes was already loaded.
The next ten minutes
The first thing is the thing nobody says: a yes can be revised. Not always and not without cost, and far more often than the sequence lets you believe.
[REWRITE FRAME]
If it is inside a day and the thing has not been arranged around you yet, send one line with no reasons in it: I said yes too quickly and I am not going to be able to do it. Sorry for the change.
No explanation. Reasons invite negotiation and you will lose the negotiation, because the sequence is on the other side of it.
If it is too late to revise, then it is too late, and the useful move is a limit on this one rather than a refusal: I can do the first part and not the rest. I can stay until eight.
And if you are going to do the whole thing anyway, decide that on purpose tonight rather than by default. A yes chosen at eleven is a different object from a yes that was extracted at two, even when the diary looks identical.
Why the resentment never reaches it
Because resentment arrives after the yes, and the yes was loaded before the request finished. It is downstream of the whole sequence, which is why six weeks of it changes nothing at the next ask.
That is also why you have concluded, several times, that the problem is your character. The evidence looked overwhelming: you resent it, you know you resent it, and you say yes anyway. What is missing is not resolve. The window is upstream of where the resolve is being applied.
You did not agree to it. The part of you that would have declined was not consulted.
Where the moment actually is
At the weight. A heaviness across the shoulders and upper back when the name appears or the request starts, three to seven seconds before the reasoning begins assembling the case for why this time is different.
And the interruption is not a refusal, which is the part people find surprising and relieving. It is a delay. Let me come back to you tomorrow. The sequence needs the answer immediately and it does not survive a night.
The guilt is on a schedule
Test it on your own record rather than taking it on trust. The guilt turns up after a completely reasonable decline, delivered warmly, to somebody who took it well. It also turns up after four years of saying yes. Same guilt, same size, in both.
A signal that arrives at the same volume regardless of what happened is not measuring what happened. It arrives because a claim was made that your cost counts, and that claim is precisely what this program was written to prevent.
What tonight actually is
An entry. Filed after the fact, which is an ordinary thing a record accepts rather than a failure being reopened.
There is no shame register here and nowhere for a guilt entry to be filed. The next weight is the one available to you, and a delay is what goes there.
The full file on this sequence, including the reasoning that produces the yes, is at /patterns/why-cant-i-leave-a-relationship-that-drains-me when you want it. It will keep.