6305C25 SHSpec-269 Handling ARC Breaks [Some of the data in this tape is contained in HCOB 27May63 " ... Cause of ARC Breaks".] LRH has discovered the common denominator to all ARC breaks: by-passed charge. An ARC break is defined as "the PC's transfer of attention from the bank to the auditor and a dramatization of the bank directed at the auditor." Charge that has been restimulated in session may provide a background booster for a session upset. When you drag the PC's attention to the auditor, the charge that has been deliberately restimulated in the session doesn't get as-ised, and the PC ARC breaks. Thus, something that, outside the session, could not cause an ARC break, may and will cause an ARC break if it happens in session. The ARC break is not caused by a social faux pas. It is caused by the sudden shift of attention, the unleashing of charge that was held back by the fact that the PC's attention was on it. As long as the PC has his attention on the bank, he is cause over its charge. "The moment his attention is flicked off of it he is ... the effect of that charge ... and the PC then dramatizes [it]." Any tone level or know-to-mystery scale level that is higher than the chronic tone of the PC, being higher than the PC, is cause over the PC and is therefore dramatized. It should be noted that apathy is a high tone for a PC. The tone level contained in the incident is what the PC, unintentionally, dramatizes. He could dramatize anything, e.g. boredom, effort (e.g. breaking a chair), or a manic. And the auditor is a good target. The PC himself is helpless to restrain himself from dramatizing. He will be surprised at himself, amazed to react that way, etc. An ARC break comes about whenever charge is bypassed that then puts the PC at its effect point. The PC dramatizes the charge that has been bypassed. [This charge is unknown to him and can therefore affect him adversely.] The remedy is to locate and indicate the exact bypassed charge, at which point the ARC break ceases. That is the mechanics of it. You don't have to go into a "do" and run the ARC break and run all engrams connected with it, etc. No. You only have to indicate bypassed charge. The remedy is not continuous auditing. You know now how to turn off someone's anger by saying that someone missed his withholds. That often works, but when it doesn't, it is because you indicated the wrong bypassed charge. You could assess a number of possibilities, e.g. "missed GPM", "missed goal", "missed RI". He will stop being ARC broken when you get the right one. In session, only a few charges can be missed: goals, RI's. engrams, refutation of reality, rejection of affinity, more basic incident, failure to acknowledge. That pretty well covers it. These things occur in life also. "Rage is an automaticity... in such a delicate balance that almost anything can make it slip." A neurosis is actually hard to maintain. That explains the simple effectiveness of correctly locating and indicating bypassed charge. The psychiatrist's failure comes about from two sources: 1. Lack of technology. 2. An interest in insanity's being very hard to solve. ARC breaks are not hard to handle if you know the cause and handling of them. Don't back off or fear them. Just develop the skill to find and indicate the right BPC, or you will get loses in auditing and eventually give up. "Temporary or permanent conditions of misemotional stress are something that you have to face up to as an auditor, ... 0r just get out of the auditing chair. [So] I want you to get confidence that ... you can find the BPC, ... and then, by indicating it to the PC, realize the tool that is in your power!" That a PC ARC breaks is no guarantee that the PC is in poor case shape or difficult to get gains on. Just indicating the correct BPC turns off the ARC break. You may find that the charge was bypassed two sessions ago, or the ARC break doesn't get handled because you can't find what it was until somewhat later. Then, when you indicate it, the PC calms down. But "you shouldn't let an ARC break last more than two or three minutes," because ARC breaks multiply on a steep curve. Governments these days are run by riot, because they are so scared of ARC breaks. England's matter-of-fact handling of the "ban the bomb" movement is an exception to this rule, like an auditor who doesn't get thrown by or governed by ARC breaks. Governments have also been run by fear of assassination. This is just a dramatization of the Helatrobus implants. You, as an auditor, could be governed by ARC breaks if you can't handle them. "You are never governed by that which you can handle with ease." So learn to handle ARC breaks until ARC breaks become just another phenomenon, like a runny nose. "Your attitude on ... ARC breaks must never be one whereby you are driven by the ARC break, because you will be driven, then, into not getting the items clean, ... into taking the PC's orders, ... [which] are the direct result of dramatizations. The orders are the significance contained in what you just put him at the effect of:" the BPC. Don't, for instance as a registrar, get reasonable in the face of dramatization. Hunt and peck around for bypassed charge. The rage is an automaticity. Psychosis is very tenuous and easy to break. Number of ARC breaks is not correlated with the success of auditing. ARC breaks multiply as the square of time. The greater the facility with which you handle ARC breaks, the less you are governed by them. PC's who are continually ARC broken in session can be run on the three-way ARC break process. This process, however, is not for use every time the PC ARC breaks. For instance, for an auditor messed up with ARC breaky PCs, you could run the following: _ |what attitude has been refused?" | "In auditing, |what reality has been rejected?" | |what communication has not been acknowledged?" - This works better than mid-ruds. It is the successor to ARC break straightwire, which, in 1958, could go into engrams and even implants. It works, because what it does is directly to locate and indicate BPC. If you let the ARC broken PC control you, you will be taking his orders, because he is dramatizing not only the emotion but also the significance contained in the BPC. This is dangerous to the PC. So you should: 1. Learn to handle ARC breaks. 2. Be good enough as an auditor never to bypass charge. You can bypass charge by not finding any. You press on with the session in the teeth of a PC who is dramatizing apathy. Then the PC gives you a wrong goal and you take it, thereby bypassing more charge. "The harder you are driven [by ARC breaks] into doing a bad job, the more charge you bypass." It won't run well. Bypassed charge is always prior to the charge on what you are doing. So the ARC break is a blessing in disguise, since it tells you that there is more charge, which you have bypassed. It is more accurate than the meter, in this case. ARC breaks are cumulative in their effects. You do still have to peel enough charge from later incidents to get to the earlier ones, but the PC won't ARC break if you indicate to the PC, as an R-factor, what you are doing. If you tell the PC that there is a basic on the chain, he won't ARC break, even if you don't run the basic, because you have indicated the earlier charge. Indicating that there is earlier charge also makes it possible for the PC to run the later stuff. The PC can ARC break in the rudiments because he has out-ruds in the incident. That is just BPC, and you can indicate it. So when you chicken out of cleaning an Rl because the PC is protesty and ARC broken, you have set yourself up for more ARC breaks on subsequent items. Don't buy an RI that doesn't rocket read a full dial. If it won't, there is BPC to clean up. Bypass the charge? ... Keep it a secret? ... You will get an ARC break. Don't bypass charge!