In my last post, I talked about changing a Source Code Story, which is a story that lies beneath a series of Upsets. As our idea of being a separate identity is just an illusion, I wanted to keep working down my list of Source Code Stories in a continued experiment of chipping at the bedrock of self.
My idea is that these Source Code Stories are the drivers of how we perceive the world and how we express our “selves” to others. Our “self” is a bundle of sometimes disjointed stories, and if I can change one or many of them I can recreate myself.
Could I identify and reduce the frequency and intensity of a Source Code Story?
What I Did
Using the same mini-survey protocol I used in the first experiment, I captured the Source Code Story beneath a series of Upsets and rank ordered them to find which was the most frequent. Again, I did multiple repetitions of the exploratory protocol on that story. And throughout I was doing the mini-surveys and monitoring to see if the frequency and intensity of that Source Code Story had changed.
How I Did It
Using the same Google Forms mini-survey that I had devised in the first experiment I captured a list of Source Code Stories that lay beneath various Upsets. As a review, these surveys ask five questions. The first question is my state of mind on a scale of 1 to 5. The second was a brief description of the Upset. The third was a brief Glass Half Full opportunity within the situation. For example, if I was Upset about waiting in line, an opporunity might be I had a chance to read an interesting book. The fourth was a text entry of what I thought I was trying to protect when I was Upset. This was the Source Code Story. The fifth and final entry again rated my state of mind from 1 to 5.
The protocol for altering the Source Code Story included a different mini-survey. This broke the story down into what sensations were present, what the story that arose from the sensations and the triggering cause of the story. As I have mentioned I learned this sequence from a Guide at Liberation Unleashed. I did this exploratory protocol 25 times over the course of a week.
What I Learned
I reduced the frequency and intensity of another Source Code Story. From the list of Source Cost Stories I had gathered in the first study I determined that the next most frequent Source Code Story was my desire to work on big, important things. This took the form of me having little or no patience with tasks I had deemed were not contributing to some large and significant issue.
From the week prior to doing the protocol an Upset related to this Source Code Story occurred eleven times. This was an average of 1.8 times a day. I was spending a lot of energy feeling that I was wasting my time on tasks that were not significant. During the week, I repeated the exploratory protocol the frequency dropped to .5 per day, and after four days Upsets from this Souce Code Story stopped completely.
As I had measured my state of mind on a scale from 1 to 5 at each Upset, I had a chance to examine how the protocol changed the intensity of the Upsets. Not only did the frequency decrease, the negative state of mind decreased. With 1 being negative and 5 being positive, my average state of mind when these Upsets occurred went from 1.8 to 2.25.
Using a free Google Form and an iPhone I have moved two Source Code Stories from active to far less present in my awareness. As part of reviewing my data I checked on the frequency of the first Source Code Story I worked with, my dislike of having my decisions challenged. In the week-long period after having reduced its presence, an Upset with that Source Code Story only occurred on one occasion. Once that Source Codes Story was gone, it seems to have stayed gone.
Subjectively the amount of time my mind has been spinning due to a Source Code Story has reduced. There have been a lot of moments of relaxation. I imagine that in moments of downtime prior to this I would kick into one of these stories. I am going to conduct the protocol on the remaining list of Source Code Stories to determine what happens when they are all removed.