41
HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex
HCO BULLETIN OF 11 DECEMBER 1978
ISSUE I
_LIMITED_
_DISTRIBUTION_
Advanced Courses
Specialist
Checksheet
ACS Auditors
ACS C/Ses
_NED for OTs Series 41_
_C O N F I D E N T I A L_
_HANDLING BTs MESSED UP ON OT III_
On OT III the PreOT is Clear but running engrams, and where he
made a mistake on one of these, he'd get messed up. In some instances
the rule of "no engram running on a clear" is violated on OT III.
If BTs and clusters who were messed up on running OT III are
not repaired, the PreOT on NED for OTs can run into despair, mystery
and get into an on and on and on grind on it. This has to be repaired
at the beginning of NED for OTs and may have to be returned to later
in the Pgm.
Unblown BTs or clusters, or BTs and clusters messsed up on OT
III, are sometimes at a distance of 6 - 8 - 10 feet out from the body.
This is a perimeter you wouldn't normally think to handle. They blew
out to this perimeter and stuck there.
Up until now PreOTs on Solo OT III didn't have the data on
"earlier Incident I", and "earlier universe" and you will find misses
on this which will be picked up by doing an LDN OT IIIRB.
There will also be engram errors made in Solo OT III, which
are repaired by assessing an L3RF on the BT or cluster and indicating
the reading line.
_EXAMPLES OF ERRORS_
A BT who had no incident (Inc II or Inc I) and tried to run
someone else's;
HCOB 11.12.78
Confidential - 2 -
A BT who tried to run someone else's and didn't run his own;
A BT who thinks he is an Inc I;
A BT who thinks he is an Inc II;
A BT who think he is a picture; (some BTs will mock up or
become whatever is suggested - hence you get a recurrency of picture
due to copying).
A BT who didn't have any engram and tried to run someone
else's;
A BT who went Clear and tried to run other people's incidents;
A BT with an earlier Inc I (or Inc Is);
A BT with an earlier universe(s);
The incident was erased and was run more, mocked up by those
who didn't have it, and were told to go earlier, resulting in
misownerhip;
A _later_ similar incident mistaken for the same incident;
A wrong indication such as thinking or indicating it's a
cluster when it's really a BT - causing it to go black;
BTs or clusters who tried to blow but hung up against other
BTs or clusters or ridges or bones.
A cumulative cluster for which the original (basic) incident
was never found.
_HANDLING_
The above are to be handled in Step 4 of the Rundown (HCOB 1
Nov 78, Issue II, NED for OTs Series 27) as additional steps, given
below, or at any later point in the Rundown when encountered. A
special list has been made up of the above which may be used. The
danger of using the list is that you may get several in restim. So if
you get a read on the list handle it, and handle the right one.
HCOB 11.12.78 I
Confidential - 3 -
_Addition to Step 4:_
Step 4h) LDN OT IIIRB
Step 4i) "A BT or cluster messed up in running OT III?"
If this reads, locate the BT or cluster and assess
the NED for OTs "Repair List for Errors in Running OT III",
and find what the error was. And blow the BT or cluster,if
he doesn't blow on indication, by completing the OT III
action. Also NED for OTs techniques may be used if this
does not seem to resolve it.
After handling many of these you will get a sudden series of
blows as the barrier holding them has been removed.
L. RON HUBBARD
FOUNDER
LRH:dm:kjm
Copyright (c) 1978
by L. Ron Hubbard
ALL RIGHTS RESERVED
HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex
HCO BULLETIN OF 11 DECEMBER 1978
ISSUE II
_LIMITED_
_DISTRIBUTION_
Advanced Courses
Specialist
Checksheet
ACS Auditors
ACS C/Ses
_NED for OTs Series 42_
_C O N F I D E N T I A L_
_REPAIR LIST FOR ERRORS IN OT III_
This list is used to repair and blow BTs or clusters messed up
in running OT III. The danger of using this list is that you may get
several in restim. So if you get a read on the list handle it, and
handle the right one.
_INSTRUCTIONS_
A. _"A_BT_or_cluster_messed_up_in_running_OT_III?"_ (If this
reads, do B below. If no read, check "Suppressed?" and
"Invalidated?")
B. Pre-OT finds the BT or cluster by position in, on or
around (outside) the body. (Same BT or cluster that
read in A above and same meter read.)
C. _Assess_ down this list with Pre-OT's attention on that
BT or cluster, until you get a read, and _indicate_ the
reading line.
D. If no blow on indication, _complete_the_OT_III_action,_
to blow of the BT or cluster.
E. If no blow on D above, or you can't complete the OT III
action on that same BT or cluster, continue to assess
down this Repair List to next reading line, as there
could have been more than one error. Handle per steps
HCOB 11.12.78 II
Confidential - 2 -
C and D. (NB: You should check "Suppressed?" and
"Invalidated?" on "Earlier Inc I" and "Earlier Universe?"
if no read on either.)
F. When BT or cluster blown, return to Step A and handle per
Steps B - E. Repeat this sequence A - E until Step A no
longer reads and just F/Ns on the question.
_CAUTIONS_
After handling a BT or cluster do _not_ recheck or repeat the
Repair list line, as doing so would invalidate the fact that you have
handled it, and would restimulate others, cause others to mock up
(copy) what was just handled. Only question A is rechecked.
Be sure to handle fully to blow the same BT or cluster you
started with, and do not restimulate others, or jump from one BT or
cluster to another.
You could use other NED for OTs techniques, (such as "What?
Who?' or "Jolting the BT a bit earlier"), if the above Steps A - E do
not resolve it. You fill find that most blow either on _indication_of_
_the_error_ or on _completing_the_OT_III_action._ "Earlier Inc I"
(sometimes several earlier) or "Earlier Universe" most commonly are
the reason and produce blows.
_REPAIR LIST FOR ERRORS IN RUNNING OT III_
1. AN EARLIER INC I? ___________
2. AN EARLIER UNIVERSE? ___________
3. A BT WHO HAD NO INCIDENT II AND TRIED TO RUN
SOMEONE ELSE'S? ___________
4. A BT WHO HAD NO INCIDENT I AND TRIED TO RUN
SOMEONE ELSE'S? ___________
5. A BT WHO TRIED TO RUN SOMEONE ELSE'S AND DIDN'T
RUN HIS OWN? ___________
6. A BT WHO THINKS HE IS AN INC I? ___________
7. A BT WHO THINKS HE IS AN INC II? ___________
8. A BT WHO THINKS HE IS A PICTURE? ___________
HCOB 11.12.78 II
Confidential - 3 -
9. A BT WHO DIDN'T HAVE ANY ENGRAM AND TRIED TO
RUN SOMEONE ELSE'S? ___________
10. A BT WHO WENT CLEAR AND TRIED TO RUN OTHER
PEOPLE'S INCIDENTS? ___________
11. THE INCIDENTS WAS ERASED AND WAS RUN MORE AND
MOCKED UP BY THOSE WHO DIDN'T HAVE IT? ___________
12. THE INCIDENT WAS ERASED AND AND TOLD TO GO EARLIER
WHEN THERE WAS NONE? ___________
13. MISOWNERSHIP OF INCIDENT? ___________
14. A LATER SIMILAR INCIDENT MISTAKEN FOR THE SAME
INCIDENT? ___________
15. SOMETHING LATER MISTAKEN FOR SOMETHING EARLIER? ___________
16. DIDN'T GO BACK FAR ENOUGH AND JUST MOCKED IT UP
TO RUN? ___________
17. DIDN'T GET THE RIGHT INCIDENT? ___________
18. STUCK IN AN IMAGINED INCIDENT OR PICTURE? ___________
19. DELUSION? ___________
20. SAW SOMEBODY ELSE'S INCIDENT OR PICTURE AND
DIDN'T RUN HIS OWN? ___________
21. NEVER RAN HIS OWN INC II? ___________
22. NEVER RAN HIS OWN INC I? ___________
23. NEVER HAD AN INC II? ___________
24. NEVER HAD AN INC I? ___________
25. INTERRUPTED WHILE RUNNING INC II? ___________
26. INTERRUPTED WHILE RUNNING INC I? ___________
27. DIDN'T ERASE THE INCIDENT AND STILL TRYING TO
RUN IT? ___________
HCOB 11.12.78 II - 4 -
28. AN UNRUN INC II THAT WAS IN RESTIM? ___________
29. AN UNRUN INC I THAT WAS IN RESTIM? ___________
30. DIDN'T HAVE AN INC I, AND INC II DIDN'T ERASE
BECAUSE INC II HAS AN EARLIER SIMILAR INCIDENT? ___________
31. JUST WATCHED OTHERS RUN INC I AND INC II AND
DIDN'T RUN OWN? ___________
32. WENT CLEAR AND TRIED TO RUN OTHERS' INCIDENTS? ___________
33. JUMPED BTs? ___________
34. INCIDENT II WAS LEFT UNFLAT? ___________
35. INCIDENT I WAS LEFT UNFLAT? ___________
36. INCIDENT II WASN'T RUN? ___________
37. INCIDENT I WASN'T RUN? ___________
38. A WRONG INDICATION OF THINKING OR INDICATING
IT'S A CLUSTER WHEN IT'S REALLY A BT? ___________
39. A WRONG INDICATION OF THINKING OR INDICATING
IT'S A BT WHEN IT'S REALLY A CLUSTER? ___________
40. SOME OTHER WRONG INDICATION? ___________
41. TOLD SOMETHING DIDN'T READ? ___________
42. A BT OR CLUSTER WHO TRIED TO BLOW BUT HIT A
BONE AND STUCK? ___________
43. A BT OR CLUSTER WHO TRIED TO BLOW BUT HIT A
RIDGE AND STUCK? ___________
44. A BT OR CLUSTER WHO TRIED TO BLOW BUT HIT AN
UNHANDLED BT OR CLUSTER? ___________
45 NO PLACE TO GO? ___________
46. CAN'T GO? ___________
47. MUST GO? ___________
48. A CUMULATIVE CLUSTER FOR WHICH THE ORIGINAL
(BASIC) INCIDENT WAS NEVER FOUND? ___________
49. AN EARLIER INC I SUPPRESSED? ___________
50. AN EARLIER INC I INVALIDATED? ___________
HCOB 11.12.78 II - 5 -
51. EARLIER UNIVERSE SUPPRESSED? ___________
52. EARLIER UNIVERSE INVALIDATED? ___________
53. RAN INTO AN IMPLANT THAT SAID THERE WAS
MORE EARLIER UNIVERSES THAN THERE WERE? ___________
54. A BT OR CLUSTER WITH A WRONG ITEM OR
OUT-LIST? (L4BRA) ___________
55. A BT OR CLUSTER WITH SOMETHING ELSE WRONG?
(C/S 53 on that BT or clustere.) ___________
L. RON HUBBARD
FOUNDER
LRH:dm:kjm
Copyright (c) 1978
by L. Ron Hubbard
ALL RIGHTS RESERVED
43
HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex
HCO BULLETIN OF 31 JANUARY 1979
_LIMITED_
_DISTRIBUTION_
Advanced Courses
Specialist
Checksheet
ACS Auditors
ACS C/Ses
_NED for OTs Series 43_
_C O N F I D E N T I A L_
(Amends and clarifies
NED for OTs Series 27
Ref: NED for OTs Series 41, 42
Step 4 of the NED for OTs Rundown (Series 27) is subdivided into
9 actions (4A, 4B, 4C, 4D, 4E, 4F, 4G, 4H, 4I). _The_instruction_to_
_check_interest_only_applies_to_Step_4F_ , (Repair of Past Auditing).
All the other steps, (4A - 4E, 4F - 4I) are done without checking
interest.
The usual rules of not running anything that doesn't read, and
checking for false read or protest if the pc is not interested or
protesty, apply to all steps.
_ADDITIONAL ACTION_
After running or handling any category, one should check whether
this acted as a wrong item (or wrong indication) to other BTs to whom
it did not apply, but only if there seems to be trouble.
_Example 1:_ Auditor completes handling "BTs who went Clear and
were audited on engrams". Auditor can then check
"Did `went Clear and then audited on egrams', act
as a wrong item for other BTs to whom it did not
apply?" and if reading indicates this was a wrong
item to the others.
_Example 2:_ Auditor completes handling "BTs audited past
- 1 -
HCOB 31.1.79
erasure". Then auditor can check "Did `audited
past erasure' act as a wrong item to other BTs?"
And if reading, indicate.
If discomfort or lack of GIs seems to indicate trouble has
occurred be sure to check if it has acted as a wrong item, however you
can also use the Repair List (NED for OTs Series 24).
This pheonmenon of other BTs taking on a wrong item by copying
what is run on other BTs tends to happen on any category or button
being run. It happens to a far greater degree if an Overrun occurs,
i.e. one goes on trying to handle the same category or button after it
has been handled, and starts in on a new area of the body or new
category using the same category or button that has just been handled.
Sometimes when using a category or button, a series of automatic
blows will occur, you will get a floating TA, and this is the EP for
that action and the EP for the session. Hence the rule of short
sessioning on NED for OTs and ending off on a floating TA.
L. RON HUBBARD
FOUNDER
LRH:dm:kjm
Copyright (c) 1978
by L. Ron Hubbard
ALL RIGHTS RESERVED
47
HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex
HCO BULLETIN OF 27 OCTOBER 1979
_LIMITED_
_DISTRIBUTION_
Advanced Courses
Specialist
Checksheet
ACS Auditors
ACS C/Ses
_NED for OTs Series 47_
_C O N F I D E N T I A L_
_VALENCE TECHNIQUE ADDITION_
_References:_
HCOB 17 SEP 78 I NOTs Series 7, VALENCES
HCOB 19 NOV 78 L & N LISTS - THE ITEM "ME"
HCOB 9 FEB 79 II NOTs Series 44, WRONG ITEMS
HCOB 1 AUG 68 THE LAWS OF LISTING AND NULLING
HCOB 17 MAR 74 TWC, USING WRONG QUESTIONS
HCOB 11 APR 77 LIST ERRORS, CORRECTION OF
_LISTING FOR THE ITEM_
(Warning: All HCOBs and material on Listing Errors
apply to this procedure.)
Step One of the NOTs Valence Technique, _" What are you? "_, is
a listing question. It is asked to find the valence the BT or cluster
is stuck in (obsessively being), thereby shifting the BT or cluster
out of that valence.
Sometimes a BT or cluster will answer at first with a wrong
item or items. Then there won't be any valence shift, nor will there
be any blow. Finding the correct item (the valence the BT or cluster
is obsessively being), will shift the BT or cluster out of that
valence, and remaining steps of acknowledging the item, and asking
"Who are you?" will produce the cognition: "I'm me", and it will blow.
The correct item in answer to the question: "What are you?"
will read. If there is no read on the first item, one has to _list_ from
- 1 -
HCOB 27.10.79
the BT or cluster to get a reading item. It is often a 6 or 10 item
list (but could be shorter, including the first item on the list). The
following examples are given to show what such a list could look like.
The items in these examples and the size of reads shown, are not for
reference but are purely by way of illustration.
_Example 1_ :
" _What are you?_ "
A tree
A tree trunk
A branch
A twig
A broken limb LF - F/N (The item)
_Example 2_ :
" _What are you?_ "
A sword
An arena
A crowd
A wild animal
A lion
Dust
Blood
A dying man
A gladiator F - F/N (The item)
_Example 3_ :
" _What are you?_ "
A brain LFBD - F/N (The item)
_Example 4_ :
" _What are you?_ "
There is _no) answer from the BT
or cluster.
The technique used here is to run
"Hello and Okay" (See HCOB 17 SEP 78
Issue I NoTs Series 7, page 4) on the
BT or cluster.
When it is answering up, then proceed
as above in other examples. (Note:
BTs or clusters occasionally blow on
"Hello and Okay".)
AFTER GETTING THE ITEM, ALWAYS ACKNOWLEDGE IT.
- 2 -
[missing page]
HCOB 27.10.79
of the case when this listing action has been done, and to at once
suspect and handle any out-list/wrong item.
Despite the danger of listing errors, it will be necessary to
use this technique of listing for the item, at some point on any case
being audited on NED for OTs, since BTs and clusters often begin by
giving wrong items in answer to the question: "What are you?".
However, a good auditor can be trained to L & N successfully and get
the right item. The indicators of a wrong item (see Laws of L & N) are
very obvious, both to the auditor and C/S, and bring about a dramatic
case resurgence when spotted and corrected.
_HANDLING A WRONG ITEM_
Immediately when the PreOTs GIs go out or BIs appear in the
session the auditor must check for"A wrong item","An out-list?", and
handle. Find where the BT or cluster with the wrong item or out-list
is by position in relation to the body, and find and correct the wrong
item/out-list on that BT or cluster. After locating and indicating the
wrong item or list BPC, _always_ follow through and find the right item,
and continue the steps of the Valence Technique until the BT or
cluster blows. There may be more than one BT or cluster with a wrong
item or out-list, so it is essential to locate the BT or cluster by
position in relation to the body.
After handling the BT or cluster to a blow, check your
original question ("Wrong item?", "List error?") again to ensure there
are no more BTs or clusters with a wrong item. _Don't_ go on trying to
repair wrong items when the question"Wrong item?"ceases to read or
F/Ns, or you will start messing up BTs and clusters who did not have
that wrong with them.
If difficulty is encountered in repairing a list error, it
could be sitting on an earlier out-list or wrong item on that BT or
cluster.
An L4BRA can be used to repair a wrong item or out-list on a
BT or cluster, but if so the list must be used Method 3, and care used
to find the BT or cluster by position, and to handle each BT or
cluster encountered to blow.
_POSSIBLE ERRORS_
Errors that could possibly be made and could be anticipated on
this technique are:
(a) The auditor missing the read on the first item and
causing overlisting,
(b) Listing past the first reading item (overlisting),
(c) Leaving a BT or cluster with a wrong item,
(d) Leaving a BT or cluster not blown or only partially
- 4 -
HCOB 27.10.79
blown,
(e) Going past an F/N on listing (bypassing the item),
(f) Leaving the list incomplete,
(g) Jumping from one BT or cluster to another without
completing the first one started,
(h) Overworking the question"Wrong item?"and trying to repair
other BTs who didn't have that wrong with them.
(Remember that all items are wrong to some degree, as the
only really right item is"Me".)
These possible errors could even be assessed if need be.
_OK TO AUDIT OR C/S_
It is called to attention that the March 66 HCO PLs on High
Crime Policy apply to this issue and its references, which must be
High Crimed by any auditor or C/S before using them.
_FLUB, CRAM, RETREAD SYSTEM_
The materials of L & N are covered on Class IV, so there is no
excuse for an auditor to flub L & N, nor to be ignorant of the Laws of
L & N.
The Flub, Cram, Retread System means that on the first auditor
flub he goes to Cramming on the materials flubbed, one more flub on
these materials and he goes to Retread. It is a system put in at Flag
to ensure that there were no failures on FCCIs with new internes
auditing in the HGC. It is a proven workable system. It is imperative,
mandatory, that the Flub, Cram, Retread System be used on this listing
technique on NED for OTs, and no C/S, Cramming Officer, nor Tech/Qual
executive may get reasonable about this, nor allow any persuasion or
pressure to undermine or counter this system.
Despite the liability to the pc if flubbed, actions such as L
& N, L & N Repair, and Dating/Locating, are actually easy to do
correctly, produce spectacular results when done right, and are
sometimes necessary auditing techniques. So don't get reasonable about
demanding that these actions be done correctly. Their success depends
on the auditor's TRs, metering, no misunderstoods and thorough grasp
of the materials.
IT IS THEREFORE MADE A COMM EV OFFENCE NOT TO USE THE FLUB,
CRAM, RETREAD SYSTEM ON THIS NOTs LISTING TECHNIQUE, AND IT IS ALSO
COMM EV-ABLE TO DECRY OR COUNTER THIS SYSTEM.
Should an auditor flub again after Retread he or she goes to
full Retrain from the bottom up per C/S Series 84.
Most auditors are keen to audit well, and learn their
- 5 -
HCOB 27.10.79
materials and produce miracles as a matter of course. If they do not,
then their MUs, False Data must be cleaned up, and the materials
thoroughly restudied so that they will get the expected excellent
results from standard application of the Tech.
Another factor on flubby auditors is that sometimes an auditor
(or C/S) will dramatize the same out-tech on pcs that exists on
his/her own case. Therefore the attention of the C/S or Senior C/S is
called to this point, and the case of a flubbing Tech/Qual person
should be checked for out-tech and if there is any get it corrected in
addition to the Cramming or Retread action. (Lest this paragraph be
misconstrued it does not change policy in any way, and"case on post"is
_not_ an extenuating circumstance in any Justice action, nor may it be
used as an excuse for any failure to know and apply the Tech; besides,
to plead"case"as an excuse would be beneath contempt for any
professional auditor, C/S, supervisor, etc.)
Then in addition to cleaning up any out-tech found on that
person's case, handle the auditor and C/S who flubbed and didn't
handle it, too.
If despite the above handlings the same person persists in
repeating the same errors, then you up against a case situation
described in HCOB 8 MAR 62 THE BAD"AUDITOR", and HCOB 15 MAR 62
SUPPRESSORS, and such a person must be removed from Tech/Qual lines
for the sake of others. This label should not be assigned lightly, and
the supervisors of such a student and their seniors must be named as
Interested Parties to the Comm Ev which would look into WIAC PL
outnesses, graduating an overt product, failure to use Study Tech and
Student Corrective Actions.
_SUMMARY_
Very often, especially early on the NOTs program, BTs and
clusters will blow on inspection, or on finding where the BT or
cluster is, or before the steps of the Valence Technique have been
done. One must mot seek to carry on auditing a BT after it has blown,
as this would result in other BTs and clusters copying and
misidentifying themselves with the blown BT.
Many BTs blow very easily. Sometimes after handling one BT or
cluster, you will get a series of easy rapid blows, or even a
repetitive or automatic blow. These points are covered in earlier NED
for OTs issues, and are not changed by anything in this issue.
This refinement in the Valence Technique will enable you to
handle and blow BTs and clusters with more accuracy and rapidity. And
there are some BTs that wouldn't have blown otherwise, that this
listing step will handle.
L. RON HUBBARD
[6] FOUNDER
HCOB 27.10.79
LRH:dm:kjm
Copyright (c) 1979
by L. Ron Hubbard
ALL RIGHTS RESERVED [7]
44
HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex
HCO BULLETIN OF 9 FEBRUARY 1979
ISSUE II
_LIMITED_
_DISTRIBUTION_
Advanced Courses
Specialist
Checksheet
ACS Auditors
ACS C/Ses
_NED for OTs Series 44_
_C O N F I D E N T I A L_
_WRONG ITEMS_
(Refer HCOB 19 Nov 79)
The reason why a wrong item (L & N error) produces such a
violent reaction is because it can key-in practically every BT in the
body.
They're all sitting on a wrong item already - what they are
being - and if you find a wrong item on an L & N list, it can give
them all another wrong item on top of the wrong item each is being.
The L & N error is a wrong item for a very large number of BTs,
hence the very heavy and violent reaction.
L. RON HUBBARD
FOUNDER
LRH:dm:kjm
Copyright (c) 1978
by L. Ron Hubbard
ALL RIGHTS RESERVED
48
HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex
HCO BULLETIN OF 20 DECEMBER 1979
_LIMITED_
_DISTRIBUTION_
Advanced Courses
Specialist
Checksheet
ACS Auditors
ACS C/Ses
_NED for OTs Series 48_
_C O N F I D E N T I A L_
_AUDITING SOMEBODY UNDER CONSTANT_
_AND CONTINUOUS PT STRESS_
( _References:_
Tape 6308C15, SHSBC 295, THE TONE ARM
HCOB 4 Sep 68 "Don't force a pc who is ill."
HCOB 24 Jul 69R SERIOUSLY ILL PCS
Rev. 24.7.78
HCOB 12 Mar 69 PHYSICALLY ILL PCs AND PRE-OTs
Book DIANETICS THE MODERN SCIENCE OF MENTAL HEALTH
Book SCIENCE OF SURVIVAL
Scientology Axiom 29
HCOB 22 Sep 78 II NOTs Series 5, MISCONCEPTIONS
HCOB 30 Sep 78 I NOTs Series 8 BASIC PRINCIPLES
UPON WHICH THE RUNDOWN IS BASED
HCOB 4 Jul 79 HANDLING CORRECTION LISTS ON OTs
HCOB 22 Dec 79 FLYING RUDS AT OT III AND ABOVE)
A pc or Pre-OT living in an dangerous environment or under
continuous PT stress is subject to the rudiments going out between
sessions and is subject to continuous restimulation. Under such
circumstances one can only audit in the direction of destimulation and
handling that which is already in restimulation. To stir up anything
else on the case adds to what is already in restimulation and would
worsen the case condition. (Reference: Tape 6308C15, SHSBC 295, THE
TONE ARM) As the person is already in a state of overwhelm any error
in the auditing, or any further restimulation in the auditing could
easily make the person ill or go into a spin.
- 1 -
HCOB 20.12.79
Hence one may not audit a pc under heavy stress, or a pc who is
ill, on a major rundown nor on an Advance Program. The auditing of
cases in this condition must be accurate and flawless. The Program
and C/Sing must parallel the pc's mind and must be in the direction of
handling what has already been stirred up in life. High powered
techniques such as those used in NED for OTs, if incorrectly used
could easily plunge the pc in even deeper, but without auditing, a
person living in a dangerous environment and under constant stress is
only likely to get worse. If the person is sick as well as being
subjected to a dangerous environment, there would be no hope of
recovery without auditing. And the auditing must be powerful enough
to not only keep up with the day to day stress and restimulation, but
also to make rapid headway toward recovery.
I recently solved this dilemma with remarkable success. The
routine developed is both safe and powerfully effective. It resulted
in a remarkable resurgence ad recovery for a pc who was physically
ill, under heavy constant stress and living in a dangerous
environment. This tech is vital for the handling of such a case.
_THE THEORY OF THIS ROUTINE_
_The Importance of Rudiments on Such a Case_
A person who is under constant PT stress, or who is living in a
dangerous environment, is subject to restimulation and life knocking
the Ruds out. Therefore particular attention must be paid to keeping
the Rud in, in any auditing done on such a person. The action of
flying ruds alone is beneficial and assists the person by getting
recent and PT locks off the case. It is also very essential that the
Ruds are flown each session because auditing over out-ruds could be
enough to spin a case in this condition. (This doesn't mean that one
could or should audit other cases over out-ruds, just that the
consequences would be more disastrous here.
_Light Touch_
A person who is under stress or sick cannot usually be audited
on anything heavy, nor on major actions or programs. The worse off
the case or person is, the lighter the approach you must make in
C/Sing and auditing. There is already too much stress and
restimulation and the idea is to get what is already in restimulation
keyed out or handled - not to stir up anything else. Heavy major
actions on such a case could also cause a spin. And the auditing
itself must be accurate and flubless so as not to add any more BPC to
the case. (Ref: HCOB 4 Sep 68 "Don't force a pc who s ill.", HCOB 24
Jul 69R, Rev. 24.7.78 SERIOUSLY ILL PCs.)
_Session Length_
- 2 -
HCOB 20.12.79
A person under stress or who is sick should not be audited for
long as the person's attention span and stamina are lower that usual.
Any sessions should be short-sessioned and ended on the first win or
relief for the pc, regardless of whether the C/S for the session has
been completed.
_How to Fly Ruds on OTs_
I discovered that auditors were using the older phrasing of
rudiments questions for lower level pcs on OTs. Questions containing
the word "you", such a "Do you have an ARC break?". This is
incorrect as it is evaluative. It says whose charge it is. NOTs
Series 5, MISCONCEPTIONS and NOTS Series 8, BASIC PRINCIPLES UPON
WHICH THE RUNDOWN IS BASED, explained in full why it is important to
handle the misconception of mis-identification. It is equally
important not to ask a question which evaluates that it is the
Pre-OT's charge. (Ref: Scn Axiom 29)
The correct wording of Rudiments questions for use on OT III or
above and on NOTs are:
"Is there an ARC break?"
"Is there a present time problem?"
"Is there a withhold?"
"Is there an overt?"
"Is there an invalidation?"
"Is there an evaluation?"
Sometimes the rudiment will run and F/N and blow just on that
rudiment alone and without differentiating whose charge it is. It is
possible that the Pre-OT isn't no to differentiating whose it is.
This is how rudiments run all the time on lower level cases. It just
runs generally as the rudiment, without establishing whose it is. The
trouble you can get into is misownership, whereby you are running a
charge that belongs to a BT as if it were the Pre-OT's charge. Or the
charge of one BT is misowned as belonging to some other BT or cluster.
When misownership of charge occurs, it won't run or as-is or blow, you
can't F/N it, and it will start turning on more mass or solidity. If
you get into this sort of situation, realize that the trouble is
caused by misownerhsip and handle accordingly. But if when flying a
rudiment, or other charge found such as a reading line on a prepared
list, if it just runs and blows, realize you've had a lucky break.
Don't interrupt this to try to find out whose it is, or try to take it
up again after it has blown. This is obvious enough because as soon a
you get onto the reading rudiment or reading line the charge starts
coming off and the whole thing F/Ns and blows. This is a special
condition and if this doesn't occur, you proceed as follows.
- 3 -
HCOB 20.12.79
By using "Is there an(a). . .?" you are not evaluating whose
charge it is. Then the auditor can establish whose charge it is by
asking: "Is (charge found) yours? a BT's? a cluster's?' and indicate
which of these read. (Sometimes you may find that a charge can belong
to and read on more than one of the above, in which case you would
handle both reads. It is possible that an ARC break for example could
be shared by all present, and would simply run as the ARC break
generally, without establishing whose it is. And there is a condition
where you may find for example that it is the Pre-OT's out-rud, and
_also_ a BT's or cluster's. The question: "Is it _also_ (yours?) (a
BT's) (a cluster's?)", would be used in this case.)
Unless you get a discharge and blow of the rud as described
above, it is essential to find out if any charge found belongs really
to a BT or cluster, _when_ the charge is found. Don't fly all the ruds
for example and then ask "Are all these . . .?" as that would
generalize it. The rule is on ruds, or on a prepared list, or when
finding a charge on a case, _at_once_ check if that charge belongs to a
BT or cluster, and find where that BT or cluster is and limit the
Pre-OT's attention to that specific area. (This is also covered in
HCOB 4 Jul 79 HANDLING CORRECTION LISTS ON OTs.) And when you have
handled the rudiment or prepared list charge found on that BT or
cluster, take further actions to blow it by usual NOTs techniques.
Then the auditor continues on down the rudiments questions to
the next reading rudiment and handles it as above.
(Also see HCOB 22 Dec 79 FLYING RUDS AT OT III AND ABOVE.)
By flying the rudiment _and_ blowing the BT or cluster, you are
not only getting the lock off, but you are also handling fully what is
in restim.
_Unburdening_
Unburdening is defined in the Technical Dictionary as follows:
1. "As a basic is not at once available on any chain, one usually
unburdens it by running later engrams, secondaries and locks. The act
of unburdening would be digging off the top to get at the bottom as in
moving sand." (HCOB 23 Apr 69) 2. "The technique of thoroughly
bringing to view everything contained in an engram by scanning its
locks. Alternate running of the engram and scanning its locks bring
about a maximal release of entheta." SOS, Bk 2, pp 280-281)
This routine works on the principle of unburdening. In one
session charge is gotten off by flying the ruds and additionally
(using usual procedures of NOTs) by blowing any BT or cluster who had
that out-rud. But this may not be all there is to it. Underlying
this, there may be another BT or cluster which is also in
restimulation, but being more dormant, or due to the lowered ability
of the Pre-OT to confront and handle charge, is not immediately
available to be run. By getting off the charge that is available,
- 4 -
HCOB 20.12.79
underlying charge becomes more available to be audited. And, by
getting the ruds in, the Pre-OT's ability to confront and handle other
charge is raised. Hence, in the next session you may well find that
there is more to what was taken up in the previous session and now be
able to effect a deeper handling.
It isn't that you handled all there was in the previous session
and then more got restimulated before next session. What happens is
that in one session you unburden the charge that is already in
restimulation, then in the next session you are now able to handle
what was sitting underneath the charge you got off in the previous
ession. In other words, session by session you're able to accomplish
a deeper handling.
It works on a 24 hour basis. What you unburden in the session
on one day, becomes available to be handled in the session on the next
day.
Further data on the subject of unburdening is covered in DMSMH
and Science of Survival.
_CASE HISTORY_
The following is an example which illustrates this routine,
taken from the case history of a Pre-OT who was physically ill and
under constant heavy PT stress.
_1st session, 1st day._
The auditor began flying the rudiments. Not all ruds were flown
as the Pre-OT brightened up and had a win on spotting the source of an
upset. (None of the ruds flown in this session read as belonging to a
BT or cluster.) Time: 10 mins.
_2nd session, 1st day._
This session was begun with flying the ruds. The first ruds
flown did not read as belonging to a BT or cluster and were taken to
F/N or E/S to F/N. The PTP Rud went E/S to wholetrack medical
treatment, and a postulate that it was "Better to die than get medical
treatment", and cog on how that carried forward to PT. The Overt Rud
read as belonging to a BT, produced a series of BDs, and was blown
using the NOTS Valence Technique (per NOTs Series 7, 47). While
running this BT, heat turned on. The BT blew and so did the heat.
The auditor sought to continue the session to fly the remaining rud,
which was an error, and the TA started to climb. The auditor
indicated "Overrunning the EP of the session" and the TA BDed back
down to F/N, and the session was ended. On Say/Ask "I had a good win,
all that heat blew and I got cool". Time: 0.25 mins.
(No session was given on the 2nd day, due to no read on Metabolism
test. The Pre-OT had been on a juice only diet. At this point the
Pre-OT came off juice only.)
- 5 -
HCOB 20.12.79
_3rd session, 3rd day._
The first action done in this session was to check the area of
the body, from which the BT was blown in last session, and this was
unreading. Then a NOTs Repair List was started (as the Pre-OT had
been being audited on NOTS prior to the Illness). Several lines on
the Repair List read and were handled. Some of the lines simply F/Ned
on PT points of stress, and two of the lines uncovered and blew a BT.
After handling several questions on the Repair List, the Pre-OT
had a win, and the session was ended. Time: 0.36 mins.
_4th session, 3rd day._
The ruds were flown (very little on ruds this session), then the
NOTs Repair List was continued and the second line taken up resulted
in a BD from TA 4.5 to 3.0 and a line charge. The session was ended
with the Pre-OT in high spirits, F/N, VGIs and joking at Exams. Time:
0.16 mis.
(Of interest is that the BD above resulted from the Pre-OT recalling a
this life person who "thought he was everyone, All is one".)
-----------------
At this point the Pre-OT was put onto a biochemical handling in
addition to the auditing. This consisted of: vitamins, minerals, and
Cal/Mag to remedy deficiency; freshly squeezed fruit juice as Vit C is
said to go out of fruit juice within half an hour; and because the
Pre-OT was underweight and had been off oils and fat, a supplement of
a blend of oils (soy, walnut, peanut and safflower) preceded by taking
a balanced combination of enzymes a few minutes before eating to help
digest the oil/fat. These were taken as a supplement to te Pre-OT's
diet.
The reason for the biochemical handling is that in order to
accomplish recovery from a recurring physical condition, it is
necessary to have the enzymes, oils, minerals and vitamins necessary
for physical reconstruction. In the absence of these one could
continue to have trouble.
Quite in addition to auditing, experience has told that
biochemical necessities are needful in full recovery. (This point has
earlier been made in HCOB 12 Mar 69 PHYSICALLY ILL PCs AND PRE-OTs.)
-----------------
_5th session, 4th day._
The auditor flew all ruds, overts and inval. There was no read
on any of these ruds as "also belonging to a BT or cluster?", and the
ruds were flown to F/N or E/S/ to F/N. The ruds dealt with points of
PT stress and restimulation. The Pre-OT was vey bright after flying
- 6 -
HCOB 20.12.79
the ruds and the session was ended.
Time: 0.27 mins.
_6th session, 4th day._
All ruds, overts and inval were again flown, with very little
charge on the ruds since the previous session. The Pre-OT had a "dull
pain" which was not reading and was not taken up. The Pre-OT said
"I'm feeling much better, only have a dull pain, not in the agony I
was in, I'm more cheerful and bright, and now I'm eating again I feel
stronger." The session was ended on this. Time: 0.06 mins.
(NB: Although the Pre-OT had a dull pain, and the TA was up, it would
not have been OK to pursue this session further, as the pain was not
reading and the Pre-OT was happy with progress.)
_7th session, 6th day._
(After the last session pain turned back on again.)
In this session the auditor began by locating the area of the
body where the pain had turned on, then identifying it as coming from
a cluster. The cluster didn't answer up and so was run on "Hello &
OK" until it woke up and came into communication. Then it was blown
with NOTs Valence Technique, with a large TA BD, wide F/N, VGIs,
Pre-OT line charging and amused. (An alternate handling would have
been to assess for its mutual incident, as it was a cluster, but
Date/Locate is a bit strenuous for a sick pc and an error in it can be
very upsetting.) The sesson was ended at this point. Time: 0.11
mins, 4.0 divs TA.
(Note that this cluster has been in restimulation all along and was
the underlying cause of the stomach pain and the stomach condition.
It was unburdened in the sessions on the previous day, but did not
become available to be audited until this session. It is a classic
example of unburdening later charge off the case, and then 24 hours
later the basic charge becoming available to be audited. It was
unreading in the previous session, but in this session even though
still very dormant, it read well with LFBD.)
_8th session, 6th day._
The ruds were flown, including overts and inval. Some PT
matters came up and were F/Ned on ruds. No BTs or clusters on ruds.
Then another check was made of the body area, there were no somatics
and the area unreading. The Pre-OT felt good, and that she was better
now. The session was ended. Time: 0.08 mins. (No reacurrence of
physical condition.)
_9th session, 7th day._
The Pre-OT came to session in improved physical condition, no
somatic recurrence, but emotionally upset about events between
sessions.
- 7 -
HCOB 20.12.79
The ruds were flown which handled the stress and upsets since
the last session. No BTs or clusters were found on ruds. After
flying the ARC Break Rud and two PTPs, the needle float widened and
the Pre-OT became VGIs again and so the session was ended at this
point. Time: 0.18 mins.
In spite of the heavy enturbulation between sessions, there had
been no recurrence of the physical conditon and Pre-OT health, skin
colour, eyes, etc. continued to improve.
Subsequently the Pre-OT continued in good health and good
spirits. The biochemical handling was continued to ensure full
physical recovery. Despite extreme and heavy stress on the Pre-OT
from day to day, a full recovery to health was accomplished, with no
further relapse since, and all of this in but one week!
_THE ROUTINE_
_Routine A:_
Routine A is the special condition of a reading rudiment running
and blowing the charge on the rudiment alone and resulting in a
resurgence. This is what we call a lucky break. You'd end the
session on the win. You get a free bonus of it all blowing and
F/Ning, and you mustn't overlook this possibility. And don't then
start in on an additional action of checking for whose it is, nor
taking up another rud or anything else. End off the session on that
relief or win.
Most people are sick due to some sort of out-rudiment scene and
if you can just find the out-rud you can blow it and get a case
resurgence on that alone. So if you get a resurgence on a sick pc on a
rud alone, don't go any further. You just had a lucky break.
This doesn't apply just to NOTs, one time a girl who was sick -
nigh unto death - and in looking it over it was obvious this girl was
sitting on a withhold from her parents. There was an assessment of the
ruds, and on the reading one I asked "What might that be?" and next
thing there was charge flying off all over the place and she got a
resurgence on that alone. There wasn't even much of a discussion of
the reading rud. But the resurgence occurred, and you have to be alert
for that and don't overlook it. End off on a win.
Routine A doesn't just apply to sick pcs, you can get it at any
time on ruds on any case. It all just blows and you leave it at that.
_Routine B_
Routine B is another special condition. It applies when the pc
got sick during auditing, or within three days of last session. It
consists of an assessment made up by the C/S from a folder study of
what it might be. You're not just assessing the ruds here, as in
Routine A. It's a prepared assessment of possible causes of the
- 8 -
HCOB 20.12.79
trouble or BPC. The C/S list is assessed and you indicate the charge,
and if the assessment is accurate you can get a resurgence on that.
A pc one time got sick after a session during some auditing and
turned on a 104.5 degree temperature and still raising and he was
about to be rushed off to a hospital. The C/S looked over the folder
and made up a little assessment of about eight items that it could be
and had it assessed. The biggest read was on "wrong item" and this was
indicated. The TA BDed from about 5.0 to about 2.5 and this guy sat up
in bed and said "Oh yeah, so that's what it was!". His temperature
turned off and that was that. No further action taken. He got his
resurgence. (This doesn't mean that on Routine B you would always get
a resurgence on indication alone, but it can happen.)
Routine B differs from Routine A in that instead of the ruds, a
C/S prepared assessment based on folder study is done, and it applies
when the pc got sick during or within three days of auditing.
_Routine C:_
Routine C is the more usual routine. Routines A and B are for
special conditions. The steps of Routine C follow.
1. Fly all ruds including Overts, Invalidation and Evaluation at the
beginning of each session.
The phrasing of the Rudiments question is:
"Is there an ARC break?"
"Is there a present time problem?"
"Is there a withhold?"
"Is there an overt?"
"Is there an invalidation?"
"Is there an evaluation?"
Having gotten a read on a Rudiment question, the auditor now
establishes _whose_ it is, i.e. whether the charge belongs to a BT or
cluster or the Pre-OT, by asking: "Is it yours? a BT's? a
cluster's?". The auditor notes which of these reads, and indicates it
to the Pre-OT. If it read on a BT or on a cluster the auditor has the
Pre-OT find where the BT or cluster is by position in relation to the
body and then flies the rudiment on that BT or cluster, _and_ then blows
the BT or cluster by usual NOTs techniques. If the charge read as
belonging to the Pre-OT, the auditor simply flies the rud to F/N or
E/S to F/N.
See if any charge found belongs to a BT or cluster, _when_ found,
and handle that BT or cluster. Don't do a series of actions, such as
flying all the ruds, and then generalizing by asking if all these
- 9 -
HCOB 20.12.79
belonged to a BT or cluster.
The idea here, on Routine C, is that when getting a charge off,
to _at_once_ establish if that charge belongs to a BT or cluster that
either it (BT or cluster), or the Pre-OT, has identified with the
Pre-OT (In other word, the possibilities are that: (a) the BT or
cluster thinks it is the Pre-OT, or (b) the Pre-OT thinks the BT or
cluster is himself/herself, or both (a) and (b).)
By so doing you are handling any misconception or
misidentification. The theory of this is covered in NOTs Series 5
MISCONCEPTIONS, NOTs Series 8 BASIC PRINCIPLES ON WHICH THE RUNDOWN IS
BASED and HCOB 4 Jul 79 HANDLING CORRECTON LISTS ON OTs. These issues
must be understood for the auditor to successfully handle this, as
they explain why one must establish whose charge it is, and handle
that being.
The question asked to establish whose charge it is must not be
invalidative or evaluative (Auditor' Code, Clauses 1 & 2). That's
why you don't ask "Do _you_ have an ARC break?" (evaluation), or argue
with the Pre-OT if he/she says whose it is, or ask if he has made a
mistake in thinking it was . . .'s or anything like that
(invalidation). This is why you use "Is there a . . .?" and then you
can say "Is it yours? a BT's?" . . . or "Is it also . . .'s?"
Correctly establishing whose charge it is will bring in Good
Indicators and permit the charge to be handled. A wrong assignment of
charge will result in further misidentificaton, failure to blow the
charge, and Bad Indicators.
The handling of any ruds type question, prepared list question,
or any charge found on the case follows this pattern:
(a) The auditor gets a read on a rud question, prepared
list question, has the Pre-OT answer briefly and acknow-
ledges.
(b) The auditor establishes whose charge it is, i.e.
Pre-OT's, a BT's or a cluster's and indicates this to
the Pre-OT.
(c) If a BT or cluster charge, the position of the BT
or cluster in relation to the body is found.
(d) If not already F/Ned, the rud question (or prepared
list question or charge found) is F/Ned on the being to
whom it belongs.
(e) If the charge found belonged to a BT or cluster,
and if it has not already blown, blow it using NOTs
techniques.
_Example:_
- 10 -
HCOB 20.12.79
Auditor: "Is there an ARC break?" (no read)
"Is there a present time problem?" Fall.
Pre-OT: Answers stating the PTP.
Auditor: Acknowledges the answer.
Auditor: "Is that present time problem yours? (Fall),
a BT's? (no read), a cluster's? (no read")
The auditor indicates what read.
This PTP will either F/N (if it hasn't
already) or it is taken E/S to F/N.
(Note: If you get into a tangle ask "Is it also yours?", "Is it also
a BT's?", "Is it also a cluster's?", even "Is it also theirs?".
There's a possibility it could belong to everyone present. And
there's another condition that can occur. You ask "Is it yours?"
(Fall) "That read", and he says "Yeah" and right at that moment a
point of separation could occur. At any time some awareness of
separation can occur, (awareness of separate identity-ness, it can
occur at any time in NOTs. So also be alert for a sudden separation
when he suddenly realizes "It is not . . .'s", and don't go on
handling it as if it was!)
_Example:_
Auditor: "Is there a PTP?" Fall.
Pre-OT: "Problem about eating." Fall.
Auditor: Acknowledges.
Auditor: "Does that PTP belong to you? (no read), a BT?
(Fall), a cluster? (no read)". Auditor indi-
cates it read on "BT".
Auditor: "Where is that BT?
Pre-OT: "Ear" (no read), "Left ear lobe" (Fall).
Auditor: Acknowledges, and tells Pre-OT to put his
attention on "Left ear lobe" so as not to
jump to another BT).
"Does that BT have an earlier similar problem
about eating?" (Fall).
Pre-OT "Starving to death." LF - F/N.
Auditor: Acks then indicates the F/N.
Then (as no blow yet), (with Pre-OT's attention
still on "Left ear lobe"), the auditor has the
Pre-OT run Valence Technique to a blow of that BT.
- 11 -
HCOB 20.12.79
2. Then the auditor continues on down the rudiments until the next
reading rudiment and handles it as above. All the ruds are flown as
above, or until the Pre-OT gets relief or has a win, in which case the
session EP for a pc in this condition has been reached and the session
is ended. Even though it may be obvious by meter or by Pre-OT's
condition that there is more to handle, do not continue the session.
You will get a chance to take it up again next session.
3. In the next session again fly all the ruds in the same manner. If
you left an action incomplete in the last session, or if you suspect
there is more to handle on a charge found in the previous session take
it up and check it again. If now available to be run it will read.
Very often, the BT's of cluster's charge, destimulated (unburdened) in
the previous session, will become available to be run and handles more
fully 24 hour later. Do not be dismayed if you only get locks to
start with, by repeating this routine from session to session, the
case will unburden and you will get the underlying charge. This C/S
is actually a continuing program.
4. If the Pre-OT was being audited on the NED for OTs Advance Program
and became ill, _you_must_include_a_NOTs_Repair_List_early_in_the_
_program._ (In any event do not continue an Advance Program on a pc who
became ill or subject to continuous stress, but re-program and C/S as
above until the condition is fully handled.)
5. Always include a biochemical or nutritional handling combined with
the auditing program to get any deficiency or inadequacy in the pc's
diet remedied and to assist the body in regenerating itself.
_Note 1:_ Do not ask a Pre-OT for ". . .a BT who has a somatic?" as
that would be out-tech. (It takes two beings to produce a somatic. A
cluster could have a somatic, not a single BT. This is covered in NOTs
Series 5 MISCONCEPTIONS.)
_Note 2:_ This issue does not cancel anything in NOTs Series 34 THE
SEQUENCE FOR HANDLING A PHYSICAL CONDITION.
_SUMMARY_
The important points in this routine for auditing somebody under
constant and continuous PT stress are re-iterated here.
While it is always important to fly the Ruds in NOTs, and
disastrous to audit NOTs over out-ruds, it is of even greater
importance to fly all ruds on a Pre-OT who is under constant PT stress
or who is living in a dangerous environment. And the auditing of such
a person should begin with ruds. And flying all the ruds must be
repeated over and over, and is in itself a sort of continuing program.
It is important when getting charge off, to _at_ _once_ check if
that charge came from a BT or cluster, that either it, or the Pre-OT,
had identified with the Pre-OT. Don't go on and fly all the ruds and
then check, as that would generalize it and result in further
misidentification. Check any charge found, _when_ _found_ ,(with the
exception of Routines A and B) as to whether it belongs to a BT or
cluster, and handle with NOTs techniques.
- 12 -
HCOB 20.12.79
Auditors and C/Ses must recognize that a Pre-OT who was in good
shape and able to run Advance Program actions, when subjected to heavy
PT stress, a dangerous environment or illness, is now in a much
lowered case condition; such must not be audited over out-ruds,
audited roughly, or audited on heavy actions. A case in this
condition is easily overwhelmed. But if audited as outlined herein,
will make remarkable and rapid recovery.
Sessions on persons under stress or who are ill, should be
short, and ended on first win or relief for the pc. Even though there
is more to be handled on the case, do not press on past a win or
relief in a misguided desire to handle it all at once, as this will
plow the pc back in again. The idea is to aid recovery by keying out
locks, keeping the ruds in, and a succession of small wins which later
add up to a miracle win.
Understand the principle of unburdening which is the key point
of this routine. What you unburden in today's session will become
available to be audited in tomorrow's session. This is quite
different from day to day restimulation. What you are handling here
was already in restimulation, but has to be unburdened in order to
make it available to be handled and blown. Hence, when you unburden
charge in a session, end the session on the win or relief, and always
check in the next session to see if there is anything further on that
subject or area, which is now available to be fully handled.
On a pc who is sick or ill, combine a biochemical handling with
auditing, in order to remedy any deficiency (and remember that such
deficiencies will vary from one person to another), and in order to
permit the body to reconstruct itself and fully recover.
Whenever a pc gets ill during or within three days of auditing,
always include the Repair List or Correction List early in the program
to locate and handle the BPC.
This technical development is vital to the successful handling
of pcs under constant PT stress, or who are living in a dangerous
environment. Although it was previously known that one should not
audit pcs under stress on major actions, this routine now enables
auditors and C/Ses to handle cases in those conditions with safety,
rapidity and full success.
- 13 -
L. RON HUBBARD
FOUNDER
LRH:dm:kjm
Copyright 1979
by L. Ron Hubbard
ALL RIGHTS RESERVED