6309C04 SHSpec-302 How to Find a Service Facsimile Apparently, there is more to know about service facs than has been relayed, probably because it is so simple. PCs don't defend their service facs against discovery. If you point the PC in the right direction, he will go right to the service fac, unless you prevent it. So don't prevent it! In assessing for service facs, there is no substitute for knowing what a service fac is. A service fac is, first, a tremendous solution, always aberrated, in PT, as part of the PC's environment, which, the PC believes, would result in his survival being threatened if it were disturbed. It is something which others keep telling the PC is wrong, causing him to assert that it is right. This assertion of rightness is very integral and important to the service fac. It makes the PC unauditable to the degree that he is getting auditing only to prove that it is right. It sticks out like a sore thumb. One could have more trouble labeling it than finding it. The human body is a service fac, but if we used that, we would be going for OT, and we aren't shooting for that. We are just using the service fac on this lifetime, to get the PC auditable. So the body isn't the service fac that we are trying to target. Having found a service fac, we don't use it to make an OT. We are only trying to get someone auditable and to get the constantly restimulated solutions out of the way, to clear this lifetime. On the whole track, obviously, having a bank is a service facsimile. That accounts for the reluctance to go clear noticed earlier, while finding goals. "Being incapable" could still be a service fac at an OT level, if, say, the OT couldn't tilt a planet. But attacking this kind of service fac directly is too steep a gradient. You could run service facs at all different levels. The concept of a service fac is based on confusion and stable datum theory. In running a service fac, we are attacking a solution that is a barrier to getting rid of a confusion. You can pluck the stable datum out of the center of a confusion and thus get a discharge of the energy of the confusion. A stable datum holds a confusion in place. This is the reverse of using a stable datum to handle a confusion. Charge is an electrical confusion. As long as a stable datum holds a confusion in place, the confusion will not discharge. Confusions are tolerable and are not always aberrative. Most have no aberrative value, e.g. in a card game. Life is not, in itself, an aberrative action. There has to be some force and violence involved in the confusion, or at least a fairly real threat to survival, for it to be aberrative. The thetan "knows" that if he ceases to dramatize a service fac, he will die. The immediate thing someone is worried about may not be the service facsimile itself. It could be the consequence of something else that is a service fac. The consequence could be very hidden; the two things could have at best a faint connection. As you take off service facs, the central one on which they all lean eventually comes off. As you audit the case, you could get off several before the central one comes to view. The apparent service facs lean on the main service fac. A rote procedure to apply to this would be a logical solution to a very illogical area, but it is better to understand what you are doing. If the case has been audited, you could collect a list of things that have been found on the PC, e.g. old lists, R2-12 assessments, etc. By discussing them with the PC and following the PCs interest, you could find some service facs. You might have to reword some of the things you come up with, The right-wrong bracket is always the same. The question is, "How would (the condition or thing found) make you right and make others wrong?" The service fac is the PC; it is something he has; it is not like an oppterm. It is something he has, to make him right and others wrong. The PC will slop, on the auditing command. E.g. the PC may misduplicate the auditing command as, "What would be made wrong by it?" You don't worry about this. Let the automaticity run out. Then re-ask your original question and get it answered. A service facsimile is not an action. An action would be the result of a service fac. The service fac turns on automaticities because it is an automatic, unanalyzed solution. For this reason, you don't run it as a repetitive process. "Automaticity" means that more answers than the PC can articulate are arriving from the bank. When this happens, when words are coming too fast, you know that you are getting the service fac. Throw the question in and let the lions tear at it for awhile; let the automaticity run out. Let "er buck when the PC starts to run. Then, when he runs out of answers, turn it around and run it the other way, if he hasn't already done it himself. You are trying to get rid of the avalanche of automaticity and get TA. Also, don't overrun by insisting on more answers than the PC has, or you can get a stuck flow. Run it permissively. It is sometimes difficult to keep the PC answering the question, just because he is in a dissociated area. The solution is holding back a tremendous amount of aberration, which won't as-is as long as the solution is there. The solution just keeps accumulating mass. The solution is always below 2.0 on the tone scale, because it is perforce a substitute for an itsa line. The PC felt that he could not itsa the object that he was trying to make wrong, so he dreamed up this solution as a final solution, and that is a substitute for an itsa line. Then there is no as-isness or itsa on the environment. Since there is no as-isness, you get an accumulation of mass. Since it is a substitute for an itsa line, the service fac is referred to whenever the PC refers to anything. When the solution is below 2.0, it propounds the idea that to survive, it is necessary to succumb. That is what it boils down to, aberrated though that is. For instance, the solution may be not eating [as in anorexia nervosa]. The service fac doesn't even have to fit in with the guy's environment. It is often totally hidden. You can't necessarily spot the service fac by what the person is doing. It often goes underground, especially the very hidden ones. Some are very obvious, too, sometimes so obvious that you miss them. You could ask, as an L and H question, "What do you think your service fac is?" Interest is the keynote. The service fac is not a deliberate solution. It is a sub-awareness automatic solution, which the person is on the verge of all the time. That is what makes service facs easy to spot. If you've got the service fac, the PC can't stay out of it. It has to be specific enough. You can use a "represent" on something that is too general. You can assess the list according to interest. The PC tends to fall into the whirlpool of the service fac. If the PC has a fragile tone arm, easily stuck, then you've got a service fac, a solution there that is preventing the charge from running off. The PC doesn't have to look at things; he's got it solved. Once you have the service fac, get the PC to tell you how, in this lifetime, it would make him right, etc. Don't go for the backtrack. This improves the PC's ability to get TA action. The peculiarity of the action you are looking for is not particularly great, compared with the peculiarity of social mores, but it is posing as survival when it clearly isn't pro-survival. The PC will be interested in it, and it will get TA, because it is a fixed solution. Your main interest is TA action. Just get the mass flowing that was hanging up. A service fac is a fixed, contra-survival solution which the person hasn't inspected. It could even be a fixed survival solution, but then that wouldn't interfere with auditing. However, using conduct as a criterion makes anyone liable to be put away. A service fac is batty when compared, not to the mores of society, but to actual survival. So you could say the following about a service fac: 1. It is contra-survival, but poses as survival. 2. It has the PC's interest. 3. It sticks the tone arm. 4. It is always protruded into PT. Thus any constant PTP can contain a service fac. For instance, you could ask, "What did you come into scientology to resolve?" That is one reason that service fac processing is beneficial. However, it is dangerous to list too many problems on a PC, because you are giving the PC too much whatsit, while an incomplete list will ARC break the PC. So you had better two-way comm it. Use a friendly discussion, so you can move out of it if it gets sticky. Don't list it. When you find an appropriate problem, find the solution in back of it, and that fixed solution will give you the service fac. If the discussion does get sticky, you could free up the TA again by asking for a solution that the PC has had to each problem he mentions. Getting a fixed solution means that you've got the service fac. Notice that R1C and R2C are designed to strip away solutions and stable data. Therefore, they are not likely to freeze up the TA. Find out if the PC has run R1C and R2C. You can use this for data. You can ask what the PC found interesting. Don't ask, "What problems would that solve?" That sticks the TA. Assess it. Then you can get the service fac. The R3R preliminary assessment is almost a dead-center pitch at the service fac, providing it winds up with a statable solution. This solution should be something that makes sense to you and the PC. Getting the item with the PC's interest will give you the service fac. The level assessed will be too broad. The service fac is a magnet. You are asking for right answers, and the PC is giving you the rightest answer of all. You can even get the service fac as a non-sequitur item on a list. So watch for service facs on any list. The fact that the item that is a service fac is dissociated gives you a clue. The PC will handle your session with his service fac. Eventually it downs on you what he has been doing. Keep running service facs until you get change in the PC and a free needle and good TA. The service fac is the source of the PTP that the PC keeps coming to session with, so getting it saves you all sorts of time and trouble, when you get it out of the way. Get rid of the service fac, and over-restimulation of the case ends. This would reduce by 50% the total restimulation on the case, so cases wouldn't keep dropping between sessions because of environmental restimulation. Having the PC's attention on disabilities keeps his attention off the bank. Thus a good handling of service facs increases by a hundred to one the runability of the case. So you can now run him on a steeper gradient.