======== Newsgroups: alt.religion.scientology Subject: Excuse the interruption ... the project continues. From: fun@xenu.scientology.com (David Gerard) Date: Sat, 19 Apr 1997 01:44:45 -0400 Part 3 of the stuff that RTC does NOT have the rights to. Enjoy! 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 : _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_ 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 : 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 - 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 That'll do. This is tedious crap. But it should get the desired reaction. -- http://www.suburbia.net/~fun/scn/