Abridged recap of R3X
April 20, 2003 on R3X Course
First I run the item by R3R, with the provisos I outlined below in the differences between R3R and R3X (in other words, per the standard R3X procedure up to the shift).
Then, when I've gotten the Pc to basic-basic, I ask for the shift moment (equivalent to the shock moment of PAB 80 that Ron never pursued any further). There will ALWAYS be one.
I then get the Pc to assume the viewpoint of each of the dynamics at that moment and then view the shift from each of those vantage points (the list has been updated on formerscio). That's the most crucial part of the shift handling process. It's like each of the dynamics doing a contact assist.
Next I ask for the main goals (which cause the persistence) and flatten those by repeater.
Then I ask for a computation (which justifies the game's perpetuation) and flatten that by repeater.
Then as a final touch, I run "Responsibility" on the incident. By this time the Pc is ready to take honest and full responsibility for the incident along all dynamics.
Then to "polish off" the end product I have the Pc scan his track on the given item on each of the 4 flows.
I always end off with the scanning of the session and two havingness processes.
That's basically all there is to it.
From the Start to the Shift
Run the item as one would with R3R as modified by the R3X write-up. Be sure to flatten each incident along the way. R3X up to the basic incident is basically run with the rules of the R3R narrative procedure except for the "earlier incident" command.
If the Pc says there is no earlier incident to a MEST universe incident previously run, ask "Is there an earlier incident, possibly before the beginning of time..." or "...in the Theta Universe..." --whatever indicates to the Pc-- where you had the feeling of ...(item)...?" All items have their basis in the Theta Universe. Even body problems have comparable concepts in Theta incidents.
If the Pc says there's no earlier incident but has not hit basic-basic, ask: "Is there an earlier incident, possibly around the original separation (individuation, breakoff) from Static (Source, yourself -- whatever indicates) where you had the feeling of ...(item)...?"
The basic incident should have a pleasant pre-beginning. If the incident starts unfavorably, then have the Pc look for an earlier beginning until he finds a point before the bad feeling starts.
When the basic incident, hopefully basic-basic, has been flattened completly, the auditor asks the Pc for a moment of shift, the first one, and asks to Pc to describe it (like "from what to what?").
Handling the Shift
The following is the checklist of points covered in the shift handling as I do it now. It's a rudimentary list and is only an adjunct to the full writeup of the R3X process found on the Freezone America web site www.freezoneamerica.org.
I run this process on people on an almost daily basis and have been doing so for the last several years. The process, when done correctly, will resolve the item in question smoothly and flawlessly every single time. Each individual action is done to the E/P of F/N, cognition, VGIs. No need to insist on what the cog was, though. Doing so (or any roteness) can be annoying to the Pc.
• before/after process on the shift
• "Move thru that moment of shift from beginning to end."
• viewpoint after shift
• vp before shift
• vp of others (Others can always be found after the shift if not before, and should be run regardless of Pc interest in that one)
• vp of creations (This is the MEST equivalent. Any creations, energies, agreements, etc. will do)
• pan determined vp
• vp of aesthetics
• vp of ethics [
• vp of games (...or not. I've dropped it as a command) ]
• vp of being
• vp of infinite being (All That Is)
• vp of Source (source of All That Is, source of all consciousness)
• As Static ("As Static, experience that moment of shift from beginning to end")
• As Static backwards ("As Static, experience that moment of shift backwards from the end to the beginning.")
• Check for any undesirable feelings from the incident and handle. By this time there are normally none left.
• Check for goals and handle. There is always at least one pair of goals in opposition as relates to the item. You may have to start the Pc out on repeating one goal first until the opposing goal becomes more real to him, at which time you have him repeat both.
• Get and handle computation. There is always at least one. (If the Pc if insists there is none and none can be found, then it may be better to let it go at that, but that's very rare. Finding a computation can sometimes be tricky - especially when running the dynamics.)
• Run "Responsibility" process on incident. The Pc should wind up taking full responsibility for the basic incident.
• Check back on the present status of any phrases, feelings, or shocks noted down on the work sheet from later incidents and handle accordingly. By now they should all be flat.
• Scan 4 flows from basic to PT.
• Scan the item itself: "Scan out the item ..... wherever you find it exists in the universe." or any similar command. (This step works on high-level Pcs, but it's still experimental at this time as to who it can be used on.) (I have dropped this step too.)
• Ask Pc how the item is.
• Ask him if he could recreate it again if he wanted to. (This is an optional step.)
• Run havingness processes.