Русская версия

Site search:
ENGLISH DOCS FOR THIS DATE- Safe Auditing Table - B611026

CONTENTS SAFE AUDITING TABLE SAFE PROCESSES
HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex
HCO BULLETIN OF 26 OCTOBER 1961
Franchise

SAFE AUDITING TABLE

I have just isolated the reason why a pc sometimes gets a solidifying bank on Step 6 and at other times.

The reason is that no terminal, except as below, may be run that is not the pc’s goal’s terminal.

A central valence or terminal is built in to demand total attention from the pc. When attention is given another terminal, too much, in life or auditing, the bank reacts to prevent that attention.

This is why some pcs gain weight. A terminal not the goals terminal has been run too long or concentrated upon too hard.

Therefore I have composed a table of safe processes.

SAFE PROCESSES

  1. Security (Processing) Checking. As long as O/Ws (times when pc’s attention was fixed on terminals other than goals terminal) are pulled off by Meter properly per standard or composed Sec Checks. Sec Checking a single terminal is less safe than Sec Checking in general which is totally safe unless a question on which pc has withholds is left unflat.
  2. The word “you” as a terminal may be run so long as it does not eventually stick any flows.
  3. Areas of Prior Confusion (prior to a stuck point or problem) may be run and will free the stuck point that occurs later in time. The run should be done on the Prior Confusion by Sec Checking the period earlier than the stuck point or problem. The questions are by deed rather than by terminal.
  4. Concepts including Rising Scale Processing are perfectly safe as they include no terminals.
  5. ARC Straight Wire, ARC Break Straight Wire and Something you wouldn’t mind forgetting? are all completely safe as long as pc is cycled back up to present time at process period end.
  6. CCHs.
  7. Touch Assists and all Familiarization Processes.
  8. Havingness and Confront Processes (The 36 Commands).
  9. Rudiments Processes if briefly used.
  10. Routine 3, finding pc’s goal and terminal and pre-hav runs and other processes on the goal and terminal, if found and done by an expert. Otherwise process is dangerous as incorrect goal and terminal might be used. By expert is meant a course completion with honours at Saint Hill. The wrong goal and wrong terminal run in any fashion disturbs the bank without release. (No goal or terminal found on any student before that student came to Saint Hill has so far proved correct.)
  11. Sec Checking a goals terminal. Running O/W or repetitive commands on a goals terminal is perfectly safe.
  12. Running engrams on the goals terminal chain is perfectly safe if well done.

Other processes may on a good percentage of pcs produce a heavy bank reaction and not discharge but only worsen the bank. The bank generally fades down in from three to ten days, and responds well thereafter to the above.

L. RON HUBBARD LRH:imj.msp.rd