6303C26 SHSpec-252 Case Repair

     Worry is the occupational hazard of the auditor doing Routine 2 and 3.
The time to worry is when the PC looks and feels bad.  Don't plow on at that
point.  Find what is wrong.  Case repair can become necessary, once a goal has
been found and run.  If the goal has not been run, all it takes is a prepcheck
to straighten it out.  Sometimes a goal has been found which wasn't ready to
be found or run, and the auditor starts finding items that are out of another
GPM. Then Routine 2G comes into case repair.  [See HCOB 13Apr63 "Routine 2G
... " and 6303C21 SHSpec-251 "R2G Series"] The actions you should take when
one goal has been run and it has disappeared are resident in R2G1 or R2G2,
not in R3M.  You list goals against items, null old lists, run R2G1,
prepcheck an old goal, etc.  If you've got items from a different GPM, in
order to find a goal from the items you have got, you need to use R2G.  You
will appreciate the fact that some Class IV has checked out a goal and
verified that it rocket read, when you try to find the matching items.

     Say you had an old goal, which has been listed out on 114 lines and which
no longer ticks, but on which there was once an F/N.  Or say someone had a
wrongly worded source list, or someone made up his own line plot and got
sick.  The primary datum of all case repair applies to all these situations:
all these weird actions are incapable of deranging a GPM.  GPM's are Almost
impervious to improper R3M, though the PC can be made sick and caved in.
So at any stage of case repair, anything that was done right will stay right,
and anything done wrong can be corrected.  R3M stops working where it is done
wrong.  Anything that has been found on the PC has been found, even if it is
not correctly aligned as yet.  That an item was found out of place doesn't
alter the GPM where it belongs.  R3M will still work fine.

     We can call the whole bank the Goals Problem Masses and one GPM a GPM.
One goal and a packet of items equals a GPM.  R3M is what handles the repair
of messed up GPM's.

     If you want to know exactly what a GPM is and the explanation for the
formation of the GPM, read DMSMH.  Wherever it says "engram" in the
explanation of why people have engrams, put in "item" or "GPM".  It is quite
interesting.  There is a reason why the thetan postulated each goal.  It was
born out of the goal that the thetan has just survived.  Only the first goal
of the bank is postulated from nothing.

     The only thing that can upset a GPM is the exact auditing that we give
it.  It hangs together by violence or lack of it, so it is accustomed to
violence and mistakes.  Practically no auditing goof can affect it, though you
can make a PC unhappy and miserably uncomfortable.  By making auditing goofs,
you will upset the PC, but you won't upset his bank.  However, you are not
running the PC.  You are running a GPM with the PC's cooperation.

     The varying length of a GPM depends on how well it served the PC as a
survival mechanism.  That doesn't vary much, although the difference of line
plots gives the appearance of more variation.  This occurs because some items
found are extraneous, and others are strays from other line plots.

     If you can't find anything while doing R3M, you have goofed, and you are
looking in the wrong place.  It is not that there is nothing there or that the
GPM has gotten messed up.

     In case repair at any stage of auditing the GPM, find the first wrong
action that you can find behind you and do it right.  If a Piece or item of a
GPM is missing, you can always find it and put it in.  You can do a goals
"oppose" list to start it and stop it.  Also, don't just straighten out the
PCs.  Straighten out the auditor who goofed.  Get him to study the bulletins
and find what he didn't get.  It could be that he never read them!  Otherwise,
he will keep making the same mistake.

     Handle a case repair as though it were a clear test.  Compare the goal to
the line plot and see if they relate.  Put in buttons on the goal.  Get it to
fire or at least tick.  Go over your line plot and read each item against the
meter.  If one rockslams, even though it is from a source list and has been
opposed, you know the source list was improperly handled.  Any item that
reads, no matter how slightly, after having itself been opposed, came off a
wrongly done or handled list.  That is a stable datum.  If it rocket reads,
you have no guarantee that there has been a wrong way oppose.  The only
guarantee is that the list it came from is wrong.  Correct that list.

     What you want is the earliest item on the line plot that now reads.  Look
behind it at the line plot on which it appeared, and do that list correctly.
If you don't find something wrong with it, the error is earlier.  Look at
items that were found earlier.

     What happens when you do a wrong-way oppose?  It usually throws the PC
out of the right GPM into another GPM and gives you a stray item that looks
out of place on the plot.  So, seeing a stray look at the list it came from.
One test for which way to list is to call the question each way.  The one that
turns on more mass is the wrong one. You should get good enough to recognize
it by significance, as all GPM's follow the pattern in HCOB 13Mar63.

     In a case repair, having found the right item, just proceed as though the
subsequent items had never been found.

     Repair a case that needs repair.  Don't just blunder on.  If the PC ARC
breaks, use the assessment bulletin [Bulletin not available, but is based on a
list of fifteen causes of ARC breaks in R2 and R3, given in HCOB 14Mar63
"Urgent -- Routine 2 - Routine 3:  ARC Breaks, Handling of", p. 3] to find out
what was really wrong.  Don't just try to spot it or guess.  The cause of a
rough ARC break is withheld from both the auditor and the PC.

     Don't put figure-figure into what you are doing.  Just be sure that you
are doing R3M right.