6402C25 SHSpec-6 What Auditing Is and What It Isn't LRH is the first survivor of the Battle of the Goals Plot. GPM's contain trickery and treachery. That is why no one, hitherto, has figured them out. Routine 3 didn't bite deep. Even running "oppose" didn't get much depth of bite. When you move it into "solve", you are beginning to get into dangerous areas. The tiger can bite your head off, but you can't get back at him. In R6, you are handling pure starving tigers. [For definition of R6, see p. 568, above.] Someone who could handle the oppose line easily will find enough aberration to make a powerful being unpowerful on the actual GPM line, quantitatively and qualitatively. The data of this lecture is valuable at all levels, but it is vital at Levels V and VI. It is so simple that you may think that there is nothing there to grasp. There is also confusion that blows off as one attempts to grasp it. The following is a pure piece of data that is incredibly difficult to TR-3 over to somebody. I am going to tell you: 1. The difference between auditing and assessing. 2. The difference between destimulating and erasing. 3. The difference between a PTP and an ARC break. 4. The targets of the auditor, which are: a) The PC. b) The bank. The auditor speaks either to the PC or to the bank. Auditing and the auditing cycle is addressed to the PC. Assessing is addressed to the bank. When the auditor talks to the PC, he often restimulates the bank; he has an influence on it, but he is still talking to the PC. Sometimes, during an assessment, the PC talks, and the auditor must acknowledge the origination, but these are separate actions. Auditing ... has only two products: destimulation and erasure., [See also pp. 486-487, above, for illustrations of destimulation and erasure (or "discharge").] You can get the PC out of it, or you can use the PC to wipe it out. The first is destimulation; the second is erasure. Destimulation gets the dogs that are barking at the PC to lie down and be quiet, and the PC to "come away from there". Auditing wipes out the dogs. Don't try to erase a PTP. That requires auditing, and PTP's prevent auditing. You destimulate PTP's, so that you can audit. You can get the PC to dust himself off (destimulation), or you can use the PC like an ink eraser (erasure). Some auditors specialize in trying to erase everything but never really get anything erased. It is OK to erase anything, as long as you complete your cycles of action. But the lower levels of auditing are practically all destimulation, not erasure. If an auditor can't destimulate a PC, he can never take up his own cycle of action, because the PC's restimulation takes charge. If the PC is elsewhere when you start the session and the cycle of action, you will never complete the cycle of action that you start. Destimulation is the only action that you can undertake to get a PC located and oriented. Don't try to audit, when all you should, or can, be doing is a destimulation. "Where did it happen? Where are you now?" is a destimulation. So is a prepcheck. Since an auditor can't complete his cycle of action unless he first destimulates the PC, destimulation is a very important skill. Running engrams, RI's, implant GPM's, etc., are all erasure. Even in destimulation, a tiny amount of erasure takes place. Just the PC's attention on the subject for a short time brings about erasure of a bit of it. The fact that a certain amount of the incident runs out during destimulation is shown by the fact that a PC experiences somatics during assists. We just hit the key-in [and erase that]. You can also destimulate something and then run out the incident. You could use effort processing, or run the engram. [Cf. running locks, secondaries, and engrams on subjects.] If you do this, though, complete the cycle of destimulating first, or you will leave some attention stuck on what you were destimulating, which, in the course of destimulating, you also restimulated somewhat. Not completing the destimulation cycle will make it that much harder to erase what you wanted to erase. You don't want the PC to come out of a destimulation attempt involving Mata Hari with his feet still all tangled up in silk stockings and old German documents. Complete cycles of actions, once started. If you start to erase something, erase it. Don't abandon it in order to go erasing something else. In Level VI, ideally, when you get a GPM, you erase it. This is complicated by the fact that that GPM is connected to the one above it and the one below it. But you could erase the middle. In practice, you consider the whole first series of goals one action and erase that, or half the first series, then the rest of it. [See p. 591, below, for an explanation of the goals series.] "The heart of certainty is arrival [at the end of a cycle of action]. The anatomy of uncertainty is a failure to complete a cycle of action." Rapid methods of destimulation are necessary. For instance, since-mid-ruds are needed to keep incipient BPC cleaned up and out of the road for the rest of the session. Life is restimulative. The purpose of ruds is destimulation. When the PC brings up something that is not in the auditor's main line of action, the auditor destimulates it and goes back to his main action. Case analysis is the tech that destimulates unwanted resurgences of case. Its purpose is handling PTP's as they arise. The activity of figuring out where GPM's fit, which has been called case analysis, we now call track analysis. Case analysis is a wide-level activity that can be used at any level. It is just finding what the PC is sitting in and getting his considerations. So while you are working on one GPM, if the PC gets his attention on another one, destimulate it with case analysis and go back to the first action. Otherwise. leaving him stuck in one mass, you let him go to another mass, and he will get over-restimulated. The rule applies to all levels. Make up your mind about what you are doing and complete your cycle of action. What is auditing? Auditing is "the action of asking a PC a question which he can understand and answer, getting an answer to that question, and acknowledging him for that answer." And then also, when the person originates, auditing involves understanding and handling that origination. That is all auditing is. It is TR-0, 1, 2, 3, and 4. When that occurs, TA action occurs and sanity occurs. Auditing is not assessing. Auditing may have the purpose of making someone feel better, but that has nothing to do with the definition of auditing or with what auditing is. The fact that someone feels better after an assessment does not mean that it was auditing. Therefore, from the above definition, you can't have self-auditing. "The technique is scientology, but auditing is this one ... action." If you understand the above to apply to all auditing, you will be fantastic as an auditor. You will find gold at the end of the rainbow. Nothing is very difficult about getting a result, if you just do what is in that definition. What makes the PC better is not the technique you use. It is simply the auditing comm cycle. "Auditing is a cycle of action.... And that two-terminal aspect, which is what this physical universe consists of, is what gives you tone arm action and is what makes a PC better. It's not a technique that makes a PC better, and it never will be.... Auditing is the "carrier wave' ... that handles anything and everything" for the PC. There is another activity an auditor can do, besides auditing: assessment. Auditing goes mainly to the PC; "assessment never goes to a PC." It goes to the bank. Therefore, by definition, it is not auditing. You can never assess a PC who thinks that he is being addressed. If you are trying to assess and the PC is trying to communicate with you, or if he thinks that you are trying to communicate with him, you will get messed up. When the auditing cycle is out, assessment cannot occur, in that the PC hasn't understood that it is not an auditing cycle that he is engaged in, and he can't just sit there and be assessed. He is nervous and restimulated, and his mind is darting all over the place. Even so, if you ask the question just where the mind is, it reads, through all his mental busywork. R2H is not really an assessment, even though you go down a prepared list, because you are really asking the PC those questions, and setting up 2WC about things that have occurred in the comm cycle. If a PC gets ARC broken during an assessment, it is because he has originated something, which you haven't acknowledged. He does not get ARC broken because you are assessing. Sometimes you sandwich auditing in with the assessment, but they are still two separate activities. The TA action that you get when you find an actual RI occurs when you have an auditing cycle going. It does not occur without the auditing cycle. An assessment, even of a correct RI, is not what gives TA action. It is the auditing comm cycle that gives TA. That is why, when you ask, "Is that your item?", you get TA action, in the form of a big blowdown. It is not because the PC contacts the item. He is already in the middle of it. So on solo auditing, the PC would get needle actions but not TA action. Assessment doesn't give you TA action. An ARC break assessment is given when the PC has an ARC break. This assessment list has other uses, but the ARC break assessment simply consists of assessing the list, getting the read, and indicating it to the PC. During an ARC break, you must not audit! "An ARC break is when the auditing comm cycle cannot take place.... It isn't anything else." The PC is upset and accusative. He won't talk to you. If you force a comm cycle at that time, you will only deepen the ARC break. At that point, you do nothing else but an ARC break assessment. When you have a real ARC break, you assess it, always. Know your tools so that you can do the right assessment, whether it be a session ARC break or an ARC break from the particular action that you are on. As long as you are addressing, with auditing, an area of disability in the PC, you will get TA.