6212C11 SHSpec-222 R2-12 Data

     [Much of the data in this lecture is given in HCOB 15Dec62 "Urgent --
R2-12, The Fatal Error" and HCOB 30Dec62 "Urgent -- Important -- Routines 2-12
and 2-10: Case Errors -- Points of Greatest Importance".]

     Don't overuse 2WC, e.g. "Did you just think of something?", in
mid-session.  "Have you thought of anything?" tends to put responsibility on
the PC.  This tells him to self-audit.  If the PC says that he has forgotten
something, don't say, "What was it?" Give the missed withhold question.

     Cleaning a needle is just fundamental auditing.  You could do it
thoroughly with an eighteen button prepcheck "In auditing", or even just
"suppress" and "invalidate" as a prepcheck assist.  You could assess the
eighteen buttons and run what reads best.  That would clean up a needle.  A
very high TA will also be brought down with this basic stuff.  Don't spend a
lot of time fixing up the case before you audit it.  You can also clean up a
needle with R2-12.

     If a case doesn't move on R2-12, assume that he is a rockslammer and take
the largest read on List One and oppose it. Or just do an oppose list on
scientology. [Cf. the green form handling, "What are you trying to prevent?"]
There is no disgrace in being a rockslammer.  Some people have lied about
whether it was pain or sensation, so as not to seem "declasse". So LRH checks "untruth", because if you write a backwards list, it is useless, as well as hard on the PC.

     There are two ways to approach the persistent dirty needle.  If you don't
have someone to do R2-12, pull missed withholds, etc.  Do a prepcheck of sorts
to clean the needle, and teach the auditor to get missed withholds.  If these
attempts to clean the needle go on too long, there is a point where the PC's
anxiety about no auditing dirties the needle.  So don't overrun this repair
action.  No-auditing can be counted on to dirty a needle.  The PC can also get
anxious if nothing is reading on nulling.  He can be afraid that you are going
to go into mid-ruds and get a dirty needle from that.

     The first symptom of a session blowing up is the PC getting a little bit
critical of the auditor.  This is the only thing LRH stops at when putting in
mid-ruds.  It is always the sign of an O/W underlying it.  To neglect it lets
it multiply into a screaming ARC break later.  So pick up "critical" with
"missed withhold" at once.  This is fundamental!  Any indication of missed
withholds makes LRH go after them.  You don't use "missed withhold" to punish
the PC but to prevent the PC from blowing up.

     In R2-12, one mistake you can make is not to know what a rock slam looks
like and therefore to neglect a rockslamming item.  The auditor knows that it
reacted, so he represents it.  This isn't invariably disastrous.  The command
value of a rockslamming item is terrific.  But the PC's Attention is not on
the slamming item.  It is on what opposes it in the GPM.  So, when you do a
represent list, it takes the PC's attention off the item that claims it and it
drives the PC around the bend.  If you really get mad at someone, when he is
rockslamming on something, represent it instead of opposing it.  He will
practically go out the bottom.  Another goof would be to null the opposition
list just to the point where all the reads are gone, without finding the
item.  Then quit, just short of getting the package.  This leaves a hidden
pair in PT.  The PC will feel better, but there is still something there.

     Nulling the represent or oppose list makes it easier for the PC to extend
it.  You can get to a point where a list can be nulled even though it is
incomplete.  Just continue the list, and you will see another rock slam turn
on, and the rock slam on the original item you were opposing will come back.

     Another error that people are making is abandoning lists that had rock
slams on them.  They can get into this mistake by representing instead of
opposing a rockslamming item.  The list will go nowhere, because there is
nowhere to go, except to the original item.  Sometimes an item which didn't
rockslam at first will unburden enough when you start to represent it to start
rockslamming.  So check for this, when the "represent" list gives a dirty
needle and no item.

     "The less attention one has in PT, the more one is likely to go down
[the] tone scale." As the PC takes his attention off past incidents to handle
PT, these past incidents collapse in on him and he dramatizes.  This is
applicable to the fact that we have found the worst attention trap there is:
RI's represented in PT.  The rock slam is caused by the fury and franticness
of the PC's attention and opposed attentions.

     Never fail to pair an item, once found.  If you only find one item of a
rockslamming pair, especially if you do this several times, after awhile you
will get no rock slams.  That amount of attention is absorbed in the bank, and
all you will get will be dead horses, thenceforth.  This isn't terribly
serious, since we can take the folder and go back to find the incomplete
packages.  If you don't do this, the packages can add up to a point where the
PC won't go clear.  An auditor who repairs a situation like this gets all the
residual gain.  The PC will already have gotten gains; he will have felt much
better, even before the repair.  It is not dangerous to put R2-12 in clumsy
hands, as long as good records are kept and common ordinary good auditing gets
done.  Doing R2-12 right is last in order of importance.

     If you simplify this down to the bare minimum, omit mid-ruds and anything
at all complicated, you have R2-10, to be run on a heavily supervised co-audit
basis.

     The only place you will have trouble is deciding whether to represent or
oppose an item that rockslams cyclically, so you don't know if it is an RI.
Learn what one of these cyclic dirty needle opposition lists looks like.  Then
you will know what you are listing.

