Warning: These materials are only to be read and used by students ready for the Level. To qualify you have to have attested Clear and done Advanced Level 2, Pre-OT Two. The student should also be a trained Solo-auditor.

Ruds, Remedies and Tips


Ruds Going Out on BTs
One thing a Solo-auditor has to learn quickly is that auditing BTs and Clusters is not that different from auditing a Preclear sitting in a chair across from him. All the basics of auditing apply, including the Auditors Code, auditing comm cycle and handling of rudiments. Not realizing that he may at some point feel that he doesn't want to audit anymore or needs a review session, etc. The truth of the matter is, that he has roughened up his "Preclears" and they don't like it and their out-rudiments are what makes him feel miserable.

Any student who has done a beginning Auditors course will be familiar with what is called Case Supervisor Series One, "Auditors Rights".

That issue lists at great length how to handle a variety of bad indicators and out rudiments in a Preclear.

Likewise, when the rudiments go out on BTs during the session the Solo-auditor should recognize the symptoms and handle accordingly. Advanced Level Three is of course audited silently and the Solo-auditor has to sharpen up his theta perceptions and develop a feel for the BTs and Clusters expression of emotion and originations.

Here is the list of things he should be able to recognize and how to handle them:

BT critical = W/H from Auditor.
BT antagonistic = BPC in session.
No TA = Problem.
BT sad = ARC Break
Soaring TA = Overrun or protest; 
(also more than one
BT being run in error or it's a Cluster.)
Auditor tired = No sleep or incomplete Incident Ones.
Auditor dope off = By-passed FN or not enough sleep.
Auditor no interest = Out ruds on BTs.

A new Solo-auditor who isn't sure what it is but runs into trouble with a BT is smart to end off the session quickly, write down the full observation and get it to the C/S. If more experienced the Solo-auditor can do a correction list such as the Green Green Form.

The Solo-auditor who knows what he is looking at per the above list of indicators can however go ahead and handle it right away:

BT critical = pull the W/H.

BT antagonistic = BPC = assess proper list (such as L1C) and handle.

No TA = (or case gain) = Problem = locate the problem and handle.

BT sad = ARC Break = locate and handle, itsa earlier itsa.

Soaring TA = O/R or Protest (Also more than one BT being run in error or it's a Cluster) = find which and handle.

Auditor tired = no sleep or incomplete Inc 1's = check which it is and handle.

Auditor dope off = lack of sleep or bypassed FN = check on sleep or rehab FN.

Auditor no interest = out ruds on BTs = put in ruds.

Another reason for high TA is not completing Incident Two and One on BTs and Clusters so they in fact are not taken to blow but are still there and thus add to the restimulated mass and charge on the case.

Note: Running more than the one Thetan intended comes from a too wide intention span, meaning more than one BT and Cluster will in error receive the  auditing command and seek to comply.

The above remedies for out rudiments can be applied at any time when encountered in session. They do not require a special C/S OK.

"Overrun" on Pre-OT III
A BT can be overrun. This fact sometimes causes a Solo-auditor
to believe OT III is overrun. If he asks "Is OT III overrun?" he may get a read and a blowdown. This is actually just one BT or Cluster that is overrun.

The only way you can get a read on "overrun on III" is to have accidentally run Incident One out and then later "run it out again" on the same Thetan or make a similar blunder.

Example: One flattens Incident One by several passes on a BT. This Body Thetan for some reason does not fly off. Then, not noticing this, one again finds the same Thetan and once more seeks to run Incident One. One then gets in answer to the question "overrun on III?" a lot of reads and other overrun phenomena.

The remedy is to find out who was overrun and get the charge off by cleaning up that action.

One then completes the steps of basic procedure or any other action lacking to make that BT be able to blow off successfully.

BTs can be overrun. To get a read on  "overrun on Level Three?" does not mean the Pre-OT was overrun on the Level but that a BT was overrun on some procedure and obviously failed to blow off successfully - or there wouldn't be a read.

Troubles Running Incident Two
There are three common reasons why a Pre-OT might have trouble
whilst running BTs on Incident Two:

1. It is the wrong area.
2. It is not the volcano of the BT being run.
3. It is not an Incident Two but another incident of a
different date.

'Wrong area' means the BT has been given Asia-Pacific or Atlantic as the area he was dumped and implanted at in error. It's a session error. (See Volcano List).

Check (1) and (2) if you are having any difficulty in running Incident Two and handle by locating the correct area or finding the volcano of the BT being run.

If it is not an Incident Two, simply check for the date and if different, run it using D/L Cluster Handling.

Running Incident Two - Running  The Overt Side
Any trouble a Pre-OT can get into on running Incident Two is handled and destimulated by:

1. Running Incident Two per the Platen: from "Capture to Pilot" or from "Explosion to Pilot", as the case may be. Don't try to run things later than 'Pilot'.
One reason for the BT free-wheeling and spinning is the "earlier beginning" of capture is kicking in.

2. When Incident Two is run per above without blow, find and run Incident One on that BT. An unrun Incident One will keep the Incident Two in place to some extent as Incident One is the Basic-basic Engram on the Chain. Once Incident One is found and run the whole charge on that BT will blow. 

Also, one can find and run the OVERT Side Engrams (of the overt motivator sequence) that makes the Motivator side key in so hard. Incident Two and One are after all Motivator incidents, things being done to self. Finding the Overt side of implanting another or others will undo the fact that it is keyed in so hard. This can usually be done in Solo.

In Solo (1) and (2) are the immediate approach to prevent the Pre-OT from "spinning". Running the Overt side is an additional tool available to use.

Theta Bops
A "theta bopping" Meter sometimes puzzles a Solo-auditor on Pre-OT III. It simply means a BT is trying to exteriorize and can't. The remedy is to complete the partially run Incident Two or Incident One or, in extreme cases, put the ruds in on the hung up BT. Int RD can be required but would be done in review.

Solo C/S' Toolbox

The remedies below are mainly data the Solo C/S can use. You don't suddenly start a new Major Action in session on a BT just because they could work. Any such Major Action is usually done in review auditing; or it requires a special C/S instruction when the Solo C/S is confident about the Solo-auditor's general auditing skills.

The Int Rundown (with recall only) can be applied on this Level but it would mainly be relevant if the Pre-OT has a general condition of Out Int. In extreme cases it can be run on a BT to help it blow successfully. The first indicator of out int may be the theta bop needle phenomena described above.

Rock Slams
"A R/S or Rock Slam is defined as a crazy irregular slashing motion of the needle. It can be as narrow as one inch or more than a full dial in width, but it's crazy! It slams back and forth. It is actually quite startling to see one". It can be caused by a faulty wire or can connection or PC wearing rings. This has to be ruled out first.
It is an indicator of an evil purpose in restimulation. The R/S may be that of a BT or Cluster and the full handling is then simply to audit the BT or Cluster to a blow. 

Suppressive Body Thetans
BTs can be very ill intended and in fact suppressive. They became SPs by going into valence of some of the bad characters in R6.
Any such SP Body Thetan will usually again be in 'his own valence' in Incident One.

A BT can be SP and psychotic. 

A suppressive Body Thetan sometimes isn't auditable. In case the Pre-OT runs into an impasse the C/S can usually sort this out by using Grades 0-4 and Power Processes. Which processes to use is a judgment call based on general C/S data.

C/S can order to run Grade Four, then Incident Two and Incident One on that BT. If this doesn't do it, the C/S can order Power Processes run on the SP BT. The greatest error the Solo-auditor can make is to get upset with one of these, cause the ruds to go out, and make the BT submerge so he can't be found. In such case, the suppress Button is put in repeatedly or he (the BT) is prep-checked.

Grade Four, Power Processes and Incident Two and Incident One can be run on such a BT. But these SP BTs are far less common than sometimes supposed.

The Power Process Six is especially designed to handle any SP, whether BT or Preclear. If the Solo-auditor can handle it the C/S can have him run Power Processes 4-6 on such a BT (without Grade 0-4 first) and this should 'crack the BTs case'. This would be done single flow.

Handling such a rare SP Body Thetan would usually be done in a review session, where the Pre-OT is being audited by a qualified Power Auditor and relaying the commands and answers to and from the BT.
The Pre-OT simply has to focus his attention narrowly on the BT being audited and the Meter will respond well and make the auditing possible.

Other types of resistive BTs can actually with benefit be audited on the Grades (meaning Flow One of the last major process of Grade 0-4 is run). The most important Grades are still Grade Four and Power (Grade Five). Grade 4 is Service Facsimiles, which are a major reason for making the BT so resistive; it is some fixed idea that makes it impossible to get the BT going. This subject is taken up and handled on Grade Four. The Power Grade (process 4-6) takes up the incident the BT is stuck in that makes him combative and suppressive.

Regardless how resistive a BT seems to be it is important to realize that no unusual tricks are needed but that the BT will respond to standard technology.

Application of any of this is today, as mentioned, a C/S only specialty and a last resort as there is a whole battery of other tools, such as rudiments, D/L Cluster Handling, correction lists, etc. The above is however part of a Solo C/S' toolbox of proven technology.

Low TA
The reason for low TA is unflat Pre-OT III phenomena.
If a person has had a low TA on lower Grades it usually means the Preclear is overwhelmed or Auditor has rough TRs (excluding simple false TA for physical reasons). But behind this will be Pre-OT III phenomena. The full and permanent handling is not accomplished before. On lower Grades it is overcome by giving the Preclear light approach auditing, such as Life Repair, patch up auditing with plenty of simple Itsa and Two-way comms. The key is to take it very easy as Auditor and C/S. 

That a Preclear's TA routinely goes below 2.0 is a sure indicator of unflat OT III. He's still got BTs and Clusters.

When a person cannot handle OT III he is too much at effect. He cannot project his intention. And so can't run OT III.

Levels OT I and OT II, particularly OT II, are designed to increase a Pre-OTs ability to project his intention to others. If he can't, the Pre-OT III will overwhelm him and you get low TA or "no BTs on III". But harsh, overbearing auditing or life incidents have to occur as well, apparently, to drive the TA down.

But any "case of low TA" Hubbard found during research was:

(1) Overwhelmed in life;
(2) Unable to project intention;
(3) Physically inactive;
(4) Loaded with BTs;
(5) Tended to go out of valence easily.

In all this (4) 'Loaded with BTs' was the important point.

Endless OT III and Low TA are alike - inability to project intention, PC at effect. This is remedied by lightly causing PC to come to cause, to be able to project his intention and thus flatten OT III.

Can't Find any BTs or Clusters to Run - Failed Solo III Auditors
If the Solo-auditor is failing on Level III or can't find any BTs or Clusters to run when beginning the Level it usually requires a longer handling by the C/S.

The C/S has to make sure of:

1. That the Solo-auditor has his procedure checked out thoroughly and through study and drilling is made fully competent as a Solo III Auditor.

2. That the Pre-OT was fully set up for the Level. This requires folder study (Folder Error Summary) and Repair programs. This is dicey as it should have been taken care of on Prepatory auditing before Pre-OT One. At this point the actions allowed in the so-called non-interference zone is limited prepared lists and Int RD. The Pre-OT has to be gotten through Three before a full Repair and Advance Program can be undertaken.

RE: 1. The Solo-auditor cannot audit - has not absorbed his training or at least isn't putting it into practice. Solo-auditor cannot put ruds in or do other elementary auditing actions.

The remedy is to get the Solo-auditor better trained. This may be a matter of cramming or it may be a matter of the Pre-OT redoing his basic Solo-auditors course. If the person then still has trouble on this Level, he would need a thorough retread of practical and session Solo-auditor skills or better, take a full Auditors course, Level 0-4.

The best approach to Level III is to be a well trained Auditor before beginning Solo. The more Auditor training and experience the better.

Any of these two points can result in the pathetic situation where the Pre-OT tries to declare "no BTs or Clusters on Level III" and tries to attest. Or finds a few BTs and decides to rabbit out (run away) by quick attempt to attest.

The remedy for all this is to:

(a) get ruds well in and use the correction lists appropriate to the Solo-level they have done, including an LDN,
(b) get the person more training as in 1 above, and
(c) get the person through the Level standardly, using Review as needed, to an OT III attest.

These actions take care of the majority of "difficult" cases on OT III.

Solo-auditors who "can't find any BTs and Clusters on III" and handled per above are routinely found to be loaded and now capable of running them.

There are literally hundreds of BTs and Clusters to handle on any case on Earth or they wouldn't be here.



Prometheus International, 2004. Plus fair use quotes from Ron Hubbard's published notes and works.