6301C08 SHSpec-227 Case Repair

     If you did the pure form of listing and opposing described in the last
lecture, you get less mass as a result.  If you start seeing more rock slams
than before and there is more mass on the PC, you have been goofing.  The best
visual indicator is the PC's skin tone.  If mass is increasing, the PC's skin
goes green or yellow or grey or black.  The eyes are also an indicator,
although they are somewhat less reliable, because going through a period of
sen. will make the eyes look "sen.-y".  But do note the PC's skin tone at the
start of the session, so that you can compare this with its later appearance.
Age is another symptom.  The PC should look younger half way through the
session.  Even hair color will change: it will get grayer or less gray.
Weight will also change, over the course of two to three sessions, in the
direction of optimum weight.  The meter should also behave better.  It should
be more responsive; there should be a cleaner needle.  Routine 2 doesn't do
much for the TA position.  The needle is more indicative.  The PC's TA can sit
at five, with the PC getting better and better.  If the TA remains motionless
throughout listing, that's fine.  After awhile, there should be some change.
It is not in the course of one session, but after several.  Eventually, there
should be improvement in a high or low TA, or the mass hasn't been cleaned
up.  Persistent low TA is worrisome.  Seeing no change in TA, look for:

     1. A wrong source

or   2. A list that should be completed.

You should be especially concerned if the PC was at 1.5 and didn't change
after a couple of packages had been found.

     Listing wrong way to makes the needle stiff and jerky.  On a right list,
the needle should free up, get clean and stay clean.  A list can go clean
needle before the item is on it, so avoid short lists.  A super-long list, say
twenty-five pages, is from wrong source or wrong way to.  Five to six pages
should do.  The wronger you are, the longer it takes.  The right way goes
fast.  When nulling a list, don't tell the PC that an item rockslammed until
you have finished nulling.  Then watch his indicators to be sure that it is
his item.  Don't shift his attention after telling him the item.  If he ARC
breaks when you have given him the item, it is wrong, and you had better get
him to go on.  He won't mind, if it was the wrong item.  If he knows it is his
item and you try to make him go on, he will ARC break.

     When do you repair a case?  When it won't run right.  The commonest error
in Routine 2 is wrong source, and the commonest source of that is an item
taken from an incomplete list.  Any item is viewed as coming from a list, even
if it was never before listed.

     The three areas that you have available to get items from are:

     1. The PC's PT session environment.

     2. His PT non-session life and livingness environment.

     3. The parts of existence.

So if the PC has several rock slams on List One, you know at once that List
One is an incomplete list.  This gives you the problem of regress: you are
always starting from a list that hasn't been written.  The auditor's
responsibility is to make sure that the list source question doesn't rockslam,
since if it does, it is obviously part of a list, so he can't use it for a
represent or a "consist of" list.  All lists start with a represent list.


     Just because something slams, you don't necessarily oppose it.  You might
try to find out what the item is from by asking, "What list question would
_______ be an answer to?"  If you have been listing from something which, when
you check it, now slams, it is wrong source.  It is not that it is "getting
unsuppressed".  So what you want to do is to find a non-rockslamming list
question that produces rock slams.  There must be no rock slam anywhere in the
list question.

     If you list from a non-rockslamming source and don't get rock slams, you
can always use the negative version, "What doesn't _______ consist of?" If you
don't get anything on "Parts of existence", try, "What isn't part of
existence?" You can also do this with List One.  If a PC has his interest
stuck on an item, find what list that item was on, and complete the list.
Once you have got a rockslamming item from a complete list, you can go ahead
and oppose it.

     What about a case that has been run a long time on wrong sources, wrong
way to, and has lots of wrong items?  This is pretty sad, but the case will
still have been improved.  Just repair it by finding the first incomplete list
on the case, even a suppositional one or a List One, or whatever.  Get a list
question of some sort that doesn't rockslam, add to the list, and try to tiger
drill alive what originally rockslammed.  If you get a rock slam while
extending, watch to see whether you keep getting them.  If you do, it shows
wrong source or wrong way to.  Try it the other way around.  If it still won't
clean up, it is wrong source.  Complete all such incomplete lists.  Where you
get RI's, oppose them, and the bric-a-brac will blow off.

     When repairing lists, just examine the genus of the list and see if it
needs completing.  Get it completed to its proper item, oppose it, and package
it up.  Before this is done, the PC will be interested in the item.
Afterwards, he will have no interest in the item; it erases.  He will cognite
on it.  The PC may have trouble remembering right items; wrong ones will be
memorable because the PC's attention is still stuck there.

     The purpose of Routine 2 is to clear away chronic PTP's and hidden
standards, so you can find and run the PC's goal.  Having found his goal, you
may still need to use Routine 2 to wipe out restimulated terminals, when the
PC caves in while running the goal.  You can use, "What does PT consist of/not
consist of?" or "What does auditing consist of/not consist of?" Everything
said here about lists also applies to goals clearing lists: Routine 3-21.
[For more data about R3-21, see pp. 332 and 356, above. More data is also
available in confidential HCOB's 7Nov62II "Routine 3-21:  The Twenty-one Steps
-- Finding Goals" and 17Nov62 "Routine 3-21".] One of the hardest things you
will use to get a rockslamming item from is a goals list.  Goals lists almost
never run out of slams.  When they do, though, they behave like any other
list.

     Remember that a rocket read is senior to a rock slam, and that in other
respects, you trust it the same.  If you find rocket reading items on a
(therefore incomplete) list, complete it to one rocket-reading item.

     The "frequency of rock slam" test is senior to the "stickier needle" test
on wrong-way-to.  Having found an RI, a PC's needle may be fine, but the
wrong-way-toness of it will beef it up.  Do it the other way.  If it still
doesn't clean up and give one rock slam on nulling, the source item must have
been from an incomplete list, so complete it.  Be prepared to be wrong, and
straighten it out.  Straighten up Routine 2 thoroughly; fix up auditing
briefly.  You could also find one rockslamming item that never got opposed.
So oppose it.

     You could take List One and ask, "What question would complete List
One?", and complete it.  This would handle most problems.

