| R3RA Commands, Theory | R3RA Drills, TR-100's |

 

R3RA ENGRAM RUNNING BY CHAINS

THE COMMANDS

 

FLOW 1:
STEP ONE:  Locate the first incident by the command  
"Locate a time when you had_____."
 
Also make a note of TA position.
 
STEP TWO:  
"When was it?"
 
You accept any time or date or approximation the pc gives you. Do not attempt any dating drill with Meter.
 
STEP THREE: 
Move the pc to the incident with the exact command, 
"Move to that incident."
 
(This step is omitted if the pc is telling you he is there already.)
 
STEP FOUR: 
"What is the duration of that incident?"
 
Accept any duration the pc gives you or any statement to that effect the pc makes about it. Do not attempt to use Meter to get a more accurate duration.
 
STEP FIVE: 
Move the pc to the beginning of the incident with the exact command: 
"Move to the beginning of that incident and tell me when you are there."

 
STEP SIX: 
Ask pc what he or she is looking at with this command. First, if the pc's eyes are open, tell pc, 
"Close your eyes"
, acknowledge him quietly for doing so and then give him the command 
"What do you see?" 

 
STEP SEVEN:  
"Move through that incident to a point (pc's given duration) later."
 

STEP EIGHT: 
Sit quietly; say nothing, do nothing; just observe the pc and Meter or make quiet notes while pc is going through the incident. If pc comments before reaching the end just say 
"OK, continue."

 
STEP NINE: 
When the pc reaches the end of the incident say only: 
"What happened?"
 

 Take whatever pc says, acknowledge as appropriate. Say nothing else, ask nothing else. When pc has told little or much and has finished talking, give him a final acknowledgement. That ends cycle on one run through.
 
If the TA has risen (from its position at Step 1) the auditor immediately checks for an earlier incident (Step G). If no earlier incident, he asks for an earlier beginning to the incident (Step H).
 
If the TA is the same or lower, he runs the incident through again (Step A).
 
In going through an incident the second or more times auditor does not ask for date and duration or anything else.
 
STEP A. 
(After pc has competed Step 9) 
"Move to the beginning of that incident and tell me when you are there."
 

STEP B. 
"Move through to the end of that incident."

 
STEP C. 
(When the pc has done so) 
"Tell me what happened."

 
STEP Ca. 
"Is that incident erasing or going more solid?"
 
(TA rising means the incident has gone more solid so the question is not asked if TA is higher.)
 
If the incident is erasing, go through it again.  If it has gone more solid, ask for an earlier incident.
If no earlier incident, ask for an earlier beginning.
 
STEP D. 
"Return to the beginning of that incident and tell me when you are there."

 
STEP E. 
"Move through to the end of that incident."

 
STEP F. 
"Tell me what happened."

 
STEP Fa. 
"Is that incident erasing or going more solid?"
 
(TA rising means the incident has gone more solid so the question is not asked if TA is higher.)

If the incident is erasing, go through it again (Step D).
If it has gone more solid, ask for an earlier incident (Step G) 
and if no earlier incident, ask for an earlier beginning (Step H).
 
STEP G. 
"Is there an earlier incident when you had a (exact same somatic)?"
 

Continue on down the Chain of the same somatic using Steps 2-9, A, B. C, D, E, F. G. H. and EYE.
 
Step H: 
"Is there an earlier beginning to this incident?"
 
or "Does the one we are running start earlier?"  
or "Does there seem to be an earlier starting point to this incident?"
 

(If not, give command D and put the pc through the incident again. If there is an earlier beginning, give command EYE.)
 
STEP EYE. 
"Go to the new beginning of that incident and tell me when you are there."
 
(Followed by B. C.)
 
 
Postulate Off Equals Erasure
 When it looks like you have reached the basic incident of the Chain and that it is erasing, after each pass through, ask: 

"Has it erased?"
 
The pc sometimes thinks the incident is erasing but it's not erasing, so you have to go back to your G. H. EYE followed by 2-9, A-EYE. In some cases this can happen several times on one Chain.
 
