Charged Terminal rundown

December 24, 2003 on R3X Course

From a post to the R3X thread on the Freezone America Board:

Posted on Wednesday, December 24, 2003 - 10:59 am:

Scanning terminals by four flows: Charged Terminal rundown

I've been testing out this process lately with great success.

Scanning used to be a standard procedure in the early '50s and then it was dropped. Why it was dropped is easy to understand. By itself it's a flawed process. It tends to run shallow. Running into engrams can stop the process in its tracks and throw the PC into an overwhelm. If not run properly it can restimulate areas of life that would be better left undisturbed for the time being.

Yes, I'm familiar with potential shortcomings of lock scanning. They are not anything to be concerned about though, and never come up as a problem in a standardly run R3X session.

The results of scanning terminals by four flows, although nowhere near as spectacular as contacting whole-track basic-basic on a chain and running it out, nevertheless are spectacular enough in their own right. I've seen it magically clear up relationships, whether intimate, casual, work, or otherwise. I've never tried, but I suppose it could be run on various dynamics too, but I'd rather wait to do that thoroughly with R3XD.


The first thing one does do is to determine which terminal is to be run. That can be arrived at with 2-way comm or assessment. Usually parents are good terminals to start with, with later terminals often being restimulators of the parents.

Next the span of time to be addressed should be established: the entire lifetime on the subject of the terminal, or just a segment of time. Breaking it down by segments and running it segment by segment, usually from the later segment on the track (closer to present time) to earlier, is the more conservative approach. I limit the use of this technique to only this lifetime. Engram running by chains is still the mainstay technique in my arsenal, but when this lifetime needs to be destimulated, scanning periods of time, whether in general or with particular attention to specific terminals, is my technique of choice.

The next thing is to give the PC an R-factor of what is expected on flows 2 and 3. Flows 1 and 4 are self-explanatory. Flows 2 and 3 can but do not necessarily include the terminal being run. In other words, it's a wide open command that allows for anything the file clerk is willing to present. So if the terminal is "your father", the "another or others" can be anybody, father or otherwise. It is important that the PC allow the file clerk to present whatever needs to be viewed. Forcing a particular image or scene into view by the PC is not part of the process and only detracts from it.

Also the term "With regard to..." is made sure to be understood by the PC. It means the same thing as "On the subject of _____" or "With respect to _____", or "Concerning _____" or "As regards _____".

The best approach is to first run the 6 Direction Process to EP on the terminal itself before doing the scanning. If one does this step, it is done right after assessing for which terminal to run. I do this step to reduce the charge on the terminal at the beginning in order to make the scanning easier. Besides, it might key out earlier-similar whole track terminals, so it wouldn't hurt to add this step every time.

Commands on general terminals like "a father" as opposed to "your father" are better since they don't limit the parameters of time. Specific terminals will work, but general terminals that represent the specific one, are always better. Sometimes I'll make an exception and use specific terminals though, as with certain co-workers for instance, but that's a judgment call.

Qualifying adjectives like "terrible" or "stupid" or "good" etc. are never used in this process. (References for this can be found in the 1st Melbourne ACC lectures)

So that process would go:

"Get the concept of a father" "Alright"
"Put it above you" "Good"
"Put it below you" "Good"
"Put it to the right of you" "Good"
"Put it to the left of you" "Good"
"Put it in front of you" "Good"
"Put it in back of you" "Good"
etc., etc.....

When the person has EP'd on it, he will find that he has to actively put the picture there -- that the automatically occurring charged facsimiles will have vanished.

Here are the scanning commands:

Move to the beginning of that period of time.

From that point forward to _____, with regard to _____, scan through all the incidents where...

(Flow 1) experienced stress.
(Flow 2) caused another or others to experience stress.
(Flow 3)...others caused others or themselves to experience stress.
(Flow 4) caused yourself to experience stress.

This process is done in conjunction with the 6 Direction Process. With few exceptions, I always end off with the scanning command once more to make sure the period of time in question is flat. What the 6 direction process does, essentially, is to extricate the PC from identification with the terminal or incident.

If a certain incident shows up that is particularly charged, like a heavy engram or secondary, it is wise to stop and address that single incident until flat, and then return to the more general scanning.

As always, running havingness, at least at the end, is important when running these processes. Also, scanning the session at the end is always a good idea.

Robert D.