Starting R3X

August 2, 2004 on R3X Course

From: "Robert D."
Date: Mon Aug 2, 2004 5:59 pm
Subject: Getting Started on R3X

As I mentioned previously, one way to get started on R3X would be to simply find an incident on a PC (an abbreviation which could stand for processee or processing client and not necessarily pre-clear).

The procedure is simple. Just start a session as you normally would, and find an isolated incident like a divorce, a death in the family, an upsetting event, etc. Run the incident just as you would any narrative incident, except for the additional options. Remember that with R3X you always have the option of sticking strictly with R3R procedure too. R3X simply gives you the additional options that have been time-tested and proven to work standardly in PC after PC.

If you were to run the incident R3X style, the procedure would go something like this:

Auditor: "Move to that incident."
PC: "Okay".
Auditor: "What is the duration of the incident?"
Auditor: "Move to a point just before the incident began."
PC: "Okay."
Auditor: "Good." "Move through to the end of the incident."
PC: (scans through the incident) "Okay".
Auditor: "Alright. What happened?"
PC: (tells auditor what took place)

(At this point the auditor has the option of using the Before/After process if the PC's data is too scant or occluded. This is done to a release point.)

Auditor: "Okay. Now get that incident and put it above you".
PC: "Yes".
Auditor: "Good. Put it below you".
PC: "Yes".
Auditor: "Good. Put it to the right of you".
PC: "Yes".
Auditor: "Good. Put it to the left of you".
PC: "Yes".
Auditor: "Good. Put it in front of you".
PC: "Yes".
Auditor: "Good. Put it in back of you".
PC: "Yes".
Auditor: "Good. Put it above you"
PC: "Yes".
etc., etc., etc. done to a release and flat point.

Auditor: "Move to the beginning of the incident". (The PC should know to move to the same point as before)
PC: "Okay"
Auditor: "Good." "Move through to the end of the incident."
PC: "Okay"
Auditor: "Good. What occurred that time?" (The question can be varied as "What came up that time?", "What did you get?", etc.
The idea is that the auditor wants to know what the PC newly saw as he scanned through, not necessarily the whole story parroted back.)

By this time the incident should be flat and the PC should have VGIs. If it's not, it's okay to use TR-4 and query the PC as to what aspects of the incident are left. Then the 6-Dir process is used again, followed by another scanning. This is done until all the charge in the incident has vanished. If, in the rare case where there appears to be any lingering bad feeling to the incident, the auditor can ask the PC if the charge is coming from that incident or an earlier (or another) one. If it's still coming from that incident, then it's safe to go through the procedure again. Otherwise, running the earlier similar incident would probably be the next thing to do.

If you want to do a narrative 4 flows, fine. I'm not that concerned about getting 4 flows in on this-lifetime narrative incidents. Besides, doing Lifetime Scanning 4 flows (as mentioned in the R3X thread of the Freezoneamerica board) would cover pretty much anything from this lifetime that needs to be run.

A system of notation I use for the 6-Dir process is the following done on letter-sized college ruled paper.

A |||| |
B |||| |
R |||| |
L ||||
F ||||
B ||||

Robert D.