The postulate coming off is the EP of the Chain; it means you have obtained an erasure. This will be accompanied by F/N and VGIs. Getting the postulate is the important thing. Even if you get an F/N you don't indicate the F/N until you've gotten the postulate, at which time you have reached the EP and end off on that Chain.
 
If the pc says the Chain has erased, but the postulate made during the time of the incident has not been expressed by the pc ask:

  "Did you make a postulate at the time of that incident?"  

Only when the postulate has come off to F/N and VGIs can one consider that the full EP of an engramic incident or Chain has been reached.
 
You must recognize what the postulate is when it comes up. It is usually signaled with a BD. If you try to run pc past the postulate it messes up the situation and pc. It may need extensive repair. All you're basically going for is find and blow the postulate, because hat is what is keeping the Chain there. When the pc has given the postulate to F/N and VGIs, that is it. You have the EP of that Chain.
 
Going Earlier
Usually an incident is run through twice, (Steps 1-9 then A-C). This is done to unburden the Chain and allow the pc to locate earlier incidents on the Chain, now coming to view. You get some of the charge off the present incident and the pc can now find anything earlier.
 
The TA, however, tells the story as well. If the TA is rising on Step 9 it usually means there is something earlier. If the auditor observes the TA rising, he should ask the pc (1) if there is an earlier incident, using in the command the exact same somatic or feeling used in Step One. (2) If there is no earlier incident he asks if there is an earlier beginning.
When the TA has gone up you check for an earlier incident (or earlier beginning) after the first run through.
 
If, after the second pass through, when you have asked the pc "Is the incident erasing or going more solid?" and the pc doesn't know or isn't sure, ask for an earlier incident. Never ask erasing/solid in the middle of an incident.
 
 
Bouncers
If the pc bounces out of the session, out of the incident, bounces from the incident, etc., you would have to tell him to 

"Return to the beginning of the incident and tell me when you are there"  

and move him through the incident. The pc who bounces out of an incident on a "bouncer" has to be put back into the incident and continue to run it. So you give pc the above command followed with E, F. Fa.
 
FLOWS 2, 3 and 0
Step One and Step G (going earlier) commands for Flows 2, 3 and 0 are:
 
FLOW 2:

STEP ONE:  
"Locate an incident of your causing another_____  
(the exact somatic or feeling used in Flow 1)."
 

STEP G: 
"Is there an earlier incident of your causing another_____  
(the exact somatic or feeling used in Flow 1)?"

 
FLOW 3:

 
STEP ONE: 
"Locate an incident of others causing others_____ 
(plural of the somatic or feeling used in Flow 1). "

 
STEP G: 
"Is there an earlier incident of others causing others___ 
(plural of the exact somatic or feeling used in Flow 1)?"

 
FLOW 0:

STEP ONE: 
"Locate an incident of you causing yourself___ 
(the exact somatic or feeling used in Flow 1)."

 
STEP G: 
"Is there an earlier incident of you causing yourself____ 
(the exact somatic or feeling used in Flow 1)?"

 
Each of these Step One and Step G commands are followed by on the full exact commands 2-9, A-EYE in the steps as given above.
 
Narrative R3RA
A narrative item is often run to run out the physical experiences the person has just undergone. This could be for example an accident, illness, an operation or emotional shock. When you are running a narrative you always add the known incident to the command. 

Using the earlier beginning command in running narratives is important. For example: If the pc is running out a death of somebody closely related to him you will find that the incident actually started when he heard the phone ring, then, going back earlier to when somebody looked at him in a strange way, etc. So using the earlier beginning command in narrative running is important.
 
The commands for Narrative are:
 
FLOW 1:

STEP ONE: 
"Return to the time you______  (specific incident) and tell me when you are there."

 
Steps 2-9 follows (3 is omitted as you have already got the pc to the incident by giving him the first command, "Return to the time....").
 
Earlier beginning (Step H) is checked after each run through the incident. If there is one, send the pc to the new beginning of the incident (Step EYE) then follow with Steps B and C.
 
If there is no earlier beginning, return the pc to the incident with Step A, followed by B and C. Then again check for earlier beginning (Step H) at the end of each run through the incident. On third and additional runs through the incident use steps D, E, F making certain to check for earlier beginning after each run through, and only when the pc is obviously starting to grind and gets no place does one then use the command, "Is there an earlier similar incident?"
 

 
FLOW 2:

STEP ONE: 
"Return to the time you caused another to/a (specific incident) and tell me when you are there."
 

Steps 2-9 follows (3 is omitted as you have already got the pc to the incident by giving him the first command, "Return to the time...").
 
Earlier beginning (Step H) is checked after each run through the incident. If there is one, send the pc to the new beginning of the incident (Step EYE) then follow with Steps B and C.
 
If there is no earlier beginning, return the pc to the incident with Step A, followed by B and C. Then again checking earlier beginning (Step H) at the end of each run through the incident. On third and additional runs through the incident use Steps D, E, F. Make sure to check for earlier beginning after each run through, and only when the pc is obviously starting to grind and gets no place do you then use the command, 

"Is there an earlier similar incident?"
 
 
FLOW 3:

STEP ONE: 
"Return to the time others caused others to/a (specific incident) and tell me when you are there."
 

Steps 2-9 follows (3 is omitted as you have already got the pc to the incident by giving him the first command, "Return to the time....").
 
Earlier beginning (Step H) is checked after each run through the incident. If there is one, send the pc to the new beginning of the incident (Step EYE) then follow with Steps B and C.

If there is no earlier beginning, return the pc to the incident with Step A, followed by B and C. Then again check for earlier beginning (Step H) at the end of each run through the incident. On third and additional runs through the incident use steps D, E, F making certain to check for earlier beginning after each run through, and only when the pc is obviously starting to grind and gets no place does one then use the command, 

"Is there an earlier similar incident?"
 
 
FLOW 0:

STEP ONE: 
"Return to the time you caused yourself to/a (specific incident) and tell me when you are there."
 

Steps 2-9 follows (3 is omitted as you have already got the pc to the incident by giving him the first command, "Return to the time....").
 
Earlier beginning (Step H) is checked after each run through the incident. If there is one, send the pc to the new beginning of the incident (Step EYE) then follow with Steps B and C.

If there is no earlier beginning, return the pc to the incident with Step A, followed by B and C. Then again check for earlier beginning (Step H) at the end of each run through the incident. On third and additional runs through the incident use steps D, E, F making certain to check for earlier beginning after each run through, and only when the pc is obviously starting to grind and gets no place does one then use the command, 

"Is there an earlier similar incident?"
 
 
Secondaries
Secondaries are run with the same commands as R3RA. Narrative Secondaries (such as a recent loss)  are run with the same commands as Narrative R3RA Engrams.
 
The earlier similar command is 

"Is there an earlier similar incident?"
 
Narrative incidents are always run Quad flows.
 
Certainty of Commands
The commands etc. has to be drilled, drilled and drilled with TR 101, 102, 103 and 104 before actually doing Engram running on a pc.
 
A hesitant auditor or incorrect use of commands kills Engram running. Auditor certainty inspires confidence and the Time Track will respond properly only when auditor is capable of positive control.

Flattening the Chain
You always take a Chain to full EP for Engram running. Sometimes there is "no earlier incident" and "no earlier beginning". In this case you simply send the pc through the incident you are running once more. It may need to be unburdened some more and pc can all of a sudden see the earlier beginning or earlier incident and you simply continue down the Chain. In case you don't complete Chains you will get unflat incidents all over the place and a pc suffering from BPC. The EP of a Chain is:

1) The basic postulate off - that is the erasure.
2) Floating Needle
3) VGI's

Postulate off (1) often happens in a spectacular way. Pc spots the earlier beginning or earlier incident. There is a BD and so on. Listen up and figure out if the postulate came off. It may be in plain view and expressed by pc or he may have to be coaxed to express it. He may need to go through one more time. But unless you get the postulate off you are not there yet. But when it is off. that's it! You should stop right there.

Ending too Early
You don't stop at the first sign of an F/N. You basically ignore the F/N until the postulate is off. You simply ask if it is erasing. When the postulate comes off you call the F/N. That is your EP for that Chain.