10
HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex
HCO BULLETIN OF 16 SEPTEMBER 1978
ISSUE IV
_LIMITED_
_DISTRIBUTION_
Advanced Courses
Specialist
Checksheet
ACS Auditors
ACS C/Ses
_NED for OTs Series 10_
_C O N F I D E N T I A L_
_OT III AND DORMANT BTs_
_OT III ATTEST_
The actual fact of the case is those that have been with the guy
for quite a while and those that plunged in on a guy and those that
are real tough and real tight and so forth, when you get rid of those,
that's it. That's the end of III.
But Planet Earth was a dumping ground to end all dumping grounds.
Actually the end of OT III is when those BTs and clusters which can be
gotten into communication easily and can be made to run Incident IIs
and incident Is are gone. It's not when all BTs in the whole universe
that ever will be are gone.
_DORMANT BTs_
You can wake up very dormant BTs and clusters that actually
you've never hit on OT III - never dreamed they existed.
Many are not visible in PT. These dormant ones are not squarely
in the time stream, they're down the track a bit. You shift your
attention and pull them into PT, or your attention goes a bit out of
PT and there they are. They are not precisely in the time stream.
This solves the mystery of how an OT III can see none, get run on some
NED and it kicks them in.
It is like a whole being reviv. Dormant BTs and clusters are
stuck down the track in an incident. Dormant BTs are out of PT in
denyer chains (like "not there", "can't be there"), so they "don't
- 1 -
HCOB 16.9.78 IV
exist", yet they do exist. If you look down the track, here they
are, and if you ball them up with engram running or bad auditing, you
get real trouble, as they recoil against the body.
_PRE-OT'S PERCEPTION_
Some Pre-OT's perception is not up to perceiving BTs and clusters
and masses. Unless you raised their perception you would miss on this
Rundown. The preliminary action of "NED for OTs" is designed to raise
the Pre-OT's perception to a point where he can perceive BTs and
clusters and other beings' pictures, and this step is vital to this
RD.
L. RON HUBBARD
FOUNDER
LRH:dm:kjm
Copyright (c) 1978
by L. Ron Hubbard
ALL RIGHTS RESERVED [2]
9R
HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex
HCO BULLETIN OF 15 SEPTEMBER 1978
ISSUE IV
REVISED 13 FEBRUARY 1981
_LIMITED_
_DISTRIBUTION_
Advanced Courses
Specialist
Checksheet (Revisions in Script)
ACS Auditors
ACS C/Ses
_NED for OTs Series 9R_
_C O N F I D E N T I A L_
_CLUSTER, CUMULATIVE CLUSTER_
_HANDLING AND DATE/LOCATING_
(Ref: HCOB 25 Oct 69R CLUSTER FORMATION, CUMULATIVE)
A cluster or cumulative cluster is dated to blow, located to
blow. Dating must be accurate and precise down to the seconds and
fractions of a second. Locating must be accurate and precise. _Both_
Date and Locate steps must be taken to a blow. No misdating, no
partial dating, no locate errors, no partial locating.
A heavy pressure or somatic comes from a cluster, rather than a
single BT.
Get the type of incident (by meter read) e.g. _impact,_injury,_
_illness,_freezing,_heat_or_burning,_explosion,_implosion,_psychiatric_
incident,_implant,_electrical,_lightning,_a crash,_accident,_shot,_
etc.
_Date_the_point_when_the_cluster_was_formed._
In the case of a cumulative cluster you date the later mutual
incident first, before proceeding to the earlier mutual incident.
When the basic incident is date/located it will all blow. Singles may
be handled with Valence Technique; they may also be handled with Inc
II and Inc I, when appropriate.
- 1 -
HCOB 15.9.78R IV
It is essential to check for and handle copies. This is done _by_
_spotting_the_fact_that_someone_else_copied_it_ and it usually goes. If
not, you could _find_the_BT_or_cluster_who_is_copying_what_was_just_run_
and blow it off
Dating and locating must be precisely and accurately done.
The procedure is:
1. Type of incident that made the cluster
2. Date to blow
3. Locate to blow
4. Handle any remaining individuals and copies.
-------------
Note that you can get _a_wrong_date_if_other_BTs_ are _stirred_up._
A correct date or location for one BT or cluster can be a wrong date
or wrong location for another BT or cluster, because it doesn't apply
to them. This will cause mass and pressure to build up. And the mass
and pressure will relieve on the indication of "wrong date" or "wrong
location" to the appropriate BT. A technique powerful enough to
handle BTs and clusters, is also powerful enough to mess them up, if
done wrong. Wrong or partial dates or lcoations will hang them up.
_IMPLANT DATES_
False dates given in an implant can be confused with the actual
date of the implant. It is necessary to be able to tell the
difference between implant dates and actual dates. Implant dates
won't read or won't read much on the meter. You can meter check for
_"false_date_given_in_an_implant"_ , and the read will tell, and the
implant dates will no longer read. Actual dates will read well.
_CAUTION_
Remember that in any dating you can also be falsely dating some
other BT or cluster so you must _check_ , after any dating or locating
and getting a blow _whether_this_served_as_a_wrong_D/L_on_any_other_BT_
_or_cluster_ and indicate it as such.
Because D/Ling is dicey in NED for OTs you hold it to a minimum
and only do it as a sort of last resort when other techniques don't
work.
- 2 -
HCOB 15.9.78R IV
L. RON HUBBARD
FOUNDER
Assisted by
Snr C/S Int Assistant
Accepted by the
BOARD OF DIRECTORS
of the
CHURCH OF SCIENTOLOGY
OF CALIFORNIA
LRH:dm:kjm
Copyright (c) 1978
by L. Ron Hubbard
ALL RIGHTS RESERVED [3]
11
HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex
HCO BULLETIN OF 30 SEPTEMBER 1978
ISSUE II
_LIMITED_
_DISTRIBUTION_
Advanced Courses
Specialist
Checksheet
ACS Auditors
ACS C/Ses
_NED for OTs Series 11_
_C O N F I D E N T I A L_
_THE FIRST STEP OF NED FOR OTs_
The first step of NED for OTs consists of repairing past
mis-auditing. You check "Past auditing" first, and if it's not
reading, no pc interest, you skip it. But if later in the Rundown you
run into a bog, TA goes high, or any kind of grind or mess up, you
recheck past auditing, and handle. Repair of engram running is
limited to simply indication. You mustn't get into continuing to run
the engram or you'll be running engrams on a Clear, as you aren't
running them on a Clear and aren't repairing them on a Clear, you are
repairing them on a BT.
_THE BUG ON NED FOR OTs_
If you get a wrong item on somebody they will now have that item
- it persists; e.g. you run "sore toe" on somebody who doesn't have
one, they'll end up with a sore toe! If you now try to handle sore
toe with auditing it will worsen. Because it was a wrong item in the
first place. You have to repair the wrong item. A BT could be run on
a non-existent somatic, and to be obliging mocked it up. They can get
run on imaginary incidents and on things that are not their track so
what was run could have been false.
If the pc was run on an unreading item, BTs will be activated,
but they don't have that item either. It's a false assumption there
was something there to run - that's their misconception foisted off on
them by being given the belief that the item existed or read. When
called on to run something, they will furnish copies, misowned and
manufactured items. You need to check for BTs run on wrong items,
unreading items and sort it out.
- 1 -
HCOB 30.9.78 II
Some BTs went exterior and were audited past it. Some BTs had
already gone Clear - not just on the Clearing Course - some went Clear
on Objectives. So you don't just have Dianetic auditing on somebody
after Clear. You also have Dianetic auditing on BTs after they went
Clear! Resulting in invalidation of the State of Clear, the mistake
of misowning others' pictures, and then misidentification of identity.
NED auditing after Clear applies to BTs as well as Pre-OTs. So there
are residual BTs with invalidated erasure, invalidated Clearing. And
the originally overrun thetan may have blown and left copies of the
overrun.
Grinding an incident on Dianetics or NED will result in some BTs
run past erasure, so they have to mock it up again to run. Or they
never got to basic and erasure because the auditor never asked for
E/Beg or E/Sim, and were left hanging incomplete on the chain. And
other BTs will copy all this obsessively.
Out L & N lists and wrong items will do the same thing, and also
can be repaired.
Auditor command flubs, lack of acknowledgement, couldn't hear the
auditor, session distractions - all these will hang up BTs. Even
false dates could be copied - they can be twice removed from reality.
In trying to date something now you could wind up dating the wrong
date, or dating the date that the wrong date was given. And it might
not have been that BT's or cluster's incident that was being dated in
the first place - the incident may have been misowned - not their
incident.
YOU CAN'T RUN NED FOR OTs ON SOMEBODY WHO HAS BEEN RUN ON WRONG
OR UNREADING ITEMS WITHOUT REPAIRING THEM.
Also beware of getting into over-correction, because what you are
correcting on one BT, can start uncorrecting on another BT.
So you check _"past_auditing"_ for read and _interest_ as the first
step. If it reads and Pre-OT is interested you handle it. If not,
skip it, but be alert and if Pre-OT hits a bog you recheck past
auditing. Remember not to run anything, just indicate it.
This doesn't mean that all previous auditing was bad - far from
it! But some auditors due to poor training, bad metering, or nasty
habits will be found to have messed up cases. So you repair past
auditing by auditors - by auditor's name. (And also see that such
auditors are handled too.)
That's the bug on NED for OTs - you can collide with BTs and
Clusters messed up in past auditing, and this can recoil heavily and
physically upset the Pre-OT. So you keep the Repair List handy and if
you run into a bog, use the Repair List and next session C/S to take
up past auditing, remembering not to continue to run engrams but only
indicate.
- 2 -
HCOB 30.9.78 II
_REPAIRING PAST AUDITING BY AUDITOR'S NAME_
Make a list of names of auditors and test these for read.
Include self-auditing and solo auditing too. Those that read, you
repair the items run by that auditor, or in self-auditing. And make
provision for occluded auditing. You may think you've got it all,
only to find an occluded session or sessions spring to view later.
This is why you must teach FESers to FES and make up FFTs, that
include the auditor's name.
And that's why the Advanced Courses Specialist auditor must know
what he's doing in training to deliver this Rundown. It's not a piece
of cake.
Do it flawlessly and produce the spectacular results the Rundown
is capable of.
L. RON HUBBARD
FOUNDER
LRH:dm:kjm
Copyright (c) 1978
by L. Ron Hubbard
ALL RIGHTS RESERVED [3]
12
HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex
HCO BULLETIN OF 16 SEPTEMBER 1978
ISSUE II
_LIMITED_
_DISTRIBUTION_
Advanced Courses
Specialist
Checksheet
ACS Auditors
ACS C/Ses
_NED for OTs Series 12_
_C O N F I D E N T I A L_
_REPAIRING AND BLOWING BTs AND CLUSTERS_
_FROM PAST AUDITING OR MISAUDITING_
_STEPS_
1. What was being run?
2. What was the error in running?
3. Indicate.
4. Who was it run on?
(Find BT or cluster by position in the body.)
5. Blow BT or cluster.
6. Copies.
_HANDLING PAST DIANETICS, NED, OR R3R_
Prior to auditing have the folders and a Full Flow Table (FFT)
made up which contains all Dianetic, NED, XDN, or any other R3R items
that have been run, in date order, including the _name_of_the_auditor_
who ran these. (This includes any somatic or narrative item that was
audited Dianetically.) Dianetic lists as well as L & N lists should
also be available. (N.B. Some old timers may have been audited on
secondaries and engrams prior to folder records having been kept, and
there is always the possibility of false reports and unrecorded items
having been run.) This repair action is done by name of auditor, and
- 1 -
HCOB 16.9.78 II
those auditors who audited the case on engram running after Clear, or
who most grossly misaudited the case, will be found to be charged
(reading) and it is their auditing which most likely will need to be
repaired. Auditors whose names come up as aving grossly misaudited
the case in the past should be Crammed or Retreaded or Retrained or
subject of an Ethics action in order to safeguard any other pc in
future.
Make up a list of names of auditors from the Full Flow Table and
include "Self-auditing" and "Solo Auditing". Allow for the
possibility of occluded auditing showing up later as charge is taken
off during this repair.
Assess the list of auditor names, including self-auditing and
Solo auditing, for read and note size of read. Start with the largest
reading, and repair the items run by that auditor as follows:
1. Take the Dianetic item that was run, e.g. "Pain in the
Zorch", and test it for read. (If no read, skit it.).
2. Find the error in running. Such as: "Unreading item",
"Wrong item", "No such item ever existed", "Run past erasure", etc.
(Usually the Pre-OT will be able to get this. If not the auditor can
find out quickly by meter.).
3. _Indicate_ the BPC found. (ONLY indicate, do _not_ start running
anything.)
4. _"Is_the_BT_or_cluster_this_was_run_on_still_around?"_ ( _And_
_note_whether_this_reads_ , it won't read if the BT or cluster has
already blown.
Have the Pre-OT fond the BT or cluster by position on the
body - sometimes the BT or cluster will blow on inspection on this
step alone; if it doesn't,
5. Blow the BT or cluster.
6. Copies. The auditor asks "copy?" and if reading has any
copies spotted and blown. Often the BT or cluster who originally ran
the item will have blown, leaving BTs or clusters who copied the
auditing or copied the overrun, etc. And don't nag the Pre-OT for
copies or you'll start some other BT copying now.
As with any Repair auditing this can very quickly repaired, and
the auditor must be alert for this and not get into overcorrection.
You must also be _alert_ for what you _are_correcting_on_one_BT_or_
_cluster_uncorrecting_on_another_BT_or_cluster_ ; e.g. "Overrun" may be
correct for one, but not correct for another. You can check for this
and if so, indicate that "Overrun" did not apply to the rest.
Step 2 above - Finding the error - may go earlier similar, the
same BT or cluster may ave been mis-audited in an even earlier session
or sessions, and these too may need to be repaired. But only if
- 2 -
HCOB 16.9.78 II
earlier auditing BPC exists on the BT or cluster you started with or
you'll jump from one BT or cluster to another.
Handle each reading item run by the assessed (reading) auditor in
the sequence these items were run. Then take next best reading
auditor by name or reassess the list of auditors. Be very alert for
this whole repair action EPing well before all auditors or items have
been addressed and when that occurs and it off.
_STUCK PICTURE REMEDY_
1. The stuck picture.
2. What was the error in running?
3. Indicate.
4. _Who_was_it_run_on,_or_whose_stuck_picture_is_it?_
5. Blow BT or cluster.
6. Copies.
_AUDITING ITSELF MAKING A CLUSTER_
Seriously bad or rough auditing, Code Breaks, overruns, demanding
something that isn't there, asking for an earlier similar that didn't
exist, continuing to run an incident that has already erased, grinding
incidents, running unreading/uncharged items or wrong items, will mess
up BTs and clusters that were not in restimulation or who were
dormant. When very bad such a session can itself have been a cluster
making incident and is the _latest_mutual_incident_for_those_BTs_and_
_clusters_ stirred up in that session. There will have been
considerable cross-copying. Do not attempt to R3R or R3Ra such a
session. Handle it as described above under Repairing Past Auditing.
Repeat those steps until all BTs and clusters have been blown off that
session.
_PAST MIS-METERING, MIS-DATING OR LOCATING_
If the Pre-OT has been mis-metered in the past this may need to
be repaired.
Meter evaluation by which is meant the auditor keeps telling the
pc that this or that didn't read, etc., can be highly evaluative and
invalidative, especially when that auditor was mis-reading the meter.
The pc was left hung up in things that did read, but weren't taken up,
and when things that didn't read are taken up, it will stir up dormant
BTs and clusters, and misowership and misidentification occurs. Add
to that cross-copying of BT pictures and you get a mess that can
recoil very heavily against the Pre-OT's body, dangerously so.
- 3 -
HCOB 16.9.78 II
Meter evaluation can be repaired by getting off when the pc or
Pre-OT was told _something_read_when_it_didn't,_ and vice versa. And
handling _"Evaluation?"_ E/Sim to F/N.
_Mis-dating_ and _partial_locating_ is similarly corrected by getting
off any wrong locations that were given or locations that were wrong
for other BTs or clusters.
Note that on Dating and Locating you can get a build up of mass
and pressure, even a protest ridge, due to the date for one BT or
cluster being the wrong date for some other BT or cluster. _The_mass_
_and_pressure_will_blow_on_indication_that_it_was_a_wrong_date_or_wrong_
_location_for_them._ A technique as powerful as Dating and Locating
which will blow clusters and cumulative clusters when done right, can
also mess them up badly when done wrong.
_MESSED UP INT RUNDOWNS AND INT REPAIRS_
Handle any BT or cluster with out-Int before doing any other
action. These are handled per HCOB 17 Sept 78 OUT-INT, WENT IN, WENT
ON.
If a Pre-OT has too much or recurring Int trouble, do the "End of
Endless Int Repair" process (by Recall only). As it is only recall,
it will run on and handle BTs or clusters.
_LIST ERRORS ON L & N AND WRONG ITEMS_
Mis-done L & N lists, especially over-listed lists and wrong
items mess up BTs and cluster. The right item for one BT is wrong
item for for another. When overlisted, several BTs and clusters can be
pulled in. The handling is as described in the Steps for Repairing
Past Auditing.
_STATE OF CLEAR_
_If_the_Pre-OT_has_charge_on_having_been_audited_ on engrams after
he/she went Clear, you can Date/Locate the point when the Pre-OT went
Clear. Then clean up _misownership_ by asking the Pre-OT _"Have_you_
_misowned_any_BT's_or_cluster's_pictures_as_your_own?_
As well as the Pre-OT having been audited on engrams after Clear,
you may also encounter _BTs_who_went_Clear_and_were_audited_on_engrams_
_subsequently.__Locate_and_indicate_their_BPC_of_having_been_audited_on_
_engrams_after_Clear,_any_misownership,_any_invalidation_of_the_State_
_of_Clear,_ and copies of this by other BTs and Clusters.
L. RON HUBBARD
FOUNDER
LRH:dm:kjm
Copyright (c) 1978
by L. Ron Hubbard
ALL RIGHTS RESERVED - 4 -
13
HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex
HCO BULLETIN OF 30 SEPTEMBER 1978
ISSUE III
_LIMITED_
_DISTRIBUTION_
Advanced Courses
Specialist
Checksheet
ACS Auditors
ACS C/Ses
_NED for OTs Series 13_
_C O N F I D E N T I A L_
_FESING OF FOLDERS_
_AND FULL FLOW TABLES_
An FES should contain the name of the auditor and name of the
C/S, per existing issues.
It now becomes imperative that the name of the auditor be clearly
noted on the FFT (Full Flow Table) as well as the FES. In making up
FFTs on any Dianetic or NED auditing clearly note the auditor's name
as well as the date and item run by that auditor. Existing FFTs do
not need to be re-done - just print in the name of the auditor, in
different coloured ink (to make it very visible) against the items run
by that auditor.
On new FFTs add a column on left side of sheet for auditor's
name.
----------------------
PC's name
_FULL FLOW TABLE_
| Auditor | Date | Item Run | F1 | F2 | F3 | F4 |
| (name) | | | | | | |
|---------------------------------------------------------------------
| | | | | | | |
| | | - 1 - | | | | |
HCOB 30.9.78 III
Some cases have had unreading items, wrong items, run on them;
sometimes the auditor changed the pc's item or even just decided what
to run on a pc. These are grave and can have serious consequences on a
case.
In order to fully handle such a situation it is imperative that
all the data above is available to a C/S or auditor.
L. RON HUBBARD
FOUNDER
LRH:dm:kjm
Copyright (c) 1978
by L. Ron Hubbard
ALL RIGHTS RESERVED [2]
HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex
HCO BULLETIN OF 17 SEPTEMBER 1978
ISSUE III
_LIMITED_
_DISTRIBUTION_
Advanced Courses
Specialist
Checksheet
ACS Auditors
ACS C/Ses
14
_NED for OTs Series 14_
_C O N F I D E N T I A L_
_OUT-INT, "WENT IN", "WENT ON"_
If a Pre-OT can put his attention on a BT and blow it off,
without even working too hard at it, BTs, with their attention must be
sort of blindly in-drawn.
"Went in" and "Went on" are two different characteristics of Int.
Some think they can't go in - because they think they can't go through
solids - so they "Went on", plastered on (to something).
Another way to blow them is to scan them back to when they went
in - and they blow out. Like a plus/minus reaction, "Went in" - blow
out.
A BT with Out-Int affects its ability to blow - not the Pre-OT's
ability to blow them off - the BT's ability to blow. You _scan_ them
_down_a_chain_of_"Went_ins"_to_the_first_"Went_in"_ and it will blow.
You could handle a very difficult one by _recalling_"times_ they
went in" - for very difficult ones. A fast way to blow them would be
to get them to scan back through "Went ins" - "When did you go in?" -
and they blow.
_"ON-NESS'_
There's also "Went on", _"Went_onto_something"_ , and a lot are
stuck on something. _You_scan_them_back_through_times_when_they_"Went_
on"._ They went onto something and couldn't get off.
Sometimes a BT will blow from inside the body and catch on the
- 1 -
HCOB 17.9.78 III
outside of the body, or within 2 - 3 feet of the body. You can get
too many restimulated on the surface of the body. You have to blow
off there surface ones.
Being stuck on the surface of something would have something to
do with the button _"Can't_go_in"_ for a BT, and that button produces
blows. BTs who "can't go in" to something, "Went on", and stuck.
"On-ness" is different from Out-Int. They are stuck _on_ , not in.
"On-ness" is handled in the same way as Out-Int but with "Went
on" or _"Got_on"_ . The "earlier than" phenomenon applies to "ON", as
one has to first get on something before he gets off. Trying to
persuade a stuck "Went on" BT or mass to get off, _can_run_into_the_
_same_phenomenon_as_Out-Int_and_he_won't_blow_ . Handle it the same way
as "Went in" but with the difference "Went on". One could in
theory find a thetan who was "stuck on" , handle that and _then_ find
that the _same_being_had_Out-Int._
_OUT-INT_
Sometimes BTs have Out-Int because they _can't_get_out_ or _couldn't_get_
_out_ .They are in the valence of something that can't be out, even
fatal to be out, e.g. "the inside of body" or an internal organ. They
consider these safe beingnesses, and it's safe to be in. So you ask
_"What_couldn't_get_out?"_ and they blow.
If you ask them to _point_ which way _is_ in, they can't. Getting
them to point which way _was_ in works, and produces blows. Use the
past tense, _"Which_way_was_in?"_ and they will blow.
_RECURRING INT TROUBLE_
If a Pre-OT on NED for OTs has recurring Int trouble or continues
to run into Out-Int, and you can't solve it easily, do the End of
Endless Int Repair Rundown (assessing and handling Int buttons by
_Recall_ , not R3RA). This Recall technique will run and solve any Int
troubles.
L. RON HUBBARD
FOUNDER
LRH:dm:kjm
Copyright (c) 1978
by L. Ron Hubbard
ALL RIGHTS RESERVED [2]
15
HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex
HCO BULLETIN OF 21 SEPTEMBER 1978
_LIMITED_
_DISTRIBUTION_
Advanced Courses
Specialist
Checksheet
ACS Auditors
ACS C/Ses
_NED for OTs Series 15_
_C O N F I D E N T I A L_
_THE "SOLIDITY" OF THE BODY_
BTs think they're pinned to the body, when they're pinned into
other BTs, they think they're interiorized into the body, when they're
pinned into BTs. How could a being get stuck to a body? There's some
kind of central core in the body that the being mistakes for the body.
The central core sticks to the body and the thetan sticks to it. Some
BTs think they are a body. There are clusters that think they're a
body and other BTs stick to the cluster and wind up thinking they're a
body. They would have to be stuck by a postulate: "I am a body", or
"I am a head", or "I am the brain", etc.
Someone on OT III can think he's complete on OT III because he
thinks the solidity he perceives as the body is the body. It is a
mistaken apparency of solidity of the body. This apparent solidity of
the body is composed of BTs and clusters and may be the same size and
shape as the body when first contacted. So someone on OT III
perceives this and assumes it's the body and thinks he's done on OT
III. This "solidity" he perceives as the body is composed of BTs and
clusters. The body becomes transparent to an OT to the degree he
clears this up. It is a "body" built of thetans - you have to learn
you're not looking at the body, but a false body composed of BTs and
clusters. A Pre-OT on "NED for OTs" will become aware of this during
the RD (it is not drawn to his attention by the auditor). It's not
the solidity of the body but the solidity of BTs and clusters formed
as a body.
The body acts as a magnifier of perceptions - it collects and
magnifies perceptions - some thetans think they can't perceive well
exterior, as the actual body and objects and walls look pretty flimsy
and transparent to an OT.
- 1 -
HCOB 21.9.78
The guy gets fooled - he thinks he's looking at this body and
he's not. He's looking at a solid mass of BTs and clusters. The
actual body looks transparent to an OT. Unless you get the guy's
perception up, he won't be able to perceive this and if he can't
perceive them, he won't be able to run them. The preliminary step of
"NED for OTs" is to get the Pre-OT's perception up enough so it can be
run. This false "body" composed of BTs and clusters is blown off
piece by piece on the RD.
_COMPOSITE MASSES_
A composite mass such as the false "body" composed of BTs and
clusters needs to be handled or blown off in pieces. You could make
the mistake of trying to blow it all at once instead of piecemeal.
You may also encounter "layered clusters", which is layers of clusters
on top of each other.
Use the "thetan hand" technique to separate ridges and masses,
(you can split ridges apart and separate masses and clusters by
passing a "thetan hand" between them). Then blow off the BTs and
clusters spearately. You can look up and down inside a mass, rather
than outside it and it starts to go.
There are so many BTs and clusters that the Pre-OT can wonder if
he's pulling in any that weren't there before or wonder if all space
is full of them-that isn't so, it only seems that way.
L. RON HUBBARD
FOUNDER
LRH:dm:kjm
Copyright (c) 1978
by L. Ron Hubbard
ALL RIGHTS RESERVED [2]
16
HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex
HCO BULLETIN OF 17 SEPTEMBER 1978
ISSUE II
_LIMITED_
_DISTRIBUTION_
Advanced Courses
Specialist
Checksheet
ACS Auditors
ACS C/Ses
_NED for OTs Series 16_
_C O N F I D E N T I A L_
_"EXTERIOR" VISION, BT PERCEPTION_
You can get a sort of exterior view as they blow - it's not an
actual exterior view, but an apparency of an exterior view. It's the
BT's visio feeding back to you while the BT is blowing. This visio
folds up when the BT has blown and your attention is off it. It's not
your own exterior view, it's their exterior view as they're blowing
and it fades as they blow and your attention comes off them.
It's to do with viewpoints and attention - if you get one of your
viewpoints (attention unit) in one (a BT or cluster), it will carry it
and you sort of see through their perception - it's how you see their
pictures and why you get some of their visio as they blow.
It has also been noted that when you do get a feedback visio from
a "BT" as it blows, that it is actually not a single BT, but two or
three and the feedback is coming from another or other BTs who have
not cognited that he is himself. In other words it is an uncleared BT
or cluster who is carrying this visio anchor point away.
Not all exterior perception comes from BTs though. The Pre-OT
can also get an exterior view which is his own actual exterior
perception. If the Pre-OT gets a stuck or fixed exterior view, it is
easily handled by having the Pre-OT look the other way, i.e. look in
the opposite direction, and the fixed direction of view, will unfix.
It is easy to differentiate between actual exterior perception of
Pre-OT and the phenoomena of the Exterior view of a BT during a blow,
by checking on the meter. If it is the view of a BT partially blown,
it will read as such. Partially blown BTs should be handled to
complete blow at which point the relayed BT visio will cease.
- 1 -
HCOB 17.9.78 II
There is a positive way to handle this if it hangs up. This is
for the Pre-OT to extend his attention out to the point to which the
BT or cluster has blown and ask it again what it is, give it an ack,
and then ask who it is. The untouched or uncleared BT or cluster that
is being carried away goes "poof" and the exterior visio ceases
instantly.
There's also perception by tactile contact, when the BT is
attached to the body.
L. RON HUBBARD
FOUNDER
LRH:dm:kjm
Copyright (c) 1978
by L. Ron Hubbard
ALL RIGHTS RESERVED [2]
17
HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex
HCO BULLETIN OF 23 SEPTEMBER 1978
ISSUE I
_LIMITED_
_DISTRIBUTION_
Advanced Courses
Specialist
Checksheet
ACS Auditors
ACS C/Ses
_NED for OTs Series 17_
_C O N F I D E N T I A L_
_PREDICTION FACTORS ON LENGTH AND PROGRESS_
_THROUGH THE RUNDOWN_
The first phenomenon you will encounter is the Pre-OT getting
apparent exterior perception, picking up the BT's exterior visio as
the BT blows.
The second prediction factor is that the amount of restim and
pressure remaining at session end becomes less from one session end to
another session end.
During the Rundown, the Pre-OT may wonder if he's pulling in BTs
and clusters to run, whether all space is filled with BTs, etc. This
isn't so, but may seem this way. The Pre-OT will get a realization
similar to the Straightwire EP that he/she won't get any worse". This
isn't the EP of the Rundown but shows progress is being made.
During the Rundown the Pre-OT will become aware that what has
been mistakenly assumed to be the body, is not the actual body, but
the solidity of BTs and clusters in shape of the body. The Pre-OT may
comment that his actual body or walls or objects look flimsy or
transparent and this is actual OT or exterior perception, and become
aware that he is perceiving BTs and clusters where the body looks or
feels solid. He is perceiving the difference between the false
"solidity of the body" and the actual body. As this false "body" is
audited out the clusters and masses remaining will swell to greater
size, with less mass and solidity.
Further through the Rundown, there are fewer BTs and clusters
remaining, and the mass expands and gets softer; it's not under so
- 1 -
HCOB 23.9.78 I
much pressure. There's less mass, and what is left is less dense.
And they blow easier and faster, with decreasing TA action.
Toward the end of the Rundown there are less and less BTs and
clusters to trap his attention into the body and his attention goes
out onto the physical environment. An OT's attention can get so
exteriorized, that it is very difficult to get his attention onto the
body; his attention is on the walls, room, building, area or planet.
The meter will read on "wall" or "room", etc., wherever his attention
is. You can get a similar phenomenon of the OT getting perception of
a wall or environment, via a blowing BT. Or the BTs can get
perception of physical environment via the OT's body. This phenomenon
is different, the OT is in direct communication and perception of the
physical environment. (Meter read will establish which it is.)
In earlier research I discovered what we call "leaning on a
wall". The OT "leans" against an object in PT and feels it, and it
can put a TA high; e.g. the being is leaning against a milk carton and
gets a waxy cardboard feeling. Realization of what is going on handles
it. But the phenomenon encountered toward the end of NED for OTs is
different. The OT's attention becomes so exteriorized that he goes
into direct comm with the environment and finds it hard to put his
attention on the body. About this time BTs and clusters do not read
well and the sensitivity has to be turned up high to get reads on BTs,
and you have a pretty constantly F/Ning needle. The auditor needs to
be sharp on TA and needle handling to keep the needle on the dial and
detect small reads on a very loose needle. F/Ning TA becomes more
frequent.
Don't try to push a session past a big win or marked case change;
several of these will occur during the Rundown. It's the EP for that
session - not for the Rundown.
It is possible for the Pre-OT later in the Rundown to blow a
distant BT stuck to somebody else. If the Pre-OT's attention is drawn
to something outside the session environment, check for a BT or
cluster in the area where his attention fixes, and have the Pre-OT
blow it off. This action is effective and permanent.
There are two changes going on during the Rundown:
(a) Pre-OT as a thetan is getting "bigger" and stronger;
(b) There are less BTs and clusters left.
The Pre-OT will get more and more relaxed, less mass, less
tension in the body. At first on the Rundown these masses are very
tense and hard, they feel like a tensed muscle, later the mass gets
less and lighter and the body more relaxed.
Toward the end of the Rundown the amount of mass left is so
slight that after a fairly short session it can become unprofitable to
audit as there's so little left, and what can be found blows so fast
- 2 -
HCOB 23.9.78 I
and easily.
These last few will blow by inspection and when there are none at
all in the Pre-OT or his environment, then you've reached the end of
the Rundown. The EP of the Rundown is when: the Pre-OT has a
transparent body and a clear area around it to some distance (barring
perception of other people's difficulties) and when he realizes he is
alive and very much himself.
L. RON HUBBARD
FOUNDER
LRH:dm:kjm
Copyright (c) 1978
by L. Ron Hubbard
ALL RIGHTS RESERVED [3]
18
HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex
HCO BULLETIN OF 23 SEPTEMBER 1978
ISSUE IV
_LIMITED_
_DISTRIBUTION_
Advanced Courses
Specialist
Checksheet
ACS Auditors
ACS C/Ses
_NED for OTs Series 18_
_C O N F I D E N T I A L_
_SESSION FACTORS_
The probable session planning should be short and frequent, based
on the general datum that early in the session the Pre-OT quite often
can blow BTs and clusters by inspection, while later in the session,
restimulation of other BTs and clusters, or possibly tiredness of the
Pre-OT, makes it difficult to blow them.
There is a session factor of cross-restimulation. If the
session goes on too long you can get some too restimulated to blow
easily. This can build up pressure and push the TA up. It relieves
on indication of cross-restimulation. BTs go into restim on other BTs'
pictures.
As the sessions are generally short, Tech Services and Tech Pages
will have to be very well organized and effective, so that no auditor
time is lost waiting for next pc, or folder. C/Ses and auditors will
have to ensure that Executives in and above Tech services know and
follow C/S Series 56 and BFO 46 VALUE OF SERVICES DELIVERED, HOW TO
RAISE and cram them on these issues whenever lines or terminals drop
out.
The sessions are generally short and frequent. You must not
continue a session past the session EP, usually an F/Ning TA, or a
win. You must not go on past the session EP or get into grinding due
to over-restimulation. Show this to your D of P if he tries to push
you.
There's also a factor of "incomplete blows". You can meter check
for this, but don't nag the Pe-OT on it, or you'll stir more up
- 1 -
HCOB 20.78 IV
because all the BTs remaining are sort of incomplete blows!
As you run "NED for OTs" there's a certain amount of pressure or
somatic remaining at session end. This becomes less from one session
end to another.
You can restimulate more in a session than you blow. This can be
checked for on the meter and handle those restimulated in the session
but not blown.
The session is usually started by 2WCing to F/N, or flying Ruds.
But the auditor must realize that charge in restim comes from
restimulated BTs and clusters. Shocks or stress in life restimulate
BTs and clusters who then copy the restimulation, and this
restimulation is a wrong incident for them as it is only a lock on
whatever they are stuck in. You handle any out-Rud BTs or
restimulated BTs at the beginning of session. If the TA is high, do
not try to 2WC it down, or go off Pgm onto a C/S 53, check for and
handle BTs or clusters in restimulation, or if there is evidence of
Out-Int, check for and handle any BT or cluster with Out-Int first.
Care must be taken at beginning of session not to ask for Earlier
Similars that don't exist, nor to restimulate more than is in restim.
_You're_only_trying_to_get_any_out-Ruds_or_restim_out_of_the_way_so_you_
_can_get_onto_the_Body_of_the_Session._
The Pre-OT probably shouldn't watch movies or TV during this
Rundown, as BTs tend to make pictures of the movie and hang up in
them, requiring handling at beginning of session. If too much restim
occurs due to watching movies or TV, get the Pre-OT to stop watching
them during the Rundown.
I had earlier found that Vitamin B1 would turn off dreams or
nightmares and that a lack of Vitamin B1 would make a pc more
susceptible to having dreams or nightmares. Apparently lack of B1
makes BTs stick to bone structure, more susceptible to restimulation,
and harder to blow. A session done on a Pre-OT who had a B1
deficiency ran very slowly with great difficulty blowing BTs and
clusters. The session was very "gluey". Taking Vitamin B1 resolved
this and BTs and clusters became easy to blow again. Pre-OTs on NED
for OTs should take 500 Milligrams of Vitamin B1 (Thiamine
Hydrochloride) daily, and if they experience dreams, nightmares or
difficulties blowing BTs and clusters, then the dosage should be
increased.
A right date or location for one BT or cluster can act as a
"wrong date" or "wrong location" for another BT or cluster, as it
isn't correct for their incident, and pressure and mass can build up
on this during a session where Date/Locating is done. Meter check for
"wrong date?", "wrong location?", Indication of this when it has
occurred will relieve the pressure and blow the TA down. BTs can also
build up a protest ridge on this.
Generally the TA will move in a pumping action, BDing as BTs and
clusters blow. The general session pattern is for the TA range to get
- 2 -
HCOB 20.78 IV
higher and higher and then pump on down to lower range, which is the
ideal point for ending session. A session continued past this
resulted in cross-restimulation and difficulty in blowing BTs.
The session must be well ended, as you are ending the session for
others (BTs and clusters) - not just for the Pre-OT. "END OF SESSION"
given Tone 40, may have to be repeated to ensure the session is in
fact ended. You will also sometimes encounter "last call" BTs and
clusters. Just as you are about to end the session, some BT or
cluster may pop up to be handled - this will often occur on "Say or
ask?" - let the Pre-OT handle any such "last call" BT or cluster. To
handle restimulation accumulated in the session, you can tell BTs to
"Come to present Time" before ending the session. Then _end_ the
session well and thoroughly.
A usual session EP is an F/Ning TA.
L. RON HUBBARD
FOUNDER
LRH:dm:kjm
Copyright (c) 1978
by L. Ron Hubbard
ALL RIGHTS RESERVED [3]