FREEZONE BIBLE ASSOCIATION TECH POST LEVEL 0 COURSEPACK: Part 7 of 10 ******************************** I am the Tech Lion. Studying the Academy Levels gave me the ability to handle life. I would like others to have the same knowledge that I now have. Here is the Academy Level 0 Coursepack from 1988, in 10 parts. There was an earlier FZBA post of the Level 0 coursepack from 1974, but due to extensive CofS revision, little remains the same in both packs. The full table of contents is in Part 1 only. To see the proper formatting, use a fixed-pitch font such as Courier to view this file. Enjoy, -The Tech Lion ******************** STATEMENT OF PURPOSE Our purpose is to promote religious freedom and the Scientology Religion by spreading the Scientology Tech across the internet. The Cof$ abusively suppresses the practice and use of Scientology Tech by FreeZone Scientologists. It misuses the copyright laws as part of its suppression of religious freedom. They think that all freezoners are "squirrels" who should be stamped out as heretics. By their standards, all Christians, Moslems, Mormons, and even non-Hassidic Jews would be considered to be squirrels of the Jewish Religion. The writings of LRH form our Old Testament just as the writings of Judaism form the Old Testament of Christianity. We might not be good and obedient Scientologists according to the definitions of the Cof$ whom we are in protest against. But even though the Christians are not good and obedient Jews, the rules of religious freedom allow them to have their old testament regardless of any Jewish opinion. We ask for the same rights, namely to practice our religion as we see fit and to have access to our holy scriptures without fear of the Cof$ copyright terrorists. We ask for others to help in our fight. Even if you do not believe in Scientology or the Scientology Tech, we hope that you do believe in religious freedom and will choose to aid us for that reason. Thank You, The FZ Bible Association ************************ PART 7 (this file) 45. HCOB 15 July 1978RA Scientology Auditing C/S-1 46. HCOB 7 Aug. 1978 Havingness, Finding and Running the PC's Havingness Process 47. HCOB 6 Oct. 1960R Thirty-six New Presessions 48. HCOB 23 Aug. 1971 Auditor's Rights C/S Series 1 ****************************************************************** 45. HCOB 15 July 1978RA Scientology Auditing C/S-1 HUBBARD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead, Sussex HCO BULLETIN OF 15 JULY 1978RA RE-REVISED 10 MARCH 1984 Remimeo All C/Ses All Auditors Tech/Qual SCIENTOLOGY AUDITING C/S-1 A C/S-1 is a general C/S (Case Supervisor direction) which covers the actions necessary to orient the pc to the basic factors of auditing and thus prepares him to receive auditing. For this purpose, because of the differences in Dianetic and Scientology auditing terms and procedures, there exists this Scientology C/S-1 as well as a Dianetic C/S-1 (HCOB 9 July 76R, Rev. 4.9.78), The Scientology C/S-1 is done to give a pc new to Scientology or a previously audited pc, as needed, the necessary data and R- factor on Scientology basics, terminology and auditing procedure so that he understands and is able and willing to be audited successfully. Note: When the Case Supervisor orders a C/S-1 for a pc who has been trained or audited previously, the pc may protest that he knows the terms and procedure. Should this occur, the auditor must acknowledge with excellent TRs. Without invalidation or evaluation, he can let the pc know that this C/S is intended to make auditing more effective for him and to ensure that anything he might have missed is picked up and cleared. If the auditor's TRs are good, if he gives an honest R-factor and if he does not clean cleans (attempt to handle something the pc has already grasped), no ARC break should ever occur. A C/S-1 standardly delivered to the pc who needs it will give tremendous wins. It is not necessary to reclear those sections of this Scn C/S-1 which the pc may have already covered in a recent and thorough Dianetics C/S-1, provided the auditor is certain of the pc's understanding of the terms. The auditor should be fully familiar with this issue as well as: HCOB 17 Oct. 64 III GETTING THE PC SESSIONABLE HCOB 5 Apr. 69 NEW PRECLEARS, THE WORKABILITY OF SCIENTOLOGY HCOB 16 June 70 C/S Series 6 WHAT THE C/S IS DOING He will need to take a very thorough look at what has to be covered with the pc in this C/S-1 and know his materials very well and have them ready in the C/S-1 session for reference and clearing any misunderstoods or questions the pc may have. The following will be needed in the auditing room: Technical Dictionary Admin Dictionary A good English dictionary A good dictionary in the pc's native language, and for a foreign language case a dual dictionary (English-to-foreign language and foreign language itself) Scn C/S-1 Definitions Sheet - Attachment No. 1 of this issue The Basic Scientology Picture Book The Fundamentals of Thought HCOB 14 Oct. 68RA, Rev. 19.6.80, THE AUDITOR'S CODE Demo Kit. The auditor makes full use of these as necessary. If further references are needed, ensure source materials are used. A. Clear with the pc each Scientology (or other) term, using the definitions on the attachment sheet and other references as needed. Ensure you fully handle any word or term that is obviously misunderstood or any word or term the pc is hesitant about or unsure of. (Note: When having the pc define a word using Method 5 Word Clearing, you don't ask "Do you know what this word means?" You ask "What is the definition of _____?") When the pc has defined a word or term, have him use it correctly in several sentences. Where it is applicable, have him give you examples, using his experiences where possible or those of relatives or friends, and/or have him demonstrate the item, using a demo kit. Cover by exact definition all terms used. B. Check for any questions (or misunderstoods) as you go along and ensure any such get handled so the pc winds up with a clear understanding of the word, item or procedure. Don't settle for glibness that does not show understanding, but on the other hand, don't overrun or put duress on the pc either. Ensure that each word cleared on the pc is taken to F/N. SCIENTOLOGY C/S-1 PROCEDURE: 1. Give pc the R-factor that you are going to do a Scientology Auditing C/S-1 to familiarize him with auditing procedure and any basic data that may require clarification. 2. Clear the word Scientology. 3. Clear the words a. auditing b. auditing session c. auditor d. Clear e. preclear. 4. Clear the words a. thetan b. mind c. body. Have pc use the demo kit as well as the references to ensure he gets the relationship between these. 5. Now clear the words a. picture b. mental image picture c. reactive mind and 1. engram 2. secondary 3. lock d. bank. Have the pc give you examples of how the reactive mind works on a stimulus-response basis, and have him demo it. 6. Clear with the pc a. the communication cycle Get the pc to give you examples he has observed. Have him demo the communication cycle. b. the auditing comm cycle Get the pc to explain the difference between a comm cycle and the auditing comm cycle. Have him demonstrate it. If it is necessary to clarify this further, you can demonstrate the steps of the auditing comm cycle to the pc using simple, nonrestimulative questions. Example: Ask "Have you eaten dinner?" (or breakfast or lunch). And when he replies and has been acknowledged, ask "What did you do when I asked that question?" Then have him ask you a similar type of question. Answer him and be sure he acknowledges you. Really establish your comm cycle with the pc. 7. Go over the TRs with the pc, demonstrating each with him, until he has a good idea of how they are used in auditing. 8. Clear the words a. charge b. mental mass. 9. Go over with the pc what the meter does (registers charge/mental mass). For demonstration, you can do a "pinch test" where you explain to the pc that to show him how the meter registers mental mass you will give him a pinch as part of the demonstration. Do so. Then get him to think of the pinch (while he is holding the cans), showing him the meter reaction and explaining how it registers mental mass. 10. a. Clear the words 1. key-in 2. key-out and have the pc demo and give you examples of each. b. Clear the word Release. Have the pc demo it. c. Clear the word: rehabilitate (rehab). Ensure the pc understands its use in auditing. Have the pc demo it. 11. a. Clear the word postulate. b. Have pc give you examples of a time or two when he postulated something and got it. 12. a. Clear the word cognition. b. Have the pc give you some examples of a cognition. 13. Clear floating needle. 14. a. Give the pc an R-factor on rudiments and when these would be used. b. Clear the word rudiment. c. Clear 1. affinity 2. reality 3. communication. Have pc give you examples of each. d. Clear the term ARC. Demonstrate to the pc how A, R and C equate to understanding. Have the pc give you examples of how A, R and C together equate to understanding. e. Clear ARC break. Have the pc demo it for you. f. Using an appropriate dictionary, clear the words curious, desired, enforced, inhibited, no, refused. g. Clear 1. problem 2. present time problem. Have the pc demo 1. a problem 2. a present time problem. h. Clear 1. overt 2. withhold 3. missed withhold. Have the pc demo 1. an overt 2. withhold 3. missed withhold. (Use definitions sheet or other references as needed.) 15. a. Using an appropriate dictionary, clear the words 1. similar 2. earlier. b. Then clear "earlier-similar." Give the pc examples of where it would be used. c. Have the pc give you an example of something "earlier-similar." 16. Briefly clear with the pc how the rudiments are flown and the procedure for each rudiment. 17. Clear with the pc what a repetitive process is. Ensure he understands why and how it is done. Have the pc demo it for you. 18. a. Clear the word flow. b. Demonstrate for the pc each of the flows 1, 2, 3, 0. c. Then have the pc demo and give you an example of each. 19. Clear the words a. assess b. assessment. 20. a. Explain to the pc that if at any time there is any difficulty in the auditing, you (or another auditor) will be using a prepared list to find and handle the exact difficulty. b. Ensure he understands that when such a list is being assessed he sits quietly holding the cans while the auditor calls the list and takes meter reads to locate the difficulty. 21. Go over the Auditor's Code, items 1, 2, 3, 4, 5, 6, 8, 9, 14, 17, 18, 19 and 22. Check for and clear up any questions or misunderstoods the pc may have on this. 22. a. Clear Examiner. b. Give the pc an R-factor on the Examiner and the fact that he will go to the Examiner immediately after each auditing session. Ensure he understands the Examiner says nothing to the preclear at that time, only recording what the pc says and noting down the tone arm position and state of the needle. Also, be sure the pc understands that the Examiner is the person he sees if he wishes to make any sort of statement regarding his case between sessions. c. Conditional: To familiarize the pc more fully with this step, if it is feasible, take the pc to the Examiner's space, introduce him to the Examiner, briefly orient him to the space and go over with him again the functions the Examiner performs. Then return to the auditing room. 23. Turn the folder in to the C/S. The C/S can also order any additional actions to the above. The Scientology Auditing C/S-1 can usually be completed in one session. If it takes more than one session, the first session should be ended off at the end of a step or completion of a word or demonstration -- never in the middle of an action. Make sure you do not leave your preclear with a question or a misunderstood or confusion. Know the preclear in front of you and get your product of an educated pc who can run Scientology processes easily and with gain. --------- CLEARING COMMANDS The Scientology Auditing C/S-1 does not preclude clearing the commands of each process or clearing a procedure in a session where the pc is begun on a new process or procedure. (Ref. HCOB 9 Aug. 78 II, CLEARING COMMANDS) This would include the first time the pc is given a two-way comm session, a listing and nulling session, etc. With any new action, the procedure would first be fully cleared on the pc by the auditor. CLEARING WORDS ON CORRECTION LISTS In addition to the C/S-1, to fully prepare the pc for his auditing up the Grade Chart, it is standard to clear the words on the various correction lists very early in auditing, before the need for them arises. (Otherwise, it is difficult to clear the words of a correction list over heavy bypassed charge.) Thus, when the need for correction lists does arise, the words have already been cleared and the correction list can be used without delay. (Ref. HCOB 9 Aug. 78 II, CLEARING COMMANDS, items 7 and 8) This would be done as ordered by the C/S. L. RON HUBBARD Founder LRH:dr.bk.iw.gm _ ATTACHMENT SCIENTOLOGY C/S-1 DEFINITIONS SHEET (The following definitions have been taken from the Dianetics and Scientology Technical Dictionary, the Basic Dictionary of Dianetics and Scientology, the glossary of the book Dianetics Today, from the book Dianetics: The Modern Science of Mental Health, Book One, Chapter Two, and from existing HCO Bulletins where indicated.) Use these in conjunction with The Basic Scientology Picture Book. If further references are needed when clearing these terms and concepts, ensure source materials are used. For any non- Scientology terms use a good nondinky dictionary. SCIENTOLOGY: An applied religious philosophy developed by L. Ron Hubbard dealing with the study of knowledge which through the application of its technology can bring about desirable changes in the conditions of life. (Taken from the Latin word scio, which means "knowing in the fullest sense of the word," and the Greek word logos, meaning "study of." The study of the human spirit in its relationship to the physical universe and its living forms. A religious practice applying to Man's spirit and his spiritual freedom. A body of knowledge which, when properly used, gives freedom and truth to the individual. AUDITING: Processing, the application of Scientology (or Dianetic) processes and procedures to someone by a trained auditor. The exact definition of auditing is the action of asking a preclear a question (which he can understand and answer), getting an answer to that question and acknowledging him for that answer. AUDITING SESSION: A period in which an auditor and preclear are in a quiet place where they will not be disturbed. The auditor gives the preclear certain and exact commands which the preclear can follow. AUDITOR: A person trained and qualified in applying Scientology and/or Dianetic processes and procedures to individuals for their betterment; called an auditor because auditor means "one who listens." An auditor is a minister of the Church of Scientology. CLEAR: A Clear is a being who no longer has his own reactive mind. (Ref. HCOB 14 Dec. 81, THE STATE OF CLEAR) A being who is unrepressed and self- determined. (Ref: Book: Dianetics: The Modern Science of Mental Health, Book One, Chapter Two) The power of auditing is such that the State of Clear is now achieved by many through the refined technology of New Era Dianetics (NED), delivered by all service organizations of the Church of Scientology. Any person who does not go Clear on NED has another chance to achieve it on the Clearing Course at an Advanced Organization of the Church of Scientology. PRECLEAR: From pre- Clear, a person not yet Clear; generally a person being audited, who is thus on the road to Clear; a person who, through Scientology and Dianetic processing, is finding out more about himself and life. Abbreviation: pc. THETAN: From THETA (life static), a word taken from the Greek symbol or letter: theta, traditional symbol for thought or spirit. The thetan is the individual himself-not the body or the mind. The thetan is the "I"; one doesn't have or own a thetan; one is a thetan. It is the person himself - not his body or his name, the physical universe, his mind, or anything else; that which is aware of being aware; the identity which is the individual. MIND: A communication and control system between the thetan and the physical universe. It is not the brain. The mind is the accumulated recordings of thoughts, conclusions, decisions, observations and perceptions of a thetan throughout his entire existence. The thetan can and does use the mind in handling life and the physical universe. BODY: The organized physical composition or substance of an animal or man whether living or dead. The body is the thetan's communication center. It is a physical object. It is not the being himself. PICTURE: An exact likeness of something; a copy or representation of a thing, not the thing itself. An image or mental image of something. MENTAL IMAGE PICTURE: Mental picture; a copy of one's perceptions of the physical universe sometime in the past. A facsimile or a mock-up. In Scientology we call a mental image picture a facsimile when it is an unknowingly created picture or "photograph" of the physical universe sometime in the past. We call a mental image picture a mock-up when it is created by the thetan or for the thetan and does not consist of a photograph of the physical universe. Facsimiles, made up of mental energy, are the pictures contained in the reactive mind. REACTIVE MIND: Reactive bank. The portion of the mind which works on a stimulus- response basis (given a certain stimulus it will automatically give a certain response) which is not under a person's volitional control and which exerts force and power over a person's awareness, purposes, thoughts, body and actions. It consists of locks, secondaries, engrams and chains of them and is the single source of human aberrations and psychosomatic ills. ENGRAM: A mental image picture which is a recording of a time of physical pain and unconsciousness. It must by definition have impact or injury as part of its content. SECONDARY: A mental image picture of a moment of severe and shocking loss or threat of loss which contains misemotion such as anger, fear, grief, apathy or "deathfulness." It is a mental image recording of a time of severe mental stress. It may contain unconsciousness. Called a secondary because it itself depends upon an earlier engram with similar data but real pain. LOCK: A mental image picture of nonpainful but disturbing experiences the person has experienced. A lock depends for its force on secondaries and engrams. It is an analytical moment in which the perceptics of the engram are approximated, thus restimulating the engram or bringing it into action, the present time perceptics being erroneously interpreted by the reactive mind to mean that the same condition which produced physical pain once before is now again at hand. The reactive mind never stops operating. Pictures of the environment, of a very low order, are taken by this mind even in some states of unconsciousness. The reactive mind comprises an unknowing, unwanted series of aberrated computations which bring about an effect upon the individual and those around him. It is an obsessive strata of unknown, unseen, uninspected data which are forcing solutions, unknown and unsuspected, on the individual -which tells you why it remained hidden from Man for so many thousands of years. BANK: A colloquial name for the reactive mind. The mental image picture collection of the pc. It comes from computer technology where all data is in a "bank." COMMUNICATION CYCLE: A completed communication, including origination of the communication, receipt of the communication, and answer or acknowledgment of the communication. A communication cycle consists of just cause, distance, effect, with intention, attention, duplication and understanding. AUDITING COMM CYCLE: (HCOB 30 Apr. 71) This is the auditing comm cycle that is always in use: 1. Is the pc ready to receive the command? (appearance, presence) 2. Auditor gives command /question to pc (cause, distance, effect). 3. Pc looks to bank for answer. 4. Pc receives answer from bank. 5. Pc gives answer to auditor (cause, distance, effect). 6. Auditor acknowledges pc. 7. Auditor sees that pc received acknowledgment (attention). 8. New cycle beginning with (1). CHARGE: The stored quantities of energy in the time track; stored energy or stored or recreatable potentials of energy. The electrical impulse on the case that activates the meter. Harmful energy or force accumulated and generated in the reactive mind, resulting from the conflicts and unpleasant experiences that a person has had. MENTAL MASS: Mental mass is the mass contained in the mental image pictures (facsimiles) in the reactive mind. It has weight; very tiny, but it has weight, and it actually has size and shape and so forth. Its proportionate weight would be terribly slight compared to the real object which the person is making a picture of. KEY-IN: Verb: The action of recording a lock on a secondary or engram. Noun: The first time an engram is restimulated is called a key- in. A key-in is merely a special kind of lock, the first lock on a particular engram. A moment when the environment around the awake but fatigued or distressed individual is itself similar to the dormant engram. At that moment the engram becomes active. It is keyed-in and can thereafter be dramatized. KEY-OUT: Verb: An action of the engram or secondary dropping away without being erased. Noun: The person without knowing what the earlier instance was has had the lock vanish. That's a key-out. Adjective: Released from the stimulus-response mechanisms of the reactive mind. Release or separation from one's reactive mind or some portion of it. RELEASE: Noun: One who knows he or she has had worthwhile gains from Scientology processing and who knows he or she will not now get worse. A person who has been able to back out of his bank. The bank is still there but the person isn't sunk into it with all its somatics and depressions. A series of gradual key-outs. At any given one of those key-outs the individual detaches from the remainder of his reactive bank. REHABILITATE (Rehab): To restore to a former capacity or condition. In auditing, this means to do the series of actions in session which result in regaining a state of Release for the pc. POSTULATE: A conclusion, decision or resolution made by the individual himself-, to conclude, decide or resolve a problem or to set a pattern for the future or to nullify a pattern of the past. We mean, by postulate, a self-created truth. A postulate is, of course, that thing which is directed desire or order or inhibition or enforcement on the part of the individual in the form of an idea. Postulate means to cause a thinkingness or consideration. COGNITION: A pc origination indicating he has "come to realize." It's a "What do you know? I..." statement. A new realization of life. It results in a higher degree of awareness and consequently a greater ability to succeed with one's endeavors in life. FLOATING NEEDLE: A floating needle is a rhythmic sweep of the dial at a slow, even pace of the needle. It is always accompanied by good indicators or very good indicators in the pc. (Ref. HCOB 10 Dec. 76RB, C/S Series 99RB, SCIENTOLOGY F/N AND TA POSITION; HCOB 21 July 78, WHAT IS A FLOATING NEEDLE?) RUDIMENTS: First principles, steps, stages or conditions. The basic actions done at the beginning of a session to set up the pc for the major session action; ARC breaks, PTPs, withholds. A rudiment is that which is used to get the pc in shape to be audited in that session. AFFINITY: Degree of liking or affection or lack of it. The feeling of love or liking for something or someone. Affinity is a tolerance of distance. A great affinity would be a tolerance of or liking of close proximity. A lack of affinity would be an intolerance of or dislike of close proximity. Affinity is one of the components of understanding; the other components being reality and communication. REALITY: Reality is an agreement as to what is. It is not what the individual thinks reality is; it is what the majority agrees it is. It is the solid objects, the real things of life. It is the agreement upon perceptions and data in the physical universe. Reality is what is. It is one of the components of understanding. COMMUNICATION: The interchange of ideas or objects between two people or terminals. More precisely the definition of communication is the consideration and action of impelling an impulse or particle from source point across a distance to receipt point, with the intention of bringing into being at the receipt point a duplication of that which emanated from the source point. The formula of communication is cause, distance, effect, with attention and duplication. Communication by definition does not need to be two-way. Communication is one of the component parts of understanding. ARC: A word formed from the initial letters of Affinity, Reality and Communication, which together equate to Understanding. It is pronounced by stating its letters, A-R-C. To Scientologists it has come to mean good feeling, love or friendliness. ARC BREAK: A sudden drop or cutting of one's affinity, reality or communication with someone or something. It is pronounced by its letters A-R-C break. Upsets with people or things come about because of a lessening or sundering of affinity, reality or communication or understanding. PROBLEM: A problem is a conflict arising from two opposing intentions. Anything which has opposing sides of equal force; it is postulate-counter-postulate, intention-counter-intention, terminal-counter-terminal, force-counter-force. It's one thing versus another thing. You've got two forces or two ideas which are interlocked of comparable magnitude and the thing stops right there. PRESENT TIME PROBLEM: A specific problem that exists in the physical universe now, on which a person has his attention fixed. Any set of circumstances that so engages the attention of the preclear that he feels he should be doing something about it instead of being audited. 0VERT: An overt act is an act of omission or commission which does the least good for the least number of dynamics or the most harm to the greatest number of dynamics. An aggressive or destructive act by the individual against one or more of the eight dynamics (self, family, group, mankind, animals or plants, mest, life or the infinite). That thing which you do which you aren't willing to have happen to you. WITHHOLD: An undisclosed harmful (contrasurvival) act. A withhold is something the pc did that he isn't talking about. Any withhold comes after an overt. MISSED WITHHOLD: An undisclosed contrasurvival act which has been restimulated by another but not disclosed. This is a withhold which another person nearly found out about, leaving the person with the withhold in a state of wondering whether his hidden deed is known or not. REPETITIVE PROCESS: A process that is run over and over with the same question of the pc. We don't expect the auditor to do anything but state the command (or ask the question) with no variation, acknowledge the pc's answer and handle the pc origins by understanding and acknowledging what the pc said. A process which permits the individual to examine his mind and environment and out of it select the unimportances and importances. FL0W: A progress of energy between two points. An impulse or direction of energy particles or thought or masses between terminals. The progress of particles or impulses or waves from Point A to Point B. The four flows used in processing are: F1, flow one, something happening to self F2, flow two, doing something to another F3, flow three, others doing things to others F0, flow zero, self doing something to self. ASSESS: To choose, from a list or statements, which item or thing has the longest read or blowdown. (In Dianetics it is choosing which item or statement has the longest read, blowdown or pc's interest. The longest read will also have the pc's interest.) ASSESSMENT: An action done from a prepared list. Assessment is done by the auditor between the pc's bank and the meter. The auditor looks at the meter while doing an assessment. He just notes which item has the longest fall or blowdown. Assessment isn't auditing; it is simply trying to locate something to audit. It is the whole action of obtaining a significant item from a pc. EXAMINER: Preclear Examiner. The person in a Scientology Church to whom preclears are sent immediately after any auditing session. The Examiner is assigned to the duties of noting the pc's statements, TA position and state of the needle and the pc's indicators, after session. He says nothing to the pc during this action; he simply records the necessary data and acknowledges the pc's statement if one is made. The Examiner is also the person the pc sees when he wishes to volunteer information or make any sort of statement about his case between sessions or if there is something he wants handled regarding his case. -------- _ ****************************************************************** 46. HCOB 7 Aug. 1978 Havingness, Finding and Running the PC's Havingness Process HUBBARD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead, Sussex HCO BULLETIN OF 7 AUGUST 1978 Remimeo HAVINGNESS FINDING AND RUNNING THE PC'S HAVINGNESS PROCESS Refs: HCOB 11 Jan. 62 SECURITY CHECKING TWENTY-TEN THEORY HCOB 29 Sept. 60 HAVINGNESS AND DUPLICATION HCOB 6 Oct. 60R THIRTY-SIX NEW PRESESSIONS Rev. 8.5.74 Book: E-Meter Essentials, Section G: Finding Havingness and Confront Processes NOTE: This issue is by no means a complete summary of the subject of havingness. There is a vast amount of material on havingness and the remedy of havingness in early publications and other HCOBs to be found in the Technical Volumes -- data the student will acquire as he continues to train up the levels and on the SHSBC. This issue is to give the beginning auditor a working knowledge of the subject of havingness. "HAVINGNESS: (1) That which permits the experience of mass and pressure. (2) The feeling that one owns or possesses. (3) Can be simply defined as ARC with the environment... (4) That activity which is run when needed and when it will not violently deflect the pc's attention. (6) The ability to duplicate that which one perceives, or to be willing to create a duplication of it... (8) Havingness is the concept of being able to reach or not being prevented from reaching..." (From the Technical Dictionary) The above are all valid, but the final definition of havingness can be simply stated as HAVINGNESS IS THE CONCEPT OF BEING ABLE TO REACH. NO HAVINGNESS IS THE CONCEPT OF NOT BEING ABLE TO REACH. Inherent in the ability to reach is the willingness and ability to duplicate. That which makes communication work in processes is the duplication part of the communication formula (Axiom 28 Amended). The position of a being on the Tone Scale is determined by his ability to reach (and thus his willingness and ability to duplicate, to communicate and experience). The lower the tone of the being, the less willing he is to reach, communicate with and experience his present time environment, and the less willing he is to reach and duplicate events of the past or permit them to happen again. This is remedied by Objective Havingness Processes. These are processes that deal with observing and touching objects in the auditing room or in the environment. They are "look around" or physical contact processes, used to remedy a low or "no havingness" condition. Thus, we find the pc's Havingness Process early on in auditing and use it to gain or remedy havingness before or after processes or at session end. FINDING AND RUNNING THE PC'S HAVINGNESS PROCESS The preclear's Havingness Process is tested for on the meter in an exact way. You test it on the needle with can squeezes from the pc. Use HCOB 6 Oct. 60R, Rev. 8.5.74, THIRTY-SIX NEW PRESESSIONS. 1. Set the sensitivity for 1/3-of-a-dial drop when the pc squeezes the cans. (See E-Meter Drill 5, The Book of E-Meter Drills.) 2. Run five to eight commands of the first Havingness Process on the above bulletin, with the pc on the meter. 3. Then have the pc squeeze the cans, noting the size of the needle read now. If this second can squeeze shows the needle looser (wider swing) than the first can squeeze did, you've got it. The Havingness Process you've tested is the Havingness Process for the preclear and may be used to remedy his havingness as necessary. 4. If the process tightens the needle during the test, don't use it. Don't bridge off. Just get off the process now and test the next process, or the next, continuing until you find a Havingness Process that does loosen the needle and gives a wider swing. One will be found among the list of Havingness Processes on HCOB 6 Oct. 60R. 5. The correct Havingness Process selected is then run ten to twelve commands at a time, usually just before ending off a session. A pc's Havingness Process can change as the pc changes with auditing. If at some point in the auditing the Havingness Process which has been being used falls to get the desired result, simply retest for a new Havingness Process, find one that works and use it. Even the right Havingness Process if run too much at one time (more than ten or twenty commands) will start running the bank. It doesn't harm the preclear but that isn't its use, as there are other processes that run the bank better. The purpose of a Havingness Process is to get the preclear stabilized in his environment. L. RON HUBBARD Founder LRH:nc.gm _ ****************************************************************** 47. HCOB 6 Oct. 1960R Thirty-six New Presessions HUBBARD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead, Sussex HCO BULLETIN OF 6 OCTOBER 1960R REVISED 8 MAY 1974 Remimeo THIRTY-SIX NEW PRESESSIONS The following material was developed for the 1st Saint Hill ACC. All cases of this ACC were well started toward Clear, 25 of them started for the first time. These new Presessions were employed. Two of the cases started with two-way comm on Failed Help only after which some of the Presessions following worked. NOTE: These Presessions are subject to revision after my further study. Their numbers will not be changed. I will probably change some of the processes and commands. They are given here exactly as developed and in the order of development, not workability. NOTE: The assistance of Dick and Jan Halpern, ACC Instructors, is gratefully acknowledged for the discussion and testing of these Presessions. NOTE: Presession I is to be found in HCO Bulletin of 25 Aug. 60 and is not actually part of this series, not being a Havingness- Confront Presession. PRESESSION II: Havingness: "Look around here and find something you could have." Confront: "What could you confront?" "What would you rather not confront?" PRESESSION III: Havingness: "Point out something in this room you could confront." "Point out something in this room you would rather not confront." Confront: "What unconfrontable thing could you present?" PRESESSION IV: Havingness: "What part of a beingness around here could you have?" Confront: "What beingness could others not confront?" PRESESSION V: Havingness: "Point out something in this room you could confront." "Point out something in this room you would rather not confront." Confront: "Point out a place where you are not being confronted." PRESESSION VI: Havingness: "Look around here and point out an effect you could prevent." Confront: "What would deter another?" "Where would you put it?" PRESESSION VII: Havingness: "Point out something." Confront: "Tell me something I am not doing to you." PRESESSION VIII: Havingness: "Where is the (room object)?" Confront: "Recall something really real to you." "Recall a time you liked something." "Recall a time you communicated with something." PRESESSION IX: Havingness: "Look around here and find an object you are not in." Confront: "Recall somebody who was real to you." "Recall somebody you really liked." "Recall somebody you could really communicate with." PRESESSION X: Havingness: "Look around here and find something you could have." Confront: "What beingness could you confront?" "What beingness would you rather not confront?" PRESESSION XI: Havingness: "Notice that (indicated object)." (No acknowledgment) "What aren't you putting into it?" Confront: "Tell me something you might not be confronting." PRESESSION XII: Havingness: "Look around here and find something you can agree with." Confront: "What is understandable?" "What is understanding?" PRESESSION XIII: Havingness: "Look around here and find something you could have." "Look around here and find something you could withhold." Confront: "What have you done?" "What have you withheld?" PRESESSION XIV: Havingness: "Notice that (room object). Get the idea of making it connect with you." Confront: (First ask: "Is there anything around here that is absolutely still?" If the answer is yes, continue. If no, use another presession.) "Look around here and find something you could stop" (to change of needle pattern or tone arm); then: "Look around here and find some thing you could start" (to change of needle pattern or tone arm); then, when neither command unsettles needle pattern or tone arm anymore, use 5 or 6 commands of "Look around here and find something you could change." Then return to "stop." PRESESSION XV: Havingness: "Look around here and find something you could withhold." Confront: "What would you rather not duplicate?" PRESESSION XVI: Havingness: "Point out something around here that is like something else." Confront: "What is something?" "What makes sense?" PRESESSION XVII: Havingness: "Where isn't that (indicated object)?" Confront: "What unkind thought have you withheld?" PRESESSION XVIII: Havingness: "What else is that (indicated object)?" Confront: "What would make everything the same?" PRESESSION XIX: Havingness: "What is the emotion of that (indicated object)?" Confront: "What intention failed?" PRESESSION XX: Havingness: "What is that (indicated object) not duplicating?" Confront: "What two thoughts aren't the same?" PRESESSION XXI: Havingness: "What scene could that (indicated object) be part of?" Confront: "What past beingness would best suit you?" "What past thing would best suit you?" PRESESSION XXII: Havingness: "Duplicate something." Confront: "What would be a betrayal?" PRESESSION XXIII: Havingness: "What is the condition of that (indicated object)?" Confront: "Describe a bad case." PRESESSION XXIV: Havingness: "What is the condition of that person?" Confront: "What is a bad object?" PRESESSION XXV: Havingness: "What aren't you putting into that body?" Confront: "What beingness would it be all right to confront?" PRESESSION XXVI: Havingness: "What bad activity is that (indicated object) not part of?" Confront: "How would you not duplicate a bad person?" "How would you not duplicate a bad thing?" PRESESSION XXVII: Havingness: "Where would that wall have to be located so you wouldn't have to restrain it?" Confront: "Describe an unpleasant environment." PRESESSION XXVIII: Havingness: a. "What around here would you permit to be duplicated?" or, b. "What is the safest thing in this room?" Confront: "Describe a removal." PRESESSION XXIX: Havingness: "Who would that (indicated object) be a good example to?" Confront: "What would that person be a good example to?" PRESESSION XXX: Havingness: "What would you have to do to that (indicated object) in order to have it?" Confront: "Spot a change in your life." PRESESSION XXXI: Havingness: (Auditor holds two small objects, one in each hand. Exposes them alternately to pc, with as little motion of arms and hands as possible.) "Look at this." (No acknowledgment) "What around here isn't this duplicating?" PRESESSION XXXII: Havingness: "How could you deter a ______?" "What have you not given a ______?" Confront: "What could you own?" "What have you denied owning?" (To clean up Scientology auditing or instruction, run on "auditor," "pc," "Instructors," "student," as indicated. "What would a ______ own?" "What would a ______ not own?") PRESESSION XXXIII: (This is used as a "post-session" to clear up an intensive at the end.) Havingness: Whatever Havingness runs best on pc, as Havingness command. Confront: "What have you done in this room?" "What have you withheld in this room?" (To clean up all auditing, use "an auditing room.") PRESESSION XXXIV: Havingness: Whatever pc runs best, as Havingness command. Confront: "Who have you overwhelmed?" "Who have you not overwhelmed?" PRESESSION XXXV: Havingness: "Notice that (indicated room object)." "How could you get it to help you?" Confront: "Whom have you failed to help?" (This will fish up a case who is out the bottom with ARC breaks. Corrects alter-isness.) PRESESSION XXXVI: Havingness: "Notice that (room object)." "How could you fall to help it?" Confront: "Think of a victim." Replace Havingness of Presession XXV with: Havingness: "Notice that body." "What aren't you putting into it?" 3 versions of Regimen 6 O/W commands: 1. "Get the idea of doing something to ______?"* "Get the idea of withholding something from ______?"* 2. "What have you done to ______?"* "What have you withheld from ______?"* 3. "Get the idea of having done something to ______?"* "Get the idea of having withheld something from ______?" *Assessed 6th dynamic terminal. (Number 3 runs regret.) L. RON HUBBARD Founder LRH:js.esc.ntm.jh.gm _ ****************************************************************** 48. HCOB 23 Aug. 1971 Auditor's Rights C/S Series 1 HUBBARD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead, Sussex HCO BULLETIN OF 23 AUGUST 1971 Remimeo All Auditors C/Ses SHSBC Academy Level IV Class VIIIs HGCs Class VIII Checksheet Class VI Checksheet Class III Checksheet C/S Course Checksheet HSST Interns C/S Series 1 AUDITOR'S RIGHTS AUDITOR RESPONSIBILITY FOR C/Ses An auditor who receives a Case Supervisor direction (C/S) of what to audit on a pc is NOT discharged of his responsibility as an auditor. THE AUDITOR HAS A SERIES OF RESPONSIBILITIES THAT ARE PART OF EVERY C/S HE GETS TO AUDIT. ACCEPTING THE PC No auditor is required to accept a specific pc just because the pc is assigned to him. If an auditor does not believe he can help that particular pc or if he dislikes auditing that particular pc, the auditor has a right to refuse to audit that pc. The auditor must state why. The Case Supervisor, Director of Processing or Director of Review or any of their seniors may not discipline the auditor for refusing to audit a particular pc. An auditor who refuses to audit his quota of hours or sessions is of course subject to action. Thus, refusing to audit a particular pc, so long as one is not refusing to audit other pcs, is not actionable. "I do not wish to audit this pc because ________. I am willing to audit other pcs," is the legal auditor statement in the matter. Some pcs get a bad name with some auditors, some don't appreciate the auditing, some conflict with a particular auditor's own personality. There are such instances. It does not mean certain pcs cannot be helped by others. It is also true that an auditor who dislikes a pc may not do a good job, so the rule also has a practical side to it. One auditor disliked young men and did a bad job on them. Another disliked old ladies and chopped them up in session. One pc had messed up several Scientologists and couldn't find anyone to audit him at all. We are not auditing people to make amends to the world. Thus, an auditor has a right to reject or accept the pcs he is given. ACCEPTING A C/S When the auditor gets a C/S to do on a case and if he thinks it Is not the correct thing to do, he has the right to reject the C/S for that pc and require another one he can agree to. The auditor does not have the right to start doing a C/S and change it during the session except as noted below. The auditor may NOT C/S in the auditing chair while auditing the pc. If he has NO Case Supervisor at all, the auditor still audits from a C/S. He writes the C/S before session and adheres to it in session. To do something else and not follow the C/S Is called "C/Sing in the chair" and is very poor form as it leads to Q and A. STALEDATED C/S A C/S that is a week or two old or a Repair (Progress) Program that is a month or two old is dynamite. This is called a "Staledated Program" or a "Staledated C/S," meaning it is too old to be valid. It should have been done sooner. The pc of last week when the C/S was written may have been well and happily employed but a week later may have headaches and a reprimand from the boss. It is dangerous to accept a Repair (Progress) Program if it is old. The auditor who sees his C/S is old and sees the pc has bad indicators is justified in demanding a fresh C/S giving his reasons why. A program written in January may be completely out of date in June. Who knows what may have happened in between. Use fresh C/Ses and fresh programs. Staledates only occur in poorly run backlogged divisions anyway. The real remedy is reorganize and hire more and better auditors. ENDING THE SESSION When the C/S he has is proving unworkable during the session, the auditor has a right to end the session and send the folder to the C/S. Ending the session is totally up to the auditor. If the auditor just doesn't complete an action that was producing TA and could be completed, it is of course a flunk. Such a case is just not running a basic engram the one more time through that would bring the TA down and give a proper end phenomena. This and similar actions would be an auditor error. The judgment here is whether or not the auditor's action is justified in ending the session. Even though he may have made an error, the auditor cannot be blamed for the ending off of the session as that is totally up to him. He can be given a flunk for the error. AUDITING OVER OUT-RUDS Auditing a pc on something else whose ruds are out is a MAJOR AUDITING ERROR. Even if the C/S omits "Fly a rud" or "Fly ruds," this does not justify the auditor from auditing the pc over out-ruds. The auditor can do one of two things: He can fly all ruds or he can return the folder and request ruds be flown. The DIANETIC AUDITOR is not excused from auditing over out-ruds and in an HGC must be specially cautioned not to do so but return the folder for a new C/S. Better still he should learn to fly ruds. INABILITY TO FLY RUDS If an auditor cannot get a rud to F/N, cannot get any rud to F/N, he is Justified in starting a Green Form. The auditor solution to no F/N on ruds is to do a GF whether the C/S said to or not. This is an expected action. It is understood the auditor would use Suppress and False in trying to fly ruds. SESSIONS FAR APART When a pc has not had a session for some time, or when a pc gets sessions days apart, RUDS MUST BE FLOWN. Otherwise, the pc will get audited over out-ruds. This can develop mental mass. Optimum session scheduling is a series of sessions or a whole program done in a block of sessions close together. This prevents the world from throwing the pc's ruds out between sessions. Giving sessions far apart barely keeps up with life. The auditing time is absorbed in patching life up. Rapid gain gets above life's annoyances and keeps the pc there. UNREADING ITEMS When an item the auditor has been told to run doesn't read on the meter, even when the auditor puts in Suppress and Invalidate on it, the auditor MUST NOT do anything with the item no matter what the C/S said. It is expected he will see if it reads and use Suppress and Invalidate on it. And if it still doesn't read, he will be expected NOT to run it. LISTS When an auditor whose C/S told him to list "Who or what _____" or any list question finds that the list question does not read, the auditor MUST NOT list it. When doing a list ordered by the C/S, it is assumed that the auditor will test it for read before listing and that he will NOT list an unreading question. (A read is an actual fall, not a tick or a stop.) LIST TROUBLE When an auditor has trouble doing a list and getting an item, it is expected he will use a prepared list like L4B to locate the trouble and handle it. As it is very hard on a pc to mess up a list, it is expected the auditor will handle the situation then and there with no further C/S directions. HIGH TA When the auditor sees the TA is high at session start yet the C/S says to "Fly a rud" or run a chain, the AUDITOR MUST NOT TRY TO FLY A RUD and he must not start on a chain. Trying to bring a TA down with ARC breaks or ruds is very hard on a pc as ARC breaks aren't the reason TAs go up. Seeing a high TA at start, the Dianetic auditor or Scientology auditor up to Class II does not start the session but sends the folder back to the C/S and for a higher class auditor to do. Seeing a high TA at start, the Scientology auditor (Class III or above) (a) checks for exteriorization in a recent session and if so the session is ended and the C/S is asked for an "Interiorization Rundown"; (b) if the pc has had an Interiorization Rundown, the auditor asks the C/S for permission to do a "C/S Series 53" or a Hi-Lo TA assessment or whatever the C/S indicates. The Int RD may have been (usually is) overrun and needs rehab or correction and it is usual to check it -- it is included in a "C/S 53" and a Hi-Lo TA. These actions are expected of the auditor even when not stated in the C/S. GOING ON HOPING When a case is running badly session to session, the LAST thing you do is go on hoping, either in auditing or C/Sing. "Let's try ______," "Then this," "Then this," is not going to solve the case. YOU GET DATA. You can get data by a White Form (Pc Assessment Form). You can get data from a GF fully assessed (Method 5). You can get data by 2-way comm on various subjects. You can have the D of P interview and get answers. You can even ask his mother. You look for case errors. You study the folder back to where the pc ran well and then come forward and you'll find the error every time. DO NOT JUST GO ON SESSION AFTER FAILED SESSION HOPING. That's pure idiocy. You get data! from prepared lists, from life, from the pc, from the folder. FIND THE BUG! Ah, good Lord, he is a Pinkerton agent sworn to secrecy! He does yoga exercises after every session. He was tried for murder when he was 16 and nobody has run the engram of it. Various auditors ran the same engram chain four times. An auditor ran Int RD twice. After Power, she had her baby and nobody ran the delivery. He doesn't like to talk but is a "Grade Zero"! A dozen dozen reasons can exist. An auditor does NOT let a C/S C/S hopefully. He refuses the C/Ses until a Folder Error Summary is done and the bug found. THINGS DONE TWICE By carelessness the same rundowns can be called for twice and done twice or even more. A Folder Summary inside the front cover must exist and must be kept up. Over it there must be a program on which the case is being audited. But just because it's covered, never neglect entering a session and what was run on the Folder Summary (FS). If Hold It Still is ordered, see if it was run before. Don't let major rundowns be done twice. DIANETIC ITEMS must NEVER be run twice. Dianetic lists must not be scattered through a folder. Bring them together and keep them together and being brought forward. COPY Don't copy Dianetic lists or worksheets from notes or items from lists. Keep all admin neat and in the original form. Copying makes errors possible. RUDS GOING OUT When the ruds go out during the session, the auditor recognizes the following: Pc Critical = W/H from auditor Pc Antagonistic = BPC in session No TA = Problem Tired = Failed Purpose or no sleep Sad = ARC Break Soaring TA = Overrun or Protest Dope Off = Bypassed F/N or not enough sleep No Interest = Out-ruds or no interest in the first place. An auditor who isn't sure what it is but runs into trouble with the pc (except on lists which he handles at once always) is smart to end off the session quickly, write down the full observation and get it to the C/S. The auditor who is an old hand and knows what he is looking at as per above scale (and the C/S the C/S would give) handles it promptly. Pc Critical = W/H = pull the W/H. Pc Antagonistic = BPC = assess proper list (such as L1C) and handle. No TA (or case gain) = Problem = locate the problem. Tired = no sleep or Failed Purpose = check which it is and handle. Sad = ARC Break = locate and handle, itsa earlier itsa. Soaring TA = Overrun or Protest = find which and handle. Such an O/R is usually by rehab. Dope Off = lack of sleep or bypassed F/N = check on sleep, or rehab F/N. No Interest = no interest in first place or out-ruds = check for interest or put in ruds. List goes wrong BPC = handle or do L4B or any L4 at once. Ruds won't fly some other error = assess GF and handle. The auditor has no business trying to do the C/S given when it collides with and isn't designed to handle any of the above. If the previous session disclosed such an error and this session C/S was designed to handle and doesn't, the auditor should end off and the next C/S should be "2-way comm for data." CASE NOT HANDLED When the auditor or the Examiner collides with a pc who is asserting his case has not been handled, there should not be a new set of actions based on little data but the auditor should end off and the C/S should order a "2-way comm on what hasn't been handled." The auditor should not at once take this up as part of any other C/S. In other words, an auditor doesn't change the C/S to a 2-way comm on something not called for by C/S. MAJOR ACTIONS An auditor should never begin a major action on a case that is not "set up" for it. As this can occur during a session, it is vital to understand the rule and follow it. Otherwise, a case can be bogged right down and will be hard to salvage as now a new action to repair has been added to an unrepaired action. Now, if the auditor starts a major action on a case not "set up," we get 2 things to repair where we only had 1, as the major action won't work either. Repair = patching up past auditing or recent life errors. This is done by prepared lists or completing the chain or correcting lists or even 2-way comm or Prepchecks on auditors, sessions, etc. Rudiments = setting the case up for the session action. This includes ARC breaks, PTPs, W/Hs, GF or Overrun listing or any prepared list (such as L1C, etc.). Set up = getting an F/N showing and VGIs before starting any major action. It means just that -- an F/N and VGIs before starting any major action. Such may require a repair action and rudiments as well. Major Action = any -- but any -- action designed to change a case or general considerations or handle continual illness or improve ability. This means a process or even a series of processes like 3 flows. It doesn't mean a grade. It is any process the case hasn't had. Grade = a series of processes culminating in an exact ability attained, examined and attested to by the pc. Program = any series of actions designed by a C/S to bring about definite results in a pc. A program usually includes several sessions. The vast bulk of auditing errors come about because C/Ses and auditors seek to use a major action to repair a case. It is a responsibility of an auditor to reject a C/S which seeks to use one or more major actions to repair a case that isn't running well. The auditor must understand this completely. He can be made to accept a wrong C/S for the pc and even more importantly can in his own session make the error and mess up the case. Example: Pc has not been running well (no real TA or had a grumpy Exam Report). Auditor sees C/S has ordered a major action, not a repair by prepared lists, ruds, etc. The auditor must reject the C/S as he will be made to fail in session by it. Example: Auditor gets a C/S, "(1) Fly a rud; (2) Assess LX3; (3) Run 3-way recall, 3-way secondaries, 3-way engrams on all / / X items." The auditor can't get a rud to fly. Does the LX3. In other words, he flunks by failing to SET UP the case. It could also go this way. Auditor can't get a rud to fly, does a GF, gets no F/N. He MUST NOT begin a major action but MUST end off right there. It is fatal to begin any new process on the case designed to change the case if the case is not F/N VGIs. The pc who starts processing for the first time and is surely not F/N VGIs must be set up by repair actions! Simple rudiments, life ruds, O/R list on life, even assessing prepared lists on life, these are repair actions. The pc will sooner or later begin to fly. Now at session start you put in a rud, get F/N VGIs and CAN start major actions. So the auditor has a responsibility not to be led up a garden path by a C/S which orders a major action on a pc who isn't repaired or by not being able in session to get an F/N VGIs by repair. The only exceptions are a Touch Assist or Life Ruds or the Dianetic Assist all on a temporarily sick pc. But that's repair, isn't it? PROGRAM VIOLATIONS When an auditor receives a C/S and sees that it violates the pc's program, he should reject it. The pc, let us say, is supposed to finish his Dianetic Triples but is suddenly being given a Group Engram Intensive. That violates the program and also the grade. If the pc is running badly, a repair should be ordered. If not, the program should be completed. Example: An effort is being made to get the pc to go backtrack. This is a program containing several major actions which probably consists of several sessions. Before this program is complete and before the pc has gone backtrack, the C/S orders "(1) Fly a rud, (2) 3 S&Ds." The auditor should recognize in 3 S&Ds a major action being run into the middle of a program and reject it. The correct action is of course the next backtrack process. GRADE VIOLATIONS A pc who is on a grade and hasn't attained it yet must not be given major actions not part of that grade. Example: Pc is on Grade I. C/S orders a list having to do with drinking. It is not a process on that grade. It could be done after Grade I is attained and before Grade II is begun. The C/S is incorrect and should not be accepted. ABILITY ATTAINED Now and then before the full major action is complete or before all the grade processes are run, the pc will attain the ability of the grade or the end phenomena of the action. This is particularly true of valence shifters or Interiorization Rundowns and can happen in grades. The auditor should recognize it and, with the F/N VGIs always present at such moments, end off. I know of one case who had a huge cog about Interiorization on Flow I Engrams and was pushed by both C/S and auditor to do Flows 2 and 3 who bogged so badly that it took a long while -- weeks -- to straighten the case out. The ability itself gets invalidated by pushing on. On the other hand, this should never be taken as an excuse. "I think he cogged to himself so we ended off." It must be a real "What do you know!" sort of out-loud cog with a big F/N and VVGIs and directly on the subject to end off a major action or a program or a grade before its actions are all audited. REVIEWING REVIEWS An auditor who gets a C/S or an order to repair a case that is running well should reject doing the action. I have seen a case ordered to repair who had Ext Full Perception Doing Great. The repair bogged the case. The case then got running well again but a second C/S ordered a new repair which of course bogged it. Then major actions were done. The case was again repaired and rehabbed and became okay. Three times the auditor should have said NO. FALSE REPORTS The vilest trick that can be played on a pc is for an auditor to falsify an auditing report. It may be thought to be "good public relations" (good PR) for the auditor with the C/S. Actually, it buries an error and puts the pc at risk. INTEGRITY is a hallmark of Dianetics and Scientology. Just because psychiatrists were dishonest is no reason for auditors to be. The results are there to be gotten. False reports like false attests recoil and badly on both the auditor and pc. OVERTS ON PCs When an auditor finds himself being nattery or critical of his pcs, he should get his withholds on pcs pulled and overts on them off. An auditor who goes sad is auditing pcs over his own ARC break. An auditor worried about his pc is working over a problem. Getting one's ruds in on pcs or C/Ses or the org can bring new zest to life. AUDITORS DON'T HAVE CASES In the chair no auditor has a case. If breath shows on a mirror held to his face, he can audit. Faint afterwards if you must but see that the pc gets to the Examiner with his F/N. Then get yourself handled. "WHAT HE DID WRONG" An auditor has a right to know what he did wrong, in the session that went wrong. Most often a sour session occurs only when the rules and data in this HCOB have been violated. But an auditor's TRs can go out or his listing and nulling is in error. After a session that went wrong, somebody else (not the auditor) should ask the pc what the auditor did. This sometimes spots a false auditing report. But it also sometimes is a false report by the pc. In any event, the auditor has a right to know. Then he can either correct his auditing or his know-how or he can advise the C/S the pc's report is untrue and better repair can be done on the pc. Savage action against an auditor is almost never called for. He was trying to help. Some people are hard to help. Not only does an auditor have the right to be told what was wrong but he must be given the exact HCOB, date and title, that he violated. Never take a verbal or written correction that is not in an HCOB or tape. Don't be party to a "hidden-data line" that doesn't exist. "You ruined the pc!" is not a valid statement. "You violated HCOB page ____" is the charge. No auditor may be disciplined for asking, "May I please have the tape or HCOB that was violated so I can read it or go to Cramming." If it isn't on a tape, a book or an HCOB, IT IS NOT TRUE and no auditor has to accept any criticism that is not based on the actual source data. "If it isn't written, it isn't true" is the best defense and the best way to improve your tech. ---------- These are the rights of the auditor with relation to a C/S. They are all technical rights based on sound principles. An auditor should know them and use them. If an auditor stands on these rights and gets beaten down, he should put all the facts before his nearest OTL or SO ship, as something would be very wrong somewhere. Auditing is a happy business -- when it is done right. L. RON HUBBARD Founder LRH:nt.jh.gm