From nobody@REPLAY.COM Sat May 16 21:05:08 1998 Path: spln!extra.newsguy.com!lotsanews.com!su-news-hub1.bbnplanet.com!news.bbnplanet.com!news.alt.net!anon.lcs.mit.edu!nym.alias.net!mail2news Date: Sun, 17 May 1998 06:05:08 +0200 (MET DST) Message-ID: <199805170405.GAA01828@basement.replay.com> Subject: FZ BIBLE 3/3 ERRORS IN TIME From: nobody@REPLAY.COM (Anonymous) Organization: Replay Associates, L.L.P. X-001: Replay may or may not approve of the content of this posting X-002: Report misuse of this automated service to X-URL: http://www.replay.com/remailer/ Newsgroups: alt.religion.scientology,alt.clearing.technology Mail-To-News-Contact: postmaster@nym.alias.net Lines: 436 Xref: spln alt.religion.scientology:300950 alt.clearing.technology:38564 FREEZONE BIBLE ASSOCIATION TECH POST TRANSCRIPT OF THE ERRORS IN TIME TAPE 3/3 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. 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 the Christians are not good and obedient Jews and yet are allowed 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 ************************************************** ERRORS IN TIME St. Hill Special Briefing Course Tape lecture of 18 July 63 6307C18 SHSBC-287 renumbered SHSBC-316 ************************************************** (continued from part 2/3) In other words, you can have a room, and the person is put on a bed, and the screen and so on, is at a diagonal up in front of them or at the other end of the room, and it shows a three-dimensional view of events or something like that. Meantime the person is being hit with this and that. It could be as simple as some kind of a scope that has a movie running in the back of it, you put your face or your face is put up to this scope and anchored there with some electric blasts, and at this close range, why, the thing runs off at a mad rate, and there it goes, with appropriate jolts in the right places. It could also be, it could also be a full set which is lugubriously - and this is earlier track when they didn't mind mass so much. If you find any back there they probably have full sets connected with them. They move them like a stage set. One of the trick ways of building these things, you take these two crayons here, you notice that it - that they are not a consecutive line if I hold them like this. And if you pull them down like this, they look like they're a consecutive line, don't you see? But there's a hole between the two of them. So the set moves up and then goes this way around the person. You understand? If a person is anchored there on a stake, or something like this, you see, when they - when the set moves then, why, they just jog the set. And he passes through this slit, which he can't see. Looks very mysterious to him. He's in one environment, total 3-D environment, he's in the next environment, total 3-D environment. After his sonic and visio picks up a little bit, however, he can hear the scene shift. They really make a lot of noise. And that type of thing, by the way, is used in some very early implant serieses types of pictures of this kind. The Helatrobus, the Bear and Gorilla and Glade Implants, none of them use pictures. They sometimes - there's only - the only picture I know of used in the Helatrobus Implants is on a railroad on which you travel sideways at a vast rate of speed. And when you meet the railroad, when you come down to the railroad, you'll see that there's a section house right at the point where you're put on the track. There's a house there, see? And then as you move down the track, a board goes up in front of you, and it's the same section house. So actually you're moved at sixiy miles an hour sideways with the same section house sitting in front of you. And this is supposed to confuse you enormously. But almost any thetan, no matter how anaten he is, can see that it's just a board shoved up in front of him. In the Gorilla and Bear GPMs, and so on, they do put a figure on the cart with the thetan. They've - there's a guy in a pink shirt with a monkey peeking out from behind him, put on the ride carts. A guy in a pink-striped shirt - very, very interesting. That's their - that was their badge, the hoi poiloi. And you'll see this bird with a pink-striped shirt. Sometimes you have a gorilla in front of you. Sometimes it's the gorilla who is spitting things at you, and that sort of thing. They use figures. But this is not the same thing I'm talking about. Don't think you're mixed up in one of these things just because in an implant, why, somebody jumps up with a picture, see, or something like that that's just a momentary picture. This is not the same intention. That's just to get you to make pictures, or louse up your pictures, or something like that. No, we're talking about another type of incident, another type of incident entirely, where you're hit with electronic blasts, at the same time you're hit with a series of pictures, which purport to be a past or a future for the individual. And when you run into that one, when you run into that one, why, if you don't recognize that these things can exist, why, you've had it. Now, this also gets in the road of running an actual incident. You've got an actua planet-builder incident, and it looks pretty wild to you. And it doesn't look like the pc could possibly have done it, and so forth. And you date it, and it's got a perfectly right date, and so on. And you've got no read of any kind on false pasts or anything of this character, and yet there's that picture and it seems very incredible to you that the pc could be running this at that particular level or line, and that sort of thing. You can get tangled up on this, but just don't forget to run the incident. Get tangled up all you please, but run the incident. If it's a right incident, it's a right incident. If it's a wrong incident, you'll never be able to find the beginning of it. About the most maddening activity you can get into is get into one of these false-past things, and go whirring along at a mad rate trying to find the beginning of the incident. Of course, you never make it. You eventually will find a beginning of an incident, but it'll be an incident of such fantastic magnitude that you've got yourself - Aw! The hell with it! You know? It could take you four, five, six sessions, just to try to find the beginning of that sequence of events. Well, there's no sense in beating your brains out. If you can't find easily the beginning of an incident, you better get interested in whether or not this thing has got a false past or a false future in it. That all depends of course on having your date right. Now, how do you clean up somebody, how do you clean up somebody with something like this? Your approved technology at the present moment is clean up his wrong dates. I'm giving you this material because right now some of you are engaged in running a Prepcheck on wrong dates. And it's a very good thing you are. You're getting tremendous tone arm action, you're getting results on this sort of thing, and this is all a very happy thing. Remember this: When you start correcting dates, the first thing you're going to run into is any false-past or false-future incident that you have triggered on the pc. And you're going to run into it head-on. So you beware of redating. Don't redate incidents endlessly. The first order of business is get in there and pitch on the subject of an incident containing a false past. And when you've got that found, because it'll be there, when you've got that found, and when you've got it run... Don't just find it and date it and walk off, because look, you're not going to date anything else from there on except the track, that is in it! You can date endlessly. You could run a pc maybe thousands of hours, cleaning up this false track which didn't exist. They can see it and so forth. So, look, if you got your hands on an incident, now, here's one of your rules of the game, when you've got your hands on an incident - even though it's hell to run and upsets the pc, and everything else, and so on - when you've got your hands on an incident which contains a false past or a false future, you finish that incident. You understand? Finish it from one end to the other. Do anything necessary to get it the hell off the track. The best way to handle it, of course, is with R3R. You just do standard R3R on the thing. And remember that its pretended duration will be in the millions or billions or trillions or quadrillions. And its actual duration is probably in the matter of hours - at the most a day or two. So I have to give you all this data now, and it's a good thing that it's turned up, because you just start correcting dates on a pc and about the first thing you're going to trip into is the phenomena of false past with all its attendant false dates. And the moment you get collided with one of those things you've had it. You want to do a pc an awful lot of good, however, get rid of one of them. Don't mistake me, they're hell to get rid of. You take the pc to the beginning of the incident, and he goes to the beginning of the incident. Only the beginning of the incident is also inside the incident, as well as at the beginning of the incident. You get the idea? He finishes up - he finishes up the incident, he leaves the incident at the point where it says he left the incident, but that's a picture of his leaving the incident, and you haven't run out his leaving the incident, you got the idea? These things usually have a minimum of two beginnings, identical, and two ends, identical. If you know that, why, you can sometimes pull the fat out of the fire. This thing - you don't do anything with it, unless it starts running badly. If it runs badly, why re-duration the actual incident itself, and square it around, and just do a routine, workmanlike auditing job. It doesn't need anything extraordinary about this thing. The pc will eventually plow on through it. All you need is very standard auditing. Very standard R3R, just its usual steps. You get into a fight with the pc about the thing, however, it's always perfectly kosher to tip him off and say, "Well, are there two beginnings?" Ask on the meter, "Are there two beginnings to this incident?" Pang! Pang! Well, you know you got a false past incident, see? "There are two endings? The reason you're having trouble with reaching the end of the incident, are there two endings to this incident?" Pang! Pang! "Yeah, you got your two endings on the end of the incident." Pc says, "Huh! There are!" As well as another beginning and ending of the incident that merely says it begins and ends at this point, which is inside the point when it really begins and ends. Talk about confusion. These things are confusing to handle. But standard processing, right as of this minute, handles them. And you're going to run into them head-on, the instant that you start correcting anybody's dates. It's one of the first things that'll raise its hand, and elect to fall in your lap as an auditor, is one of these incidents. Well, what if you're - what if you're in X Unit, and you've been ordered to do a Prepcheck on wrong dates on the pc, and so forth, and the pc starts sliding all over the track, and you're not supposed to do anything but correct that? Let me tell you the wrong thing to do. Let me tell you the wrong thing to do: Get your hands on one of these false-past or false-future incidents that's full of dates, get it dated precisely and then walk off and leave it and try to do something else. You're not going to get anything else done. I can tell you that's wrong. I won't tell you what else to do, because I'll probably contradict the orders your Instructors will be giving you. But I can tell you what not to do. Don't walk off and leave it. Because you have run into, restimulated and excited thousands of dates. Hundreds or thousands of dates have been excited, just like that. And if somebody didn't have that pc's auditor's report, and that pc ceased to be audited in some way, somebody would be wading through that for a long time trying to find the actual incident again. One of the rules of auditing, one of the little rules that goes along with: don't talk to people who are unconscious, you know - around people who are unconscious, and don't - and all aberration is at the bottom of the aberration a lie; a lie causes aberration - along with that is the fact that when you got your paws on something, you handle it. That's a maxim that I go by in my own auditing. When I find that lying under the needle of my E-Meter is something that's bothering the living daylights out of the pc, not because he put it there, but because it arrived there in the course of auditing, I handle it. I don't expect the pc to go on struggling with this thing as a PTP while I do something else because "I'm supposed to." When I get my hands on something in a case, I handle it. You understand? It makes for a little - much less trouble with a case. You get your hands on something, your - this thing is going crash! on wrong dates, crash! on wrong dates. Well, rrrr What the hell! You got the pc right there on wrong dates; what are you going to do now? Are you going to skip that? You see? Walk off and leave it? Well, you know it's top-level stuff. How come wrong dates? What are these wrong dates all about? Let's deal up a few of these wrong dates. Let's find out what this wrong date thing is. You're unfortunately liable to find yourself in a process you're not permitted to run. Just remember this. If you louse up your pc - well, I always make sure that you get two thousand words! And remember this: I never ask how it was done. That's good enough, see? Somebody loused up a pc, why, bang. I'm very interested at that point. He loused up the pc. I'm not interested if he loused up the pc because the Instructor said, or because he did, or because the bulletin said, or the this said or the that said, or something else said; I'm just interested in that he loused up the pc, see? I have a very short-circuited view of the whole thing. Because auditing is auditing. You're supposed to do auditing. I can lay you down thousands of rules on the subject of auditing. I can guide your footsteps very directly. I can give you information on the subject of auditing. I can do everything else. But I can't sit in that chair and audit your pc. You understand? And auditing, from my point of view, is supposed to produce beneficial results on a pc. That's my narrow-minded attitude. You understand? So that here's the - here's the pc - here's the pc, and we're supposed to produce good results on the pc. Well, if you don't know how to do this or how to do that or something else, I can show you how to do this or how to do that. Well, you can't ever tell what is going to come up in this case. When it's going to come up. You're not - you can't tell. Now, when you're auditing a pc, when you're auditing a pc, very often a pc comes into session in no fit shape to go on with what you're running on the pc. It's very heroic of you to try to keep on running what he's on, but remember that you can sometimes not accomplish anything by doing just this. You sometimes have to handle the pc, right there in front of you. Now, similarly, you innocently set forward to do a fundamental action on a case, like straighten out his dates. And you suddenly see yourself staring down the barrel of the incident responsible for the wrong dates. Now, remember, there's your big auditing cycle. Your big auditing cycle is to accomplish what you're trying to accomplish with the case. And you better figure out what you're trying to accomplish with the case that you're auditing. In this case you're trying to straighten out the pc's dates, right? All right, that's your big auditing cycle, right? All right. So, you're trying to straighten out the pc's dates. Now, if you go ahead and handle his lumbosis, God help you, see. I mean that has nothing to do with it. You're trying to straighten out his dates. That's a Q and A or a mess-up, see? You're trying to straighten out the big auditing cycle on this pc - we're going to get the wrong dates off this case - and suddenly you are presented with something which is outside the perimeter of the permitted process, or something like that. What do you do with it? I can tell you what NOT to do with it. Neglect it. Now that's what you must not do with it. Because you very often can't get your paws on it again. You've made a big problem for somebody else. You can't straight - when you - listen: When you've found the source of the pc's upset, what other source is there to find? See? You got that? So if you're supposed to be running, "Which ruddy rod have you stuck between your ears?" and you all of a sudden find yourself staring at the source of his upset about ruddy rods, I can tell you how not to help the pc: Ignore the fact that you have found the source of it. This results in an invalidation of the source, and nothing happens. You understand? You have to ask yourself, why are you running this thing about rudy rods between the ears? That's the big auditing cycle. Don't ever subordinate your big auditing cycle to the minor auditing cycle. You understand? See, there's your big auditing cycle, and then there's your process auditing cycle - you're supposed to flatten this process, see? But your big one is what you're trying to - intend with the pc. And then you're - what process you're running on the pc, and then you've got your other auditing cycle, which is your repetitive give and take of auditing commands, don't you see? All right, the second that you - some auditors can just get on this give and take of auditing commands and neglect even the process they're trying to flatten, see? And some, running the process they're supposed to flatten, actually can run into the denouement of the big auditing cycle. That's the end, see? The big auditing cycle - they've collided with the thing. This person has been terrified of ghosts. This person has been terrified of this particular subject. Every time they go to bed at night, why, they won't turn out the lights. You see? They've been this way since childhood, or something of this character. And all of a sudden, you're running this process of somekind or another, you're straightening out something, and the big auditing cycle turns up and drops into your paws. See? They say, "No! Not really! I'm a ghost! Ha-ha! Me! Ha-ha-ha! What do you know! I've always been afraid of myself." Now, what are you going to do from this on? What, are you going to be a complete knucklehead? Going to be a complete jackass? Having found the source, now you're going to try to do what? I'm just bringing it to your attention, what else is there left to do? There isn't anything else left to do. Somebody cognites his chain level - his level item assessment out. "Say! What do you know! It's a so-and-so and it's a th-lul, and it's a du-du-ddl, and fa-dt-d-d-dt! And, ha, well, ha-ha! What do you know! That's in the bag! That's why that level operated!" And you say the level. You say the level, "be leery of cats." Tone arm is down. Now, what are you going to do? Flatten the chain? You have to ask yourself this question. What chain? What chain are you going to flatten? Where? It now isn't! That is known as your big auditing cycle. That's what you're intending to do with the person. If you don't know that, I can see you someday auditing a person up to OT, and they arrive at the point of OT. And you get very upset, because you haven't completed your auditing cycle! You understand? So that's present in all auditing. Having found the source of the aberration in wrong dates, what you going to do? Look for another source? What you haven't got in your mind, then, is the big auditing cycle: What were you intending to do with the pc? What does this process intend to do with this pc? Wrong dates? Well, it's supposed to straighten out the pc's wrong dates, what else? And all of a sudden - you didn't even ask for it, and you possibly in a lot of cases won't get it right away, unless you're running R3R work - all of a sudden you've got your paws on the source of the pc's wrong dates! What you going to do? Run the process, of course. What nonsense. You're going to go on and say, "Give me another source for wrong dates. Give me another source for wrong dates. Give me another ... " He's just given you the source for a wrong date, see? What - the second that you say, "Give me another source for wrong dates", what are you looking at? You're looking at invalidation of THE source for wrong dates and from that point on you have thereafter defeated your auditing. See that? So there's where it'd go. So all of a sudden this guy suddenly says, "Hey! Hey, hey, hey! There's a bup-ut-ut-it and a zu-zuz-up and all that track I thought I - uh - mmmulp!" You speak about wrong dates, well there it is, see? What are you going to do? Now, you make your peace with the Instructors, but remember I count on you to handle the pc. Thank you very much! **************************************************