No matching fragments found in this document.
FREEZONE BIBLE ASSOCIATION TECH VOLUME SUPER TECH VOL FOR 1963 - PART 7 ************************************************** The Freezone Tech Volumes are a superset of: 1. The Old Tech Volumes 2. The New Tech Volumes 3. Confidential Material 4. BTBs 5. PLs from the OEC volumes concerning Tech 6. Anything else appropriate that we can find They do not include a. All HCOPLs (see the OEC volumes for those) b. Tape Transcripts (which are being posted separately) Because there is so much material (for 1963, we have twice as much material as the old tech volumes), and because the old and new Tech Volumes do not align as to how the years are divided between the volumes, we are doing each year as a separate volume. The contents will be posted separately as part 0 and repeated in part 1 but will not be included in the remaining parts to keep the size down. ************************************************** 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 freezoner's are "squirrels" who should be stamped out as heritics. 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 Judiasm 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 ************************************************** 081 HCOB 26 MAY 63 ROUTINE 3, LINE PLOT (LINE PLOT FIRST SERIES CORRECTED) (NTV. p 171, previously considered confidential) HUBBARD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead, Sussex HCO BULLETIN OF 26 MAY AD 13 Central Orgs Missions ROUTINE 3 LINE PLOT Corrections to HCOB 12 May AD 13, ROUTINE 3, RI FORM, (GPM RI FORM CORRECTED) Line Plot, First Series of Helatrobus Implants (43 trillion). The RIs indicated on the corrected line plot form are the exact RIs that will be found. Do not accept any variation. The line plot is being released, corrected, in a form for auditing use as HCO Technical Form 26 May AD 13, available as a convenience to auditors from HCOs in lots of 30 complete line plot forms for $3.00 or �1 plus postage. Address the HCO Book Department. It is important to use a corrected line plot without variations or score outs as it causes the pc to suppress and reactivate suppressions in the incidents. The corrections are as follows: Items 11, 33, 39, 41, only capitalized word correct. Scrub words in small letters. Items 43, 45, 49, 53, remove center syllable "FUL" and"ED." Item 63, "unwantably." Item 101, "vitalable." Add pair 141A, 142B, "unwantable," "nix unwantable." Item 174, correct to "isn't ever." Item 176, correct to "who hates." Item 178, correct to "doesn't." Item 180, correct to "sees." Item 185, add "the." Item 187, importances (plural). Items 201, 203, 205, 209, 225. Scrub the parenthesis on each as incorrect. The capitalized items are correct on these. This line plot has now been verified in several GPMs and found unvarying in the first series. If you permit an incorrect RI the pc will eventually stack up on that RI GPM to GPM. All ARC breaks are caused by bypassed RIs, GPMs or incidents. An RI can be bypassed by being left undischarged, by being cleanly missed or by being incorrect. L. RON HUBBARD Founder ================== 082 HCOTF 26 MAY 63 LINE PLOT FIRST SERIES CORRECTED (Not in either set of tech vols. This appears to be authentic, simply being a composite of the 12 May 63 platen with the changes of 26 May 63 applied to it. Since this would no longer be considered confidential, it was probably omitted from NTV because it was a Tech Form rather than an HCOB) HUBBARD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead, Sussex HCO TECHNICAL FORM OF MAY 26, AD13 CenOCon Franchise Do in Blue Ink LINE PLOT FIRST SERIES CORRECTED The exact words of this Line Plot with No Variation are to be found in the first Series of GPM Implants. Block One 1. TOP OPPTERM______________ NIX __________________________ 3. ABSOLUTEABLY_____________ NIX ABSOLUTEABLY______________ 5. PERFECTABLY______________ NIX PERFECTABLY_______________ 7. SUPERIORABLY ____________ NIX SUPERIORABLY______________ 9. INCOMPARABLY ____________ NIX INCOMPARABLY _____________ 11. FASCINATABLY ___________ NIX FASCINATABLY _____________ 13. HIGHLY ACCEPTABLY ______ NIX HIGHLY ACCEPTABLY ________ 15. RECOMMENDABLY __________ NIX RECOMMENDABLY ____________ 17. ACCEPTABLY _____________ NIX ACCEPTABLY _______________ 19. ENGROSSABLY ____________ NIX ENGROSSABLY_______________ 21. VITALABLY ______________ NIX VITALABLY_________________ 23. EAGERABLY ______________ NIX EAGERABLY ________________ 25. ENTHUSIASTICABLY _______ NIX ENTHUSIASTICABLY _________ 27. ENJOYABLY ______________ NIX ENJOYABLY_________________ 29. PLEASURABLY ____________ NIX PLEASURABLY ______________ 31. AGREEABLY ______________ NIX AGREEABLY ________________ 33. DEDICATEABLY ___________ NIX DEDICATEABLY______________ 35. COMMENDABLY ____________ NIX COMMENDABLY _____________ 37. DESIREABLY______________ NIX DESIREABLY _______________ 39. WANTABLY________________ NIX WANTABLY _________________ 41. COVETABLY ______________ NIX COVETABLY_________________ 43. HOPEABLY________________ NIX HOPEABLY _________________ 45. DECIDEABLY______________ NIX DECIDEABLY _______________ 47. CREDITABLY______________ NIX CREDITABLY _______________ 49. DEMANDABLY _____________ NIX DEMANDABLY _______________ 51. BOREABLY________________ NIX BOREABLY__________________ 53. DEJECTEABLY ____________ NIX DEJECTEABLY_______________ 55. DEGRADEABLY ____________ NIX DEGRADEABLY ______________ 57. IDOITABLY ______________ NIX IDIOTABLY_________________ 59. LOSEABLY________________ NIX LOSEABLY _________________ 61. BADABLY_________________ NIX BADABLY __________________ 63. UNWANTABLY______________ NIX UNWANTABLY _______________ 65. PLAYABLY________________ NIX PLAYABLY _________________ 67. ABANDONABLY_____________ NIX ABANDONABLY_______________ 69. _____________________ING NIX ______________________ ING 71. ____________________ ERS NIX ______________________ ERS 73. ________________ INGNESS NIX __________________ INGNESS 75. ________________ ISHNESS NIX ___________________ISHNESS 77. _________________ ATIVES NIX ____________________ATIVES 79. __________________ IVITY NIX ____________________ IVITY Block Two 81. GOAL TO ________________ NIX TO _______________________ 83. ABSOLUTEABLY TO ________ NIX ABSOLUTEABLY TO___________ 85. PERFECTABLY TO__________ NIX PERFECTABLY TO ___________ 87. SUPERIORABLY TO ________ NIX SUPERIORABLY TO___________ 89. INCOMPARABLY TO ________ NIX INCOMPARABLY TO___________ 91. FASCINATABLY TO ________ NIX FASCINATABLY TO___________ 93. HIGHLY ACCEPTABLY TO____ NIX HIGHLY ACCEPTABLY TO______ 95. RECOMMENDABLY TO________ NIX RECOMMENDABLY TO _________ 97. ACCEPTABLY TO __________ NIX ACCEPTABLY TO_____________ 99. ENGROSSABLY TO__________ NIX ENGROSSABLY TO ___________ 101. VITALABLY TO___________ NIX VITALABLY TO _____________ 101. EAGERABLY TO __________ NIX EAGERABLY TO______________ 103. ENTHUSIASTICABLY TO____ NIX ENTHUSIASTICABLY TO_______ 107. ENJOYABLY TO___________ NIX ENJOYABLY TO______________ 109. PLEASURABLY TO_________ NIX PLEASURABLY TO____________ 111. AGREEABLY TO___________ NIX AGREEABLY TO______________ 113. DEDICATEABLY TO________ NIX DEDICATEABLY TO __________ 115. COMMENDABLY TO ________ NIX COMMENDABLY TO____________ 117. DESIREABLY TO__________ NIX DESIREABLY TO ____________ 119. WANTABLY TO____________ NIX WANTABLY TO ______________ 121. COVETABLY TO __________ NIX COVETABLY TO______________ 123. HOPEABLY TO____________ NIX HOPEABLY TO ______________ 125. DECIDEABLY TO__________ NIX DECIDEABLY TO ____________ 127. CREDITABLY TO__________ NIX CREDITABLY TO ____________ 129. DEMANDABLY TO__________ NIX DEMANDABLY TO_____________ 131. BOREABLY TO____________ NIX BOREABLY TO ______________ 133. DEJECTEABLY TO ________ NIX DEJECTEABLY TO____________ 135. DEGRADEABLY TO_________ NIX DEGRADEABLY TO____________ 137. IDOITABLY TO___________ NIX IDIOTABLY TO______________ 139. LOSEABLY TO____________ NIX LOSEABLY TO_______________ 141. BADABLY TO_____________ NIX BADABLY TO________________ 143. UNWANTABLY TO__________ NIX UNWANTABLY TO_____________ 145. PLAYABLY TO____________ NIX PLAYABLY TO_______________ 147. ABANDONABLY TO_________ NIX ABANDONABLY TO____________ 149. TO_________________ ING NIX TO ___________________ ING 151. TO_________________ ERS NIX TO ___________________ ERS 153. TO_____________ INGNESS NIX TO_________________INGNESS 153. TO______________ISHNESS NIX TO________________ ISHNESS 157. TO_______________ATIVES NIX TO_________________ ATIVES 159. TO________________IVITY NIX TO___________________IVITY Block Three 161. GOAL MINUS "TO"___IVITY NIX (Goal Minus "TO")____IVITY 163. ____________________ING NIX________________________ING 165. ___________________ ERS NIX________________________ERS 167. _______________ INGNESS NIX___________________ INGNESS 169. _______________ ISHNESS NIX___________________ ISHNESS 171. ________________ ATIVES NIX____________________ ATIVES 173. _________________ IVITY NIX_____________________ IVITY Block Five 175. THOSE WHO ARE_______ING SOMEONE WHO ISN'T EVER____ ING 177. ______ ING FORM OF GOAL SOMEONE WHO HATES ________ ING 179. ACTIVE______________ING SOMEONE WHO DOESN'T WANT__ ING 181. ANY NECESSITY FOR___ING SOMEONE WHO SEES NO NECESSITY FOR_____ING 183. ANY ACTIONS OF______ING NIX ANY ACTIONS OF_________ING 185. A BELIEF IN________ ING NIX A BELIEF IN___________ ING 187. THE PROPONENTS OF___ING NIX THE PROPONENTS OF_____ ING 189. THE FANTASTIC THE UNIMPORTANCES OF______ ING IMPORTANCES OF______ING 191. THE OBSESSIONS FOR__ING NIX THE OBSESSIONS FOR_____ING 193. THE INTERESTINGNESS NIX THE INTERESTINGNESS OF_______________ING OF _______________________ ING 195. THE CONCERNS OF ____ING NIX THE CONCERNS OF_______ ING 197. THE UPSETS ABOUT____ING NIX THE UPSETS ABOUT_______ING 199. THE DESPERATIONS OF_ING NIX THE DESPERATIONS OF____ING 201. THE FRENZIEDNESS OF_ING NIX THE FRENZIEDNESS OF____ING 203. THE HOPELESSNESS OF_ING NIX THE HOPELESSNESS OF____ING Block Six 205. THE EXHAUSTION OF___ING AN EXHAUSTED_______________ ER 207. THE STUPIDITY OF____ING A STUPIDIFIED_______________ER 209. THE EFFORTS OF______ING AN ENEFFORTIZED_____________ER 211. THE UNREWARDINGNESS AN UNREWARDED ______________ER OF _________________ING 213. THE COMPLICATIONS A COMPLICATED_______________ER OF__________________ING 215. THE DEMANDS OF _____ING A DEMANDING_________________ER 217. THE DETERMINATIONS A DETERMINED________________ER OF__________________ING 219. THE LIMITATIONS A_____ING___________________ER OF _________________ING 221. THE OPPONENTS OF____ING A __________________________ER 223. A HATRED OF_________ING __________________________ ING 225. STOPPED____________ ING SOMEBODY WITH THE GOAL _______ 227. ANY IMPOSSIBILITY SOMEBODY OR SOMETHING OF _________________ING WITH THE GOAL ________________ 229. THE NON EXISTENCE THE GOAL _____________________ OF__________________ING 231. BOTTOM OPPTERM TO ___________________________ Next goal + this goal or this goal + next goal. Sometimes Not or Nix has to be added "What goal would_________oppose?" (50 beyond last RS or RR) 1. (Top Oppterm of next goal) The next goal is always found by doing the goal opposite indicated. The bottom oppterm cannot be put in until you know the next goal. Put in any old oppterm that fires. Then when you have the next goal put in the bottom oppterm by asking "Who or What would the goal To ______ oppose?". Get the right bottom oppterm of the upper GPM. (Consists of the two goals joined together to make sense). Then list "Who or What would oppose _______(bottom oppterm just found)" and put To_______ on the list. Then re-list "Who or What would To_______(last RI of bank) oppose?" and put in Top Oppterm of next goal and you're away into the next GPM. LRH: dr Copyright � 1963 by L. Ron Hubbard ALL RIGHTS RESERVED ================== 083 HCOB 27 MAY 63 CAUSE OF ARC BREAKS (TV5 p. 281-6, NTV VII p. 172-8) HUBBARD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead, Sussex CenOCon Franchise HCO BULLETIN OF 27 MAY 1963 ALL AUDITING Star-rating HCO Bulletin for Academies and SHSBC CAUSE OF ARC BREAKS LUCKY IS THE PC WHOSE AUDITOR HAS UNDERSTOOD THIS HCO BULLETIN AND LUCKY IS THE AUDITOR, MAY HIS OWN CASE RUN WELL. I have just narrowed the reason for ARC Breaks in auditing actions down to only one source. RULE: ALL ARC BREAKS ARE CAUSED BY BY-PASSED CHARGE. RULE: TO TURN OFF AN ARC BREAK FIND AND INDICATE THE CORRECT BY-PASSED CHARGE. Charge can be By-Passed by: 1. Going later than basic on any chain without further search for basic. Example: Looking for the pc's first automobile accident, finding the fifth instead and trying to run the fifth accident as the first accident, which it isn't. The By-Passed Charge here is the first accident and all succeeding accidents up to the one selected by the auditor as the first one or the one to run. To a greater or lesser degree depending on the amount the earlier material was restimulated, the pc will then ARC Break (or feel low or in "low morale"). One can run a later incident on a chain briefly but only to unburden earlier incidents, and the pc must know this. 2. Unknowingly ignoring the possibility of a more basic or earlier incident of the same nature as that being run after the pc has been restimulated on it. Or bluntly refusing to admit the existence of or let the pc "at" an earlier incident. 3. Cleanly missing a GPM, as one between two goals run consecutively in the belief they are consecutive. 4. Missing an earlier GPM and settling down to the assertion there are no earlier ones. 5. Cleanly missing one or more RIs, not even calling them. 6. Failing to discharge an RI and going on past it. 7. Accidentally missing a whole block of RIs, as in resuming session and not noticing pc has skipped (commoner than you'd think). 8. Accepting a wrong goal, missing the right one similarly worded. 9. Accepting a wrong RI, not getting the plot RI to fire. 10. Misinterpreting or not understanding data given to you by the pc and/or acting on wrong data. 11. Misinforming the pc as to what has or has not fired and discharged. 12. Locating the wrong By-Passed Charge and saying it is the source of the ARC Break. 13. Failing to follow the cycle of communication in auditing. These and any other way charge can be restimulated and left prior to where the auditor is working can cause an ARC Break. Charge left after (later) (nearer pt) than where the auditor is working hardly ever causes an ARC Break. The burden of skilled auditing then, is to get RIs (and GPMs and incidents) discharged as close to basic (first incident) as possible. And always be prowling for something earlier. In contradiction of this is that any GPM fairly well discharged by RRs unburdens the case, ARC Break or no ARC Breaks. And any incident partially discharged lets one go earlier. The pc never knows why the ARC Break. He may think he does and disclaim about it. But the moment the actual reason is spotted (the real missed area) the ARC Break ceases. If you know you've missed a goal or RI, just saying so prevents any ARC Break. An ARC Breaky pc can always be told what has been missed and will almost always settle down at once. Example: Pc refuses to come to session. Auditor on telephone says there's a more basic incident or RI or GPM. Pc comes to session. The auditor who is most likely to develop ARC Breaks in the pc will have greater difficulty putting this HCO Bulletin into practice. Perhaps I can help this. Such an auditor Qs and As by action responses, not acknowledgments after understanding. Action can be on an automaticity in the session. So this HCO Bulletin may erroneously be interpreted to mean, "If the pc ARC Breaks DO something earlier." If this were true then the only thing left to run would be Basic Basic - without the pc being unburdened enough to have any reality on it. A drill (and many drills can be compiled on this) would be to have a lineal picture of a Time Track. The coach indicates a late incident on it with a pointer and says, "Pc ARC Break." The student must give a competent and informative statement that indicates the earlier charge without pointing (since you can't point inside the reactive bank of a pc with a pointer). Drawn Time Tracks showing a GPM, a series of engrams along free track, a series of GPMs, all plotted against time, would serve the purpose of the drill and give the student graphic ARC Break experience. The trick is TO FIND AND INDICATE the RIGHT By-Passed Charge to the pc and to handle it when possible but never fail to indicate it. It is not DO that heals the ARC Break but pointing toward the correct charge. RULE: FINDING AND INDICATING AN INCORRECT BY-PASSED CHARGE WILL NOT TURN OFF AN ARC BREAK. An automaticity (as covered later in this HCO Bulletin) is rendered discharged by indicating the area of charge only. This is an elementary example: Pc says, "I suppressed that." Auditor says, "On this incident has anything been suppressed?" Pc ARC Breaks. Auditor indicates Charge by saying, "I'm sorry. A moment ago I didn't acknowledge your suppression." ARC Break ceases. Why? Because the source of its charge that triggered an automaticity of above the pc's tone, was itself discharged by being indicated. Example: Auditor asks for a Joburg overt. Pc gives it. Auditor consults meter at once asking question again, which is protested giving a new read. Pc ARC Breaks. Auditor says, "I did not acknowledge the overt you gave me. I acknowledge it." ARC Break ceases. Example: Auditor asks for RI No. 173 on First Series Line Plot. Pc ARC Breaks, giving various reasons why, such as auditor's personality. Auditor asks meter, "Have I missed an Item on you?" Gets read. Says to pc, "I've missed an Item." ARC Break ceases. Whether the missing item is looked for or not is immaterial to this HCO Bulletin which concerns handling ARC Breaks. If an auditor always does in response to an ARC Break, such as instantly looking for specific earlier Items, that auditor has missed the point of this HCO Bulletin and will just pile up more ARC Breaks, not heal them. Don't be driven by ARC Breaks into unwise actions, as all you have to do is find and indicate the missing charge that was By-Passed. That is what takes care of an ARC Break, not taking the pc's orders. If the ARC Break does not cease, the wrong By-Passed Charge has been indicated. The sweetest running pc in the world can be turned into a tiger by an auditor who always Qs and As, never indicates charge and goes on with the session plan. Some Qs and As would be a source of laughter if not so deadly. Here is a Q and A artist at work (and an ARC Breaky pc will soon develop) (and this auditor will soon cease to audit because it's "so unpleasant"). Example: Auditor: "Have you ever shot anyone?" Pc: "Yes, I shot a dog." Auditor: "What about a dog?" Pc: "It was my mother's." Auditor: "What about your mother?" Pc: "I hated her." Auditor: "What about hating people?" Pc: "I think I'm aberrated." Auditor: "Have you worried about being aberrated?" Pc: @! ! *?!!. Why did the pc ARC Break? Because the charge has never been permitted to come off shooting a dog, his mother, hating people, and being aberrated and that's enough By-Passed Charge to blow a house apart. This pc will become, as this keeps up, unauditable by reason of charge missed in sessions and his resulting session dramatizations as overts. Find and indicate the actual charge By-Passed. Sometimes you can't miss it, it has just happened. Sometimes you need a simple meter question since what you are doing is obvious. Sometimes you need a dress parade assessment from a list. But however you get it, find out the exact By-Passed Charge and then INDICATE IT TO THE PC. The violence of an ARC Break makes it seem incredible that a simple statement will vanquish it, but it will. You don't have to run another earlier engram to cure an ARC Break. You merely have to say it is there - and if it is the By-Passed Charge, that ARC Break will vanish. Example: Pc: "I think there's an incident earlier that turned off my emotion." Auditor: "We'd better run this one again." Pc ARC Breaks. Auditor: (Consults meter) "Is there an earlier incident that turns off emotion? (Gets read) Say, what you just said is correct. Thank you. There is an earlier incident that turns off emotion. Thank you. Now let's run this one a few more times." Pc's ARC Break ends at once. Don't go around shivering in terror of ARC Breaks. That's like the modern systems of government which tear up their whole constitution and honor just because some hired demonstrators howl. Soon they won't be a government at all. They bend to every ARC Break. ARC Breaks are inevitable. They will happen. The crime is not: to have a pc ARC Break. The crime is: not to be able to handle one fast when it happens. You must be able to handle an ARC Break since they are inevitable. Which means you must know the mechanism of one as given here, how to find By-Passed Charge and how to smoothly indicate it. To leave a pc in an ARC Break more than two or three minutes, is just inept. And be well-drilled enough that your own responding rancor and surprise doesn't take charge. And you'll have pleasant auditing. ARC BREAK PROCESSES We had several ARC Break processes. These were repetitive processes. The most effective ARC Break process is locating and indicating the By-Passed Charge. That really cures ARC Breaks. A repetitive command ARC Break process based on this discovery I just made would possibly be "What communication was not received?" Expanding this we get a new ARC Straight Wire: "What attitude was not received?" "What reality was not perceived (seen)?" "What communication was not acknowledged?" This process IS NOT USED to handle SESSION ARC BREAKS but only to clean up auditing or the track. If the pc ARC Breaks don't use a process, find the missed charge. Indeed this process may be more valuable than at first believed, as one could put "In auditing ....... " on the front of each one and straighten up sessions. And perhaps you could even run an engram with it. (The last has not been tested. "In auditing" + the three questions was wonderful on test. 2 div TA in each 10 mins on a very high TA case.) "ARC Break Straight Wire" of 1958 laid open implants like a band saw, which is what attracted my attention to it again. Many routine prefixes such as "In an organization" or "On engrams" or "On past lives" could be used to clear up past attitudes and overts. We need some repetitive processes today. Cases too queasy to face the past, cases messed up by offbeat processes. Cases who have overts on Auditing or Scientology or orgs. Cases pinned by session overts. The BMRs run inside an engram tend to make it go mushy. And Class I Auditors are without an effective repetitive process on modern technology. This is it. A Repetitive Process, even though not looking for basic, implies that the process will be run until the charge is off and therefore creates no ARC Breaks unless left unflat. Therefore the process is safe if flattened. RUDIMENTS Nothing is more detested by some pcs than rudiments on a session or GPM or RI. Why? The same rule about ARC Breaks applies. The Charge has been By-Passed. How? Consider the session is later than the incident (naturally). Ask for the suppress in the session. You miss the suppress in the incident (earlier by far). Result: Pc ARC Breaks. That's all there is to ARC Breaks caused by Session BMRs or Mid Ruds. Example: "Scrambleable Eggs" won't RR. Auditor says, "On this Item has anything been suppressed?" Pc eventually gets anxious or ARC Breaks. Why? Suppress read. Yes, but where was the suppress? It was in the Incident containing the RI, the pc looked for it in the session and thereby missed the suppress charge in the incident of the RI which, being By-Passed Charge unseen by pc and auditor, caused the ARC Break. Remedy? Get the suppress in the incident, not the session. The RI RRs. Also, the more ruds you use, the more you restimulate when doing Routine 3, because the suppress in the incident is not basic on Suppress, and if you clean just one clean, even to test, bang, there goes the charge being missed on Suppress and bang, bang, ARC Break. Lightly, auditor, lightly. Q AND A ARC BREAKS Q and A causes ARC Breaks by BY-PASSING CHARGE. How? The pc says something. The auditor does not understand or Acknowledge. Therefore the pc's utterance becomes a By-Passed Charge generated by whatever he or she is trying to release. As the auditor ignores it and the pc re-asserts it, the original utterance's charge is built up and up. Finally the pc will start issuing orders in a frantic effort to get rid of the missed charge. This is the source of pc orders to the auditor. Understand and Acknowledge the pc. Take the pc's data. Don't pester the pc for more data when the pc is offering data. When the pc goes to where the auditor commands, don't say, "Are you there now?" as his going is thereby not acknowledged and the going built up charge. Always assume the pc obeyed until it's obvious the pc did not. ECHO METERING The pc says, "You missed a suppress. It's ....... " and the auditor reconsults the meter asking for a suppress. That leaves the pc's offering an undischarged charge. NEVER ASK THE METER AFTER A PC VOLUNTEERS A BUTTON. Example: You've declared suppress clean, pc gives you another suppress. Take it and don't ask suppress again. That's Echo Metering. If a pc puts his own ruds in, don't at once jump to the meter to put his ruds in. That makes all his offerings missed charge. Echo Metering is miserable auditing. MISSED WITHHOLDS Needless to say, this matter of By-Passed Charge is the explanation for the violence of missed withholds. The auditor is capable of finding out. So the pc's undisclosed overts react solely because the auditor doesn't ask for them. This doesn't wipe out all technology about missed withholds. It explains why they exist and how they operate. Indication is almost as good as disclosure. Have you ever had somebody calm down when you said, "You've got missed withholds"? Well it's crude but it has worked. Better is, "Some auditor failed to locate some charge on your case." or, "We must have missed your goal." But only a meter assessment and a statement of what has been found would operate short of actually pulling the missed withholds. APPARENT BAD MORALE There is one other factor on "Bad Morale" that should be remarked. We know so much we often discard what we know in Scientology. But way back in Book One and several times after, notably 8-80, we had a tone scale up which the pc climbed as he was processed. We meet up with this again running the Helatrobus Implants as a whole track fact. The pc rises in tone up to the lower levels of the tone scale. He or she comes up to degradation, up to apathy. And it often feels horrible and, unlike an ARC Break and the Sad Effect, is not cured except by more of the same processing. People complain of their emotionlessness. Well, they come up a long ways before they even reach emotion. Then suddenly they realize that they have come up to being able to feel bad. They even come up to feeling pain. And all that is a gain. They don't confuse this too much with ARC Breaks but they blame processing. And then one day they realize that they can feel apathy! And it's a win amongst wins. Before it was just wood. And this has an important bearing on ARC Breaks. Everything on the whole Know to Mystery Scale that still lies above the pc finds the pc at effect. These are all on Automatic. Therefore the pc in an ARC Break is in the grip of the reaction which was in the incident, now fully on automatic. The pc's anger in the incident is not even seen or felt by the pc. But the moment something slips the pc is in the grip of that emotion as an automaticity and becomes furious or apathetic or whatever toward the auditor. None is more amazed at himself or herself than the pc in the grip of the ARC Break emotion. The pc is a helpless rag, being shaken furiously by the emotions he or she felt in the incident. Therefore, never discipline or Q and A with an ARC Broken pc. Don't join hands with his bank to punish him. Just find the By-Passed Charge and the automaticity will shut off at once to everyone's relief. Running Routine 3 is only unpleasant and unhappy to the degree that the auditor fails to quickly spot and announce By-Passed Charge. If he fails to understand this and recognize this, his pcs will ARC Break as surely as a ball falls when dropped. If an auditor has ARC Breaky pcs only one thing is basically wrong - that auditor consistently misses charge or consistently fails to anticipate missed charge. One doesn't always have to run the earliest. But one had better not ignore the consequences of not pointing it out. One doesn't have to discharge every erg from an RI always but one had better not hide the fact from the pc. The adroit auditor is one who can spot earlier charge or anticipate ARC Breaks by seeing where charge is getting missed and taking it up with the pc. That auditor's pcs have only the discomfort of the gradually rising tone and not the mess of ARC Breaks. It is possible to run almost wholly without ARC Breaks and possible to stop them in seconds, all by following the rule: DON'T BY-PASS CHARGE UNKNOWN TO THE PC. L. RON HUBBARD LRH:jw.rd Copyright c 1963 by L. Ron Hubbard ALL RIGHTS RESERVED ================== 084 HCOPL 31 MAY 63 TRAINING OF CLEARS (OEC V4 p 341) HUBBARD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead, Sussex HCO POLICY LETTER OF 31 MAY 1963 CenOCon Franchise Field BPI Magazine TRAINING OF CLEARS (Cancels HCO Policy Letter of Sept 27, 1962, Clears Must Be Trained.) HCO Policy Letter of September 27, 1962 Clears Must Be Trained, is hereby cancelled. However, it should be borne in mind that education in Scientology is highly desirable for all who obtain Scientology processing. Continual efforts should be made to get all such to read Scientology books, to take PE courses, Extension courses and HPA courses, even if they do not intend to become professional auditors. L. RON HUBBARD LRH:dr.cden Copyright c 1963 by L. Ron Hubbard ALL RIGHTS RESERVED ================== 085 HCOB 1 JUN 63 ROUTINE 2, NEW PROCESSES (NTV p. 180-2, previously considered confidential) HUBBARD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead, Sussex HCO BULLETIN OF 1 JUNE 1963 MA Missions URGENT TO ALL AUDITORS ROUTINE 2 NEW PROCESSES The recent developments on the political front and various attacks upon Scientology and Scientologists caused a sudden catalyzing of research. My answer to these attacks was to: 1. Hold the front legally, employing competent attorneys and others to halt the actions taken against us. 2. Develop a counterattack by upgrading research lines. The first part of this program is succeeding. A push on us in Australia has already collapsed and we have won. In America the situation continues to improve for us and there is little doubt of our winning eventually. The second part of our program is being successful beyond the most happy estimates. About five or ten years' research work has been crowded into the last six months and although this has been hard work beyond belief, I have brought it off. The need was for an achievement of the state of Operating Thetan. While this state existed in theory, no time for an orderly development from aberree to Clear to OT was permitted by events. My task was to short-cut from aberree to OT and bypass all niceties of in-between states. No Scientologist needs to be told the significance of this in handling our affairs on Earth. This sudden speedup disrupted and probably upset many auditors. And I am sorry that this interrupted training programs and study. What had to be done was done. But it did disrupt all previous training and auditing expectancies. The first casualty was R2-12. The moment I was informed of the US and Australian attacks I adopted the above two-point program and even though I knew it would upset things, I had no choice but to concentrate on those two points. So I dropped Routine 2-12. And a short while thereafter was able to drop the ardures of goals finding. And working at top speed, laid open the impasses to OT and developed technology to overcome them. Well, all this, I can now state, has been successful. The gamble was upon the power of an OT. We won. An OT is so much more powerful than we have ever envisioned, that there is now no faintest doubt of the wisdom of the twopoint program above. The technology now exists for the creation of the state of OT. For many weeks now, the Saint Hill course technology has been steady and Saint Hill students have been successfully applying that technology and it, in its essential points, is in the hands of Central Orgs, and their staffs are being trained on it. We have moved fast. My estimate was that we had very few years from January 1963 before the roof fell in, not just on us, but on Earth. I thought I could bring this off in that period. In only five months it was being brought off. Short of this, I could not see how I could protect individual Scientologists from persecution and I was worried about them. The state of Clear was not enough. Therefore the technology of OT and a controlled environment were the only wholly satisfactory things I could do. So don't be shocked at the way R2-12 and other data was dropped. That progress would have been orderly but a sudden time limit was placed on us by the Washington raids. These were not more than a symptom of coming chaos, not just for us but for Earth. When a government has to imagine crimes to prosecute people for, that government is responding to times that are more chaotic than we believe. So here is the technical aspect of all this: 1. R2-12 is replaced by ARC Processing designated R2-T. Any auditor can use it. It consists of three questions variously cleared and used which sweep away the RI locks on a repetitive process basis. 2. Any auditor trained to handle R2-12 is benefited by being now easily trainable on R3-N which uses an even simpler approach. 3. The state of Clear is relegated to courtesy use without test, requiring only that a GPM has been run. First Goal Clear means one GPM run, Second Goal Clear means two GPMs run, etc. We will make no attempt to stabilize Clears but press them on to OT. 4. All concentration in auditing should be toward the state of OT (Free Thetan, as they were once known). 5. All Scientologists should cooperate in making OTs and in programs calculated to prevent the environment from degenerating into chaos. ______________ It takes about 500 hours to push an average case to OT with present technology, clearing GPMs and the time track. We have very little time, not just to make OTs, but to get things under control. So the time factors are very closely figured indeed. And there's no time to be lost. If you enroll at Saint Hill you will make it faster. ______________ If the program seems at all unreal, then recall, the life we're living here on Earth is a little unreal too. R2-T The basic commands of R2-T, are these: 1. "What attitude has been refused?" 2. "What reality has been rejected?" 3. "What communication has not been acknowledged?" Each process is given a cyclic ending (pc in PT again). Run the TA action out of each command in turn, then out of each one in turn again, etc. (Reduce to .25 div of TA motion in 10 minutes of auditing.) There are various ways of clearing these commands and various ways of using them which will be covered in later bulletins. These processes are powerful enough to open up any time track if properly used. They do not make an OT. They prepare the way to make one and they undo past auditing when prefixed with "In auditing, ." They destimulate whatever has been restimulated. L. RON HUBBARD Founder ================== 086 HCOB 4 JUN 63 ROUTINE 3, HANDLING GPMS (NTV p. 183-6, previously considered confidential) HUBBARD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead, Sussex HCO BULLETIN OF 4 JUNE AD13 Central Orgs Missions ROUTINE 3 HANDLING GPMS The GPM (of the Helatrobus Implants) that is handled properly is very easy to run and the results delight the pc. When errors are made and the GPM is mishandled by the auditor, the pc becomes lethargic, ARC breaky and apparent gains are minimal. As soon as an auditor realizes this and gets alert on his technical, he or she has no trouble getting RIs to RR, the pc has no ARC breaks and succeeding GPMs get easier and easier to audit. A pc being run on these GPMs who develops mass, becomes exhausted or ARC breaky, is simply being run with certain definite R3 errors. Make up your mind to this and you'll begin to be alert when the pc starts running poorly. A pc running poorly on GPMs has had one or more of the following R3 errors committed: 1. Run without preparation on ARC processes (only true when GPMs can't be found and made to RR). 2. A wrong goal found (by wrong wording of a right goal or just a completely wrong goal). 3. Being run on a goal too early in the series too soon, or getting into second series when first series remains. 4. When goal A is found as "the pc's goal," the auditor then runs another goal (true of pc's who have had earlier goals found). 5. That which is restimulated is not discharged. (Finding several goals without discharging them, or scanning over banks.) 6. Running with RIs which differ from the basic line plot (such as "Absolutely" for Absoluteably, or "No" for Nix. There are no divergences from the HCO Bulletin line plot form). 7. Failure to do the end goal oppose list properly (the crime of having 2 or more RRing items on same list in nulling). (Always find the next goal formally by list except when pc can see it, and even then check it.) 8. Incorrect top oppterm for the goal. (Always list a page on "What would be the final achievement of this goal" and properly null it, unless a published block form issued after this date exists for it.) 9. Incorrect block RIs diverging from pattern. 10. Wrong word or sequence form for one or more RIs. 11. Failure to discharge an RI (grinding it out, not blowing it with one or more dial wide disintegrating RRs). 12. Failure to spot bypassed charge at once and thus not caring promptly for ARC breaks. 13. Forcing the pc on after an ARC break without locating the bypassed charge, or running a pc who is in trouble session after session without finding what charge was bypassed. 14. Running a doped off pc without pulling missed withholds (the only cause of dope off). 15. Failing to follow 3N remedies for lack of RR in that exact sequence given in the HCO Bulletin, and harassing the pc for non-RRing RIs. 16. Demanding more data than the pc can give on the facsimiles. 17. Failure to follow the Auditor's Code. 18. Programing incorrectly. ARC BREAKS The most frequent cause of ARC breaks and case deterioration are: 1. Failure to complete a goal oppose list; 2. Bypassing an RI; 3. Bypassing (skipping) a GPM; 4. Wrong top oppterm; 5. Restimulating more goals than are run; 6. Departure from pattern; 7. Bad programing. All these add up to bypassed charge, of course. But the above seven are the specific offenders which give even a skilled auditor trouble. Carelessness on these points can eat up all the immediate case gain. Note: This is the most frequent list, not the most dangerous or important which includes wrong goal. NEXT GOAL The next goal should be found by a formal last goal oppose list, list 50 items beyond last RR or R/S, completed to a clean needle, only one item RRing on nulling. All the rules of listing exist here, full valid. Failure to follow them will cause a skip of or failure to find the next goal. If this list does not have the next goal on it, the pc will ARC break. Sometimes a pc can see the next goal and it is it. In such cases, the goal oppose list is only one item long. But it is still a list and it does have the next goal on it. TOP OPPTERM The most insidious offender in wrecking pc's is a wrong top oppterm. If a guaranteed list of block items exists for the goal, use it. But if no such block item list exists, you must do a list for the top oppterm on the question: "What would be the final achievement of this goal?" Unless a pc random lists foolishly, the list should be about a half a page long with a clean needle. It is then routinely nulled and the BMRs put in on the 2 or 3 items that stayed in. This is however all very tricky as the second series of GPMs has things in them that could read as top oppterms for the first series. So always conclude a top oppterm list by confirming by meter that the resultant word from the list is a first series top oppterm. DIRTY NEEDLE Sometimes in trying to locate the bypassed charge causing an ARC break, the pc's needle is so dirty that it almost can't be read. However there is a way to read it. When the correct bypassed charge is located and indicated the needle will go beautifully clean. ______________ PROGRAMING There is much technology now on programing which will soon be released. Programing is what you audit on a pc and how to establish it. I only wish to note here that for several reasons, the best programing for the Helatrobus Implants for a pc who can be made to RR on "to forget" is as follows: Run right "down" from the GPM "to forget" (including its GPM) and right on out the gates of heaven, doing a proper goal oppose list at the end of every GPM you complete. There are only about 10 GPMs more or less from "to forget" to the heaven implant and they are all easy ones to run. When the pc backs out the gates of heaven an enormous reality results from the orientation achieved. Follow the precautions in this HCO Bulletin and you will have no trouble and the pc will feel great. If you start forward (to the 1st implant GPM), I now find after experience with a lot of pcs, you restimulate too much. The pc always has a live goal (restimulated) before and behind and it's uncomfortable. In backing the pc down you are following the pc's natural tendency and it's easier. Further, all the GPM's after "to forget" (and including it) are a breeze. "To forget" is usually the basic GPM on stairs. The fancy GPMs are all earlier (closer to the first one) and have spinning plates, fast rides etc., in them. They are not hard if the pc has the last 10 GPMs of the first series run first. The more GPMs you restimulate and don't discharge, the more uncomfortable the pc will become and the less apparent gain per GPM. I have now found and run the earliest GPMs "to be dead," which is followed by "to be hurt," "to experience nothing," "to be unbalanced" and "to be unconscious" and believe these are the standard sequence for all pcs in the first series. But they are pretty strong for a pc who hasn't had the end GPMs from "to forget" to "to be in heaven" discharged. ______________ SUMMARY 1. The Helatrobus Implants run give enormous case gain session by session if run with attention to the points given in this HCO Bulletin. 2. They give, when run without the points in this HCO Bulletin cared for, a hard, exhausting struggle that is very slow going and wearing on both auditor and pc. 3. No matter how they're run they give case gain. It's mainly a question of maintaining the thetan's morale and saving auditing time. It can take more than five times as long to run these implants if it is not done with this HCO Bulletin's view. And the pc can get pretty sick. So for a comfortable run, easy on auditor and pc alike, and five times as fast or more, apply these technical points very carefully indeed. I speak form great experience in this matter. On the question, do they have to be run, the answer is yes. Without running them the track remains too heavily burdened for the pc to get earlier with full perception. So there is the barricade. You won't find a new fad removing it. It can only be done smoothly by skilled auditing such as that done at Saint Hill. They may have implanted heaven, but it's hell to run, especially when you ignore the fine points. L. RON HUBBARD Founder ================== 088 HCOB 8 JUN 63 THE TIME TRACK AND ENGRAM RUNNING BY CHAINS, #2 (TV5 p. 287-91, NTV VII p. 187-192) HUBBARD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead, Sussex HCO BULLETIN OF 8 JUNE AD13 Central Orgs Franchise THE TIME TRACK AND ENGRAM RUNNING BY CHAINS BULLETIN 2 HANDLING THE TIME TRACK Although finding and curtailing the development of the Time Track at genus is not improbable, the ability of the preclear to attain it early on is questionable without reducing the charge on the existing track. Therefore, any system which reduces the charged condition of the Time Track without reducing but increasing the awareness and decisionability of the preclear is valid processing. Any system which seeks to handle the charge but reduces the preclear's awareness and decisionability is not valid processing but is degrading. According to early axioms, the single source of aberration is Time. Therefore any system which further confuses or overwhelms the preclear's sense of time will not be beneficial. Thus the first task of the student of engram running is to master the handling of Time on the preclear's Time Track. It must be handled without question, uncertainty or confusion. Failing to handle the Time in the pc's Time Track with confidence, certainty and without error will result in grouping or denying the Time Track to the pc. The prime source of ARC break in engram running sessions is by-passing charge by Time mishandling by the auditor. As a subhead under this, taking and trying to run incidents which are not basic on a chain constitute an error in Time and react on the pc like By-Passed RIs or GPMs. An ARC break-less session requires gentle accurate time scouting, the selection of the earliest Timed incident available and the accurate Time handling of the incident as it is run. There are only a few reasons why some cannot run engrams on pcs. These are: 1. Q and A with the pain and unconsciousness of incidents; 2. Failing to handle the Time Track of the pc for the pc; 3. Failure to understand and handle Time. 2 and 3 are much the same. However, there are three ways to move a Time Track about: (a) By Significance (the moment something was considered); (b) By Location (the moment the pc was located somewhere); (c) By Time alone (the date or years before an event or years ago). You will see all three have time in common. "The moment when you thought _______" "The moment you were on the cliff _______" "Two years before you put your foot on the bottom step of the scaffold" are all dependent on Time. Each designates an instant on the Time Track of which there can be no mistake by either auditor or pc. The whole handling of the Time Track can be done by any one of these three methods, Significance, Location, Time. Therefore all projectionist work is done by the Time of Significance, the Time of Location or Time alone. The track responds. Those auditors who have trouble cannot grasp the totality and accuracy and speed of that response. The idiotic and wonderful precision of the Time Track defeats the sloppy and careless. They wonder if it went. They question the pc's being there. They fumble about until they destroy their command over the Time Track. "Go to 47,983,678,283,736 years 2 months, 4 days 1 hour and six minutes ago." Well, a clear statement of it, unfumbled, will cause just that to happen. The tiniest quiver of doubt, a fumble over the millions and nothing happens. Fumbled dating gets no dates. One must date boldly with no throat catches or hesitations. "More than 40,000? Less than 40,000?" Get it the first read. Don't go on peering myopically at the meter asking the same question the rest of the session. Accurate, Bold, Rapid. Those are the watchwords of dating and Time Track handling. In moving a Time Track about, move only the track. Don't mix it and also move the pc. You can say "Move to _______." You don't have to say (but you can) "The somatic strip will move to _______." But never say "You will move to _______." And this also applies to Present Time. The pc won't come to Present Time. He's here. But the Time Track will move to the date of present time unless the pc is really stuck. In getting a pc to Present Time (unimportant in modern engram running) say "Move to (date month and year of PT)." In scouting you always use To. "Move To _______." In running an engram or whatever, you always use THROUGH. "Move through the incident _______." If an auditor hasn't a ruddy clue about the Time Track and its composition, he or she won't ever be able to run engrams. So, obviously, the first thing to teach and have passed in engram running is Time Track Composition. When the auditor learns that, he or she will be able to run engrams. If the auditor does not know the subject of the Time Track well, then he or she can't be taught to run engrams, for no rote commands that cover all cases can exist. You couldn't teach the handling of a motion picture projector by rote commands if the operator had never imagined the existence of film. An auditor sitting there thinking the pc is doing this or that and being in a general fuddle about it will soon have film all over the floor and wrapped about his ears. His plea for a rote command will just tangle up more film so long as he doesn't know it is film and that he, not the preclear, is handling it. If an auditor can learn this, he will then be able to learn to run those small parts of the Time Track called engrams. If an auditor can't run a pc through some pleasant Time Track flawlessly, he or she sure can't run a pc through the living lightning parts of that Track called Engrams. An auditor who cannot handle the Time Track smoothly can scarcely call himself an auditor as that's all there is to audit besides postulates, no matter what process you are using, no matter what process you invent and even if you tried what is laughingly called a "biochemical approach" to the mind. There's only a Time Track for the bios to affect. There's a thetan, there's a Time Track. The thetan gets caught in the Time Track. The job of the auditor is to free the thetan by digging him out of his Time Track. So if you can't handle what you're digging a thetan out of, you're going to have an awful lot of landslides and a lot of auditing loses for both you and preclears. Invent games, devices, charts and training aids galore and teach with them and you'll have auditors who can handle the Time Track and run engrams. CHARGE AND THE TIME TRACK Charge, the stored quantities of energy in the Time Track, is the sole thing that is being relieved or removed by the auditor from the Time Track. When this charge is present in huge amounts the Time Track overwhelms the pc and the pc is thrust below observation of the actual Track. This is the State of Case Scale. (All levels given are major levels. Minor levels exist between them.) Level (1) NO TRACK - No Charge. Level (2) FULL VISIBLE TIME TRACK - Some Charge. Level (3) SPORADIC VISIBILITY OF TRACK - Some heavily charged areas. Level (4) INVISIBLE TRACK - Very heavily charged areas exist (Black or Invisible Field) Level (5) DUB-IN - Some areas of Track so heavily charged pc is below consciousness in them. [TVXI p. 25 corrects this to "unconsciousness". This appears as unconsciousness in NTV7 without noting the correction] Level (6) DUB-IN OF DUB-IN - Many areas of Track so heavily charged, the Dub-in is submerged. Level (7) ONLY AWARE OF OWN - Track too heavily charged EVALUATIONS to be viewed at all. Level (8) UNAWARE - Pc dull, often in a coma. On this new scale the very good, easy to run cases are at Level (3). Skilled engram running can handle down to Level (4). Engram running is useless from Level (4) down. Level (4) is questionable. Level (1) is of course an OT. Level (2) is the clearest clear anybody ever heard of. Level (3) can run engrams. Level (4) can run early track engrams if the running is skilled. (Level (4) includes the Black V case.) Level (5) has to be run on general ARC processes. Level (6) has to be run carefully on special ARC processes with lots of havingness. Level (7) responds to the CCHs. Level (8) responds only to reach and withdraw CCHs. Pre-Dianetic and Pre-Scientology mental studies were observations from Level (7) which considered Levels (5) and (6) and (8) the only states of case and oddly enough overlooked Level (7) entirely, all states of case were considered either neurotic or insane, with sanity either slightly glimpsed or decried. In actuality on some portion of every Time Track in every case you will find each of the Levels except (1) momentarily expressed. The above scale is devoted to chronic case level and is useful in Programming a case. But any case for brief moments or longer will hit these levels in being processed. This is the Temporary Case Level found only in sessions on chronically higher level cases when they go through a tough bit. Thus engram running can be seen to be limited to higher level cases. Other processing, notably modern ARC processes, moves the case up to engram running. Now what makes these levels of case? It is entirely charge. The more heavily charged the case, the lower it falls on the above scale. It is charge that prevents the pc from confronting the Time Track and submerges the Time Track from view. Charge is stored energy or stored or recreatable potentials of energy. The E-Meter registers charge. A very high or low tone arm, a sticky or dirty needle, all are registrations of this charge. The "chronic meter of a case" is an index of chronic charge. The fluctuations of a meter during a session are registering relative charge in different portions of the pc's Time Track. More valuably the meter registers released charge. You can see it blowing on the meter. The disintegrating RR, the blowing down of the TA, the heavy falls, the loosening needle all show charge being released. The meter registers charge found and then charge released. It registers charge found but not yet released by the needle getting tight, by DN, by a climbing TA or a TA going far below the clear read. Then as this cleans up, the charge is seen to "blow". Charge that is restimulated but not released causes the case to "charge up", in that charge already on the Time Track is triggered but is not yet viewed by the pc. The whole cycle of restimulated charge that is then blown gives us the action of auditing. When prior charge is restimulated but not located so that it can be blown, we get "ARC Breaks". The State of Case, the Chronic Level, as given on the above scale, is the totality of charge on the case. Level (1) has no charge on it. Level (8) is total charge. The day to day condition of a case, its temper, reaction to things, brightness, depends upon two factors, (a) the totality of charge on the case and (b) the amount of charge in restimulation. Thus a case being processed varies in tone by (a) the totality of charge remaining on the case (b) the amount of charge in restimulation and (c) the amount of charge blown by processing. Charge is held in place by the basic on a chain. When only later than basic incidents are run charge can be restimulated and then bottled up again with a very small amount blown. This is known as "grinding out" an incident. An engram is getting run, but as it is not basic on a chain, no adequate amount of charge is being released. Later than basic incidents are run either (a) to uncover more basic (earlier) incidents or (b) to clean up the chain after basic has been found and erased. No full erasure of incidenown Time Track. You cannot have decent, honest or capable beings as long as they are trapped and overwhelmed. While this philosophy may be contrary to the intentions of a slavemaster or a degrader it is nevertheless demonstrably true. The universe is not itself a trap capable only of degradation. But beings exist who, beaten and overwhelmed themselves, can utilize this universe to degrade others. The Mission of engram running is to free the charge which has accumulated in a being and so restore that being to appreciated life. All cases, sooner or later, have to be run on engrams, no matter what else has to be done. For it is in engrams that the bulk of the charge on the Time Track lies. And it is therefore those parts of the Time Track called engrams which overwhelm the thetan. These contain pain and unconsciousness and are therefore the record of moments when a thetan was most at effect and least at cause. In these moments then the thetan is least able to confront or to be causative. The engram also contains moments when it was necessary to have moved and most degrading to have held a position in space. And the engram contains the heaviest ARC Break with a thetan's environment and other beings. And all these things add up to charge, an impulse to withdraw from that which can't be withdrawn from or to approach that which can't be approached, and this, like a two pole battery, generates current. This constantly generated current is chronic charge. The principal actions are: (a) When the attention of the thetan is directed broadly in the direction of such a track record the current increases. (b) When the attention is more closely (but not forcefully) and accurately directed, the current is discharged. (c) When the basic on the chain is found and erased, that which composes the poles themselves is erased and later incidents eased, for no further generation is possible by that chain and it becomes incapable of producing further charge to be restimulated. The above are the actions which occur during auditing. If these actions do not occur despite auditing, then there is no case betterment, so it is the auditor's responsibility to make sure they do occur. As the Time Track is created by an involuntary response of the thetan, it is and exists as a real thing, composed of space, matter, energy, time and significance. On a Level (8) Case the Time Track is completely submerged by charge even down to a total unawareness of thought itself. At Level (7) awareness of the track is confined by extant charge to opinions about it. At Level (6) charge on the track is such that pictures of pictures of the track are gratuitously furnished, causing delusive copies of inaccurate copies of the track. At Level (5) charge is sufficient to cause only inaccurate copies of the track to be viewable. At Level (4) charge is sufficient to obscure the track. At Level (3) charge is sufficient to wipe out portions of the track. At Level (2) there is only enough charge to maintain the existence of the track. At Level (1) there is no charge and no track to create it. All charge from Level (1) and up into higher states that is generated is knowingly generated by the thetan, whose ability to hold locations in space and poles apart results in charge as needful. This would degenerate again as he put such matters on automatic or began once more to make a Time Track, but these actions alone are not capable of aberrating a thetan until he encounters further violent degradation and entrapment in the form of implants. Aberration itself must be calculated to occur. The existence of a Time Track only makes it possible for it to occur and be retained. Thus a thetan's first real mistake is to consider his own pictures and their recorded events important, and his second mistake is in not obliterating entrapment activities in such a way as not to become entrapped or aberrated in doing so, all of which can be done and should be. Engram running is a step necessary to get at the more fundamental causes of a Time Track and handle them. So it is a skill which must be done and done well. L. RON HUBBARD LRH:dr.jh Copyright c 1963 by L. Ron Hubbard ALL RIGHTS RESERVED ================== 089 HCOPL 10 JUN 63 SCIENTOLOGY TRAINING, TECHNICAL STUDIES (OEC V4 p 342) HUBBARD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead, Sussex HCO POLICY LETTER OF 10 JUNE AD13 Central Orgs Academies SCIENTOLOGY TRAINING TECHNICAL STUDIES All Academy Students will be expected as an early activity in training to acquire a knowledge of the Time Track and engram running. Modernized material on this subject is now being released. A Revised Curriculum for Academies places in the hands of the HCA/HPA the fundamental skills of auditing as follows: 1. TheCCHs 2. Self Analysis version of ARC Processes (for training auditing practice) 3. The Time Track 4. ARC Straight Wire Modern Version 5. Withholds 6. Dating by meter 7. Locating and Indicating By-Passed Charge 8. Engram running by Chains 9. Routine 3N 10. Programming Cases In addition it is expected that the common academic subjects be retained such as Model Session, Scales, Axioms, the E-Meter, etc. However, it is clearly visible that no auditor would be worthy of the name if he or she did not have the above listed skills at his or her command. All other types of processing may be dropped. L. RON HUBBARD LRH:gl.rd Copyright c 1963 by L. Ron Hubbard ALL RIGHTS RESERVED ================== 090 HCOB 13 JUN 63 NEW TRAINING DRILLS (Not in either set of tech vols. Since this was not by LRH, it has probably been regulated to the status of a BTB) HUBBARD COMMUNICATIONS OFFICE Saint Hill Manor, East Grinstead, Sussex HCO BULLETIN OF JUNE 13, 1963 Central Orgs Academies NEW TRAINING DRILLS LISTING AND FINDING TOP OPPTERM Purpose: To train student how to find top oppterm. Position: Coach and student seated facing each other. The student has an E-Meter in front of him. It is not switched on. Procedure: Coach uses pencil as needle and produces ticks, falls, RRs, etc., on certain items in answer to,the question asked by the student. Unless random listing is done foolishly, the list should be about half a page with a clean needle. Nulling then commences. Each item is called out 3 times and the Big Mid Ruds are put in on the 2 or 3 items that stayed in. The student writes each item down. When the top oppterm is found it must be confirmed by "meter", that is, it is a first series top oppterm. Patter: The student asks coach:- "What would be the final achievement of this goal?" (To catch catfish) When the top oppterm has or has not been found the coach asks the following questions:-( 1) Was the needle clean when you finished Listing? (2) Did you put the big mid ruds in on the 2 or 3 items that stayed in? (3) Did the item that stayed in RR? (4) Did you confirm by meter that it was a first series oppterm? Training stress:- If the student shows any uncertainty or comm lags during the drill, the coach asks "What happened?" LISTING AND NULLING TO FIND THE NEXT GOAL Purpose: To train the student how to find the next goal to be run. Position: Coach and student seated facing each other. The student has an E-Meter in front of him. It is not switched on. Procedure: The coach uses pencil as needle and during the drill produces rocket reads and rockslams on certain goals. Student writes down each goal on paper. Nulling is not commenced until 50 goals have been listed beyond last RR or RS and the needle is clean. If coach produces a dirty needle when student starts nulling, or more than one RR or RS, or an RR and RS, the student must then ask for more goals immediately. Patter: Student asks coach "What goal would To Catch Catfish oppose?" When list is complete the student nulls the list by calling each item 3 times. This is done until one goal remains in that RRs. When goal has or has not been found, the coach says "Thats it" and asks the following questions: (1) Did you list 50 items beyond the last RR or RS? (2) Was the needle clean when you finished listing? (3) Was the needle clean during nulling? (4) If the needle dirties up during nulling, what should you do? (Ask for more goals) (5) If more than one RR or RS or an RR or RS appear during nulling, what should you do? (Ask for more goals) (6) Did the needle dirty up? (7) Did you see more than one RR or RS during the nulling? (8) What happened? (9) What did you do? (10) Did you find the next goal? Training stress:- If the student shows any uncertainty or comm lags during the drill, the coach asks "What happened?" 3N LISTING TR Student and coach have a copy each of the line plot. Use goal such as TO CATCH CATFISH. The coach uses a pencil as the meter needle and indicates to the student motions he will make to indicate a tick, choked RR and disintergrating RR etc. The coach runs the TR as per session instructions in HCO Bulletin May 13, 1963. At any time, if the student shows any hesitation, the coach asks "What happened?" When the student has found one or more items the coach says "Thats it" and asks the following questions: (1) Did you ask the correct command? (2) Did I give you the correct item? (3) If the item RRs what do you do? (Say "thankyou, I'll read the item", then check to see if all charge is off) (4) If there is any other reaction what do you do and in what order? (Ask (1) "What happened?" (2) Supress and Invalidate off the meter (3) Random list) (5) What was the needle reaction when I gave you the item? (6) What did you do? (7) What was the needle reaction when you read back the item? (8) What did you do? (9) Did you get all the charge off the item? (10) How could you tell all the charge was off? MISSED WITHHOLDS The student sits opposite coach. Student runs "Do birds fly?" or "Do fish swim?" on the coach. The coach runs the process for a while and then dramatises missed withhold manifestation. Student then locates missed withhold. The student may ask the coach any missed withhold question and ask it on "the meter" (coachs finger or pencil indicates reads). If, however, the ARC break is not showing on "the meter" the student has to dig to find it and clear the missed withhold. When this is done the coach asks the following questions: (1) What is a missed withhold? (A nearly found out) (Anothers persons actions) (2) Did you find out what had been done that had been missed? (3) Did you find out when it was? (4) Did you find out who missed it? (5) Did you find out what it was the other person did that made them wonder if they knew? (6) Did you find out whether or not it had been missed by anyone else - auditor, etc.? (7) Have you cleaned up the missed withhold? (8) When has a missed withhold been cleared up? Issued by: Jenny Edmonds Practical Supervisor, SHSBC for L. RON HUBBARD Authorized by: L. RON HUBBARD LRH:gl:jr Copyright � 1963 By L. Ron Hubbard ALL RIGHTS RESERVED ================== _