Ref:
…
Given a knowledge of the composition and behavior of the time track, engram running by chains is so simple that any auditor begins by overcomplication. You almost can't get uncomplicated enough in engram running.
In teaching people to run engrams in 1949, my chief despair was summed up in one sentence to the group I was instructing: "All auditors talk too much.” And that's the first lesson.
The second lesson is: "All auditors acknowledge too little.” Instead of cheerily acking what the pc said and saying "Continue,” auditors are always asking for more data and usually for more data than the pc could ever give. Example: Pc: "I see a house here.” Auditor: "Okay. How big is it?”
That's not engram running, that's just lousy "Q and A.”
The proper action is: Pc: "I see a house here.” Auditor: "Okay. Continue.”
The exceptions to this rule are non-existent. This isn't a special brand of engram running. It is modern engram running. It was the first engram running and is the latest and you can put aside any complications in between.
The rule is acknowledge what the pc says and tell him to continue.
Then there's the matter of being doubtful of control. Wrong example: Auditor: "Move to yesterday. Are you there? How do you know it's yesterday? What do you see that makes you think…” Flunk, Flunk, Flunk.
Right example: Auditor: "Move to the beginning of that incident and tell me when you are there.” (Pc answers.) "What do you see?………. Good.”
Another error is a failure to take the pc's data. You take the pc's data. Never take his orders.
No auditor who knew earlier than June 1978 engram running should consider he or she knows how to run engrams.
Routine 3RA is itself. It has no dependence on earlier methods of running engrams. Failure to study and learn R3RA "because one knows about engram running” will cause a lot of case failure.
If you know old-time engram running there is no attempt here to invalidate you or that knowledge or make you wrong in any way. Those are all ways to run engrams and gave you a better grasp on it. I only wish to call to your attention that R3RA is not old-time engram running.
Engram running by chains is designated "Routine 3RA.”
It is a new triumph of simplicity. It does not demand visio, sonic or other perception at once by the pc. It develops them. …
The first thing the auditor does is to make sure the room and session are set up. This means, in other words, that the room is as comfortable as possible and free from interruptions and distractions; that the auditor's meter is set up and that the auditor's report form and worksheets are ready.
The pc is seated in the chair furthest from the door and is asked to pick up the cans (from now until the session ends the pc stays on the cans).
The auditor checks that the pc has had enough to eat by doing the metabolism test and also checks that the pc has the correct sensitivity setting by having the pc squeeze the cans and adjusting the sensitivity knob so that the needle registers one third of a dial fall when squeezing the cans.
The auditor says: "This is the session” (Tone 40).
The auditor then puts in the R (reality) factor with the pc by telling the pc briefly what he is going to do in the session.
Establish the type of chain the pc is to run by assessment. This is done using the Health Form, With Form or other Dianetic type assessment.
STEP ONE:
Locate the first incident by the command "Locate a incident of another causing you _____.” (Somatic or feeling, etc. assessed from Health Form, etc.)
STEP TWO:
Date the incident. This is done by asking: "When was it?" Take what he gives you. The PC must give a date, this is what turns on the picture in many cases.
STEP THREE:
Telling a PC to move to an approximate date he has just given moves him wrong. So, move the PC to the incident with the exact command: "Move to that incident. "
STEP FOUR:
Establish duration (length of time) of the incident. Ask: "What is the duration of the incident?" (An incident may be anything from a split second long to 15 trillion, trillion years or more long.) Exact duration always turns on the picture. If it is omitted, the PC may run black — no picture.
STEP FIVE:
Move the PC to the beginning of the incident with the exact command: "Move to the beginning of that incident. " Wait until the meter flicks.
STEP SIX:
Ask PC what he or she is looking at with exact command: "What do you see?" (If PC's eyes are open, tell PC first: "Close your eyes. ")
Acknowledge whatever PC says.
Do not ask a second question, ever.
STEP SEVEN:
Send the PC through the incident with the exact command: "Move through the incident to a point (duration) later. " (Do not use "scan” use "move”. Scan is incorrect.)
Ask nothing, say nothing, do nothing (except observe the meter or make quiet notes) while PC is going through the incident. If the PC says anything at all, half acknowledge and let him continue, using this exact command softly: "Okay, continue. "
Do not coax, distract, or question PC during this period.
STEP NINE:
When the PC reaches the end of the incident (usually PC moves or looks up) say only: "What happened?"
Take whatever PC says, acknowledge only as needful. Say nothing else, ask nothing else. When PC has told little or much and has finished talking, give him a final acknowledgement.
In going through an incident the second time one does not ask for date and duration again or any description.
After the first time through an incident and when PC has recounted it, the Auditor:
A. Tells PC: "Move to the beginning of the incident. "
B. "Tell me when you are there. "
Steps A and B can be done at one time. They will sound like one sentence: "Hove to the beginning of the incident; tell me when you are there. "
C. When PC has said he is: "Move through to the end of the incident. " (Scan is no longer used and was an incorrect procedural step as part of R3R.)
D. "Tell me what happened. "
The second and third etc. run through the same incident use the above commands.
If the pc is out of the session, out of the incident, bounces from the incident, etc. you would have to have him or her return to the beginning of the incident and move through the incident returning the pc to the incident as necessary.
The commands for this are as follows:
D. "Return to the beginning of the incident. Tell me when you are there.” (Wait to see this has happened.)
E. "Move through the end of the incident.”
F. If the pc then bounces or blows the incident you would say "Return to the incident.” (Wait for the pc to acknowledge this has happened) and then "Continue moving through the incident.”
The pc who blows an incident on a bouncer and so forth has to be put back into the incident and continue running it.
After the second time through, find out if it is erasing or going more solid. Ask: "Is the incident erasing or going more solid?"
If it is erasing go through it a third time, etc. until it is erased. Erasure is … accompanied by a Floating Needle and a cognition immediately afterwards.
…
STEP ONE A
The earlier command for Flow One is: "Is there an earlier incident of another causing you ____?" (The exact somatic or feeling used in Step One.)
…
Sometimes when you ask for an earlier incident the PC will say there isn't an earlier incident. In this case the incident you have been running may start earlier.
There really isn't a pat handling for an earlier beginning. One could ask; "Does the one we are running start earlier?”, "Is there an earlier beginning to this incident?”, "Does there seem to be an earlier starting point to this incident?” and so on. Once you establish that there was an earlier beginning then you would give the command "Move to the new beginning of the incident.”
Then continue on to B, C, D and continue as usual.
The important thing is to give the PC time to find the earlier incident or the earlier beginning.
If the PC can't find an earlier incident or an earlier beginning, run the incident you were doing on A to D again.
Step One and Step One A (going earlier) commands for Flows 2, 3 and 0 are:
STEP ONE:
"Locate an incident of you causing another _______. " (The exact somatic or feeling used in Flow 1.)
STEP ONE A:
"Is there an earlier incident of you causing another ______?" (The exact somatic or feeling used in Flow 1.)
STEP ONE:
"Locate an incident of others causing others _______ (The exact somatic or feeling used in Flow 1.)
STEP ONE A:
"Is there an earlier incident of others causing others ______?" (The exact somatic or feeling used in Flow 1.)
STEP ONE:
"Locate an incident of you causing yourself ________. " (The exact somatic of feeling used in Flow 1.)
STEP ONE A:
"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 One A commands are run on the full verbatim 1-9, A-D steps as given herein.
… A narrative item is often run to run out the physically painful experience the person has … undergone, accident, illness, operation or emotional shock. This erases the "psychic trauma" and speeds healing to a remarkable degree.
Narratives are too often just run through once or twice and abandoned. This, unfortunately, leaves the incident still charged and affecting the pc. A narrative needs to be run and run and run on that one incident. What you are doing is running the incident narrative to erasure and only going earlier similar if it starts to grind very badly. It actually is treacherous to the degree that it takes a long time and s this and that, but if you want to change somebody's life, that's how you can do it.
When you are running a narrative you always add the known incident to the command. Narrative always add the specific known incident.
The commands for Narrative R3R are:
FLOW ONE:
"Locate the time when you had/were __________.” (State, the specific known incident.)
FLOW TWO:
"Locate a time you caused another to have/to be __________.” (State, the specific known incident as per Flow One.)
FLOW THREE:
"Locate a time others caused others to have/to be __________.” (State, the specific known incident as per Flow One.)
FLOW ZERO:
"Locate, a time, when you caused yourself to have/to be __________.” (State, the specific known incident as per Flow One.)
For Secondaries it would be:
FLOW ONE:
"Locate the time when you lost a/your ________ (item). "
FLOW TWO:
"Locate the time you caused another to lose a ________ (item). "
FLOW THREE:
"Locate the time others caused others to lose a ________ item). "
FLOW ZERO:
"Locate the time when you caused yourself to lose a/your ________ (item).”
Always run narrative incidents Triple or Quad flow as above.
The earlier command is: "Is there an earlier similar incident?"
In doing R3R it is necessary that (a) one chooses things the PC is interested in and (b) one does not force a PC to run things he is protesting being run on.
If you ask if there is an earlier incident and the PC says "No" you do not just walk off from the one he was just running. You send the PC through it again and it will erase,
If you do sloppy R3R and do one thing after another without getting an F/N or an erasure, you will get the PC stuck up on the track. You complete each chain to F/N or erasure.
If a lock F/Ns you can get earlier incidents on the same chain until the PC actually runs the engram or chain of engrains.
While it is not always safe to pass an F/N and go earlier to the real engram and erase it, a PC who is only F/N'd on locks will get the engram keyed in again later. The somatic may return unless engrams are run to erasure.
An R3R session can be safely ended on a cognition and good indicators such as a cheerful happy PC.
This doesn't mean the end of all Dianetic auditing. In the next session another assessment will turn up more unwanted feelings, etc.
Dianetics is ended off only when a PC has become well and happy and remains that way. …
… And there you have it, engram running superior to any engram running ever done and giving superior and faster results.