6309C11 SHSpec-306 Service Facs and GPM's

HCOB 8May63 "Routine 3 -- The Nature of Formation of GPM" says, "The
early GPM's contacted are implants. This does not mean the PC's own GPM's do
not exist." The PC's own GPM has power and velocity over an implant GPM in a
ratio of 1000 or 100,000 to 1. There is a great difference in order of
magnitude. The whole and entire amount of implanted GPM's -- all together --
are one RI of one of LRH's GPM's: the oppterm goals, which is one of about a
hundred RI's on a personal GPM, which extends from trillions 30 to trillions
20 on the track and is actually still continuing.

A number of you have some protest on the length of the time track --
multiple trillions of trillions, etc. "Modern times" is trillions 13 to now
-- the stuff that is likely to influence the PC in PT.

What you are doing in R3SC is "fooling around with the PC's current RI in
his existing PT goal line of his current truncated goal [GPM]." There is an
opposition to it. Clearing up this stuff is clearing a dumbbell pair out of
the PC's own GPM, restimulated in PT, out of sequence on the track. The PC's
goal will fall out of this with a thud. It is probable that while you are
listing for the PC's service fac, you will get the PC's goal, rocket reading.

The amount of aberration required to reduce power must be comparable to
the power reduced. To account for the reduction of power of the thetan, we
must find some force of equal power that could aberrate him. All the implant
GPM's did was to confuse you as to what was your goal and what was an
implanted goal. Implanted goals were installed backwards, from top to
bottom. An actual GPM is run the way it was lived: from bottom to top. Use
R3M2 to run actual GPM's.

[R3M2 is apparently a variant of R3M. R3M is a method of running the
sequence of actual GPM's, RI by RI, starting either with an RI or with a
rocket-reading goal. Starting with the goal, the first RI is obtained by
using a "goal oppose list", also known as a "source list", more or less with
the wording, "Who or what would (the goal) oppose?" Subsequent RI's are
obtained by "RI oppose lists". These have to be listed right-way-to. There
are different rules for finding the item on these two sorts of lists. Each
RI, after it is found, is packaged by relating it to the goal and to the RI
found just before it, and, when verified, is added to the line plot. This
packaging step also lets you know when you have entered a new GPM, as the RI's
will no longer relate to the goal previously found. When this happens, the
new goal is found by doing a new goals list for a new rocket reading goal. Or
the PC may volunteer the new goal. You can also start R3M with an RI, perhaps
one that was obtained from R2-12. In this case, you just keep doing RI oppose
lists and getting new RI's. By the time you have several RI's, the PC will
give you his goal. But you continue with the RI oppose lists. Other
references on R3M are to be found on p. 382, above.]

Don't use an early actual goal as a service fac [and try to run it as
such.] If you do this, you are making the guy look down the goals channel.
The goal in an actual GPM is the furthest item from PT, being the bottom
terminal. When you get the PC to reach down for that goal, he is, to some
slight degree, traveling through time between that goal and PT, and he livens
up the whole track, which is a lot of charge. It is like looking down between
the rows of the Helatrobus implants. You get a tunnel of blackness. That is
what happens when you reach down a GPM. The same thing happens with the PC's
GPM channel, only it is a quite different order of magnitude. With the
Helatrobus implant, it is not so good to do this, but with the PC's own actual
GPM channel, it is like having your head shot off with a sixteen inch cannon.
The residual charge in an actual GPM is incomparably greater.

If the goal comes up as you look for a service fac, put it in the
Auditor's Report Form, clearly marked with a red circle, and don't do much
with it, except in R3M2. If you run it, you are getting the PC to look down
through the GPM to the beginning of some track, with at least a hundred RI's
between you and it. You will get TA, etc., if you run it as a service fac,
but the PC running it will scuff up his track.

The PC's own GPM looks like a black island, floating. It is quite
meaty. They come in different sizes, but each is a distinct size. You are
running the PC back and forth from the bottom of a mass maybe three feet
thick, 75 feet long, and 30 feet wide. You could well restimulate so much
mass that the TA will, all of a sudden, freeze up. You would have to remedy
this by working out the GYM with R3M2. The PC's own GPM has the beauty of
disintegrating as you work with it. You get rocket-reading blowdowns. The
black islands turn grey, then start shaking and fraying, like opaque jello
that someone left in the sun. The power in this early GPM is commensurate
with the native power of a thetan, i.e. there is a lot of charge on it. This
charge doesn't discharge through the PC or the meter, luckily.

The technology for handling this is all in R3N [See pp. 414, 426,
456-457, above] and R3M2. RI's relate to a goal, but each as its own central
postulate, with regard to the goal. This is true of every RI in the PC's
GPM. For instance, the current RI might have a central postulate of "to ring
bells", where the goal is "to go to school". You might get an oppterm of
people who bring their lunches. Without knowing the goal, this would be
puzzling. That's why it would be an aberrative factor.

R3SC will land you somewhere in the vicinity of the current oppterm or
terminal of the PC's own GPM. as it applies to PT, or it may land you near
some old RI that is in restimulation in PT. That will be the source of the
PC's PT restimulation. With R3SC, you can knock that in the head. You can
pull its central postulate. But when you try to make the service fac make
sense, you may find it impossible to do so until you relate it to his goal, by
running R3M2. So that is actually what you are auditing when you find the
service fac.

You could find a service fac without a meter by having the PC write a
list of solutions, until he is easy about it and feels that it is complete,
then looking on the list for the solution that makes the least sense.
However, when seen as an RI, such things can be seen to make sense.

When you are handling a service fac, you are handling the central
postulate of an RI. So running R3SC disintegrates the RI. The thinkingness
of the RI is sometimes different from its beingness. E.g. you may have the
RI, "a lame man", but from that, you may not know what the significance is
that lies within it, i.e. you may not know what the central postulate is. You
could list for this and find it. It may turn out to be "lameness".

Things can be audited nicely without being related to the GPM where they
occur, even though, under these circumstances, they might not make sense. A
service fac is actually not a whole RI, but just the central postulate of an
RI. You are handling the central postulate of an RI when you are handling a
service fac, so you get a disintegration.

A being assumes an identity because it has a solution in the middle of
it. For instance, in the middle of the identity, "a lame man", we may find
"lameness" as a solution to something. Sometimes an RI comes up as its own
thinkingness, but a beingness RI in particular may have an idea at its core.
An RI always has an idea at its core, but sometimes you don't have the central
idea when you have the RI. Given the RI, you could list for the central
significance, which is "an automatic solution. It's safe. It solves
everything." [This safe solution would be the service fac.] That is how an RI
is generated. The thetan has an idee fixe, so he never has to inspect in
order to solve, so therefore he never as-ises the mass, so therefore he gets
caught in the middle of the mass. If the thetan does this with a goal, he
gets an accumulation of RI's resulting from this goal. Each of these RI's has
the goal carried through into it, but there is also a new idea that makes each
RI. And that whole mass comes together as a GPM, so you get this huge mass,
this huge block of energy, with its separate items in it. They don't appear
separate. The whole thing is all squashed together from so much attack and so
little inspection. The whole thing is dominated by one goal, e.g. "to go to
school", which is common to every RI or identity within it. This is what it
is accumulates it. But that goal, all by itself, is no-inspection; it is a
way to solve all problems, totally uninspected, in a fixed way. For instance, the goal "to solve all problems, go to school", is a totally uninspected solution and now gathers to itself identities who have this idea, as well as other characteristics. Because the goal is uninspected, automatic, and fixed, it generates into itself the second step of identities, e.g. "an idiot child", that have the goal as a central idea, but which already have their own characteristics. They have the main idea -- the goal -- as dominant, but the characteristic of the identity, after it is no longer able to carry out the postulate, is something like that of an idiot child. The idea of "an idiot child" is "people like unintelligence." So the central idea may be "unintelligence solves everything", but the RI is "an idiot child".
The only way that it could exist in the first place was that the thetan had
the idea of the goal. ["to solve all problems, go to school".]

So there are three types of ideas in GPM's:

1. The goal of the GPM. This is the first postulate and central idea of
the GPM.

2. The central idea or postulate of the RI, which in itself forbids
inspection.

3. The identity or individuality or the RI. This is the accumulation of
mass that results from the fact that (1) and (2), above, being fixed,
uninspected solutions, forbid itsa and hence forbid an as-isness from
occurring.

That is the anatomy of an RI, but it also tells us what a service fac is.

This is what gives us the dwindling spiral of abilities. RI's,
substitutions of ideas for thetans, the thetan's O/W's -- all these get piled
up on these fixed ideas. The biggest fixed idea was a goal, which then
developed into a GPM.

"That which is not inspected tends to persist," because it is never
as-ised. What happens? A person gets Hell knocked out of him. The RI and
its significance is the constant invitation to attack, but it is never the
right enemy. The constant O/W and battling that ensues from this fact
accumulates as the mass of an RI.

It is interesting that an idea is most easily substituted for a thetan
because it has no mass and seems to contain some wisdom. "I am a guard"
implies "I don't have to understand or inspect." The thetan has tried to
"solve" a screw-up with a fixed idea or postulate. This is a sort of
"sweeping under the rug" that permits no inspection, therefore no as-isness,
therefore persistence. Any idea is liable to become substituted for a thetan,
because he does it himself. When one gives up on one goal, one gets another.
For instance, say the last three or four mountain ranges the thetan built fell
down and fouled up his planet. So, on the ideal planet, "Never build
mountains" becomes the solution that holds all the confusion uninspected. It
is "solved" instead. Sooner or later, we will find him running a Society for
the Prevention of Building Mountains. He is now an identity. He is the idea,
"Never build mountains", substituted for a thetan. The PC keeps abandoning
old solutions as they fail, and keeps getting new goals. This is covered in
R3M, basically, except for finding the PC's own goal and distinguishing it
from implant goals.

So be alert to anything you find in R3SC that rocket reads, but don't run
it with service fac tech. You can't run a GPM with service fac tech, but you
can run one RI with it. But that rocket read is more than just a service
fac. R3SC does handle the RI that is part of the PC's PT environment.

If you find an RI, and your PC is having energy doing odd things to him,
giving ghastly sensations, body distortion sensations, etc., the PC is liable
to disclaim the RI in an effort to get away from it all. Getting towards the
service fac causes qualms and invalidation in a PC. The service fac is
"pro-survival", so he doesn't want to give it up. Don't Q and A with that
invalidation. To do so will just restimulate it worse. If the invalidation
occurs, pick up everything found as a service fac and finish it off
standardly, with all of the R3SC steps. When a stable datum is pulled out and
not run off completely, you leave some of the confusion behind. So just get
it with R3SC. If you take the stable datum half way out of a confusion, you
leave the confusion. This is what happens when you leave R3SC on something
half-run. The result is that the person will get foggy; his memory will
deteriorate. If you took the stable datum all the way out, you would blow the
confusion.

The postulate in the center of the RI is so far downscale that it is
twenty TA divisions below "hide". It is an idea that has turned into MEST.
You run it only as far as cognition, but it may enter at any of these levels:

1. Solutions.

2. Right/wrong.

3. Domination.

4. Survival.

But a real GPM item service fac goes through the steps of:

1. Solutions.

2. Right/wrong.

3. Domination.

4. Survival.

5. Domination.

6. Right/wrong.

Then the next:

1. Solutions.

2. Right/wrong.

3. Domination.

4. Survival.

Etc.

Again, the service fac may enter at any of these stages. It starts off
reasonably sensible, but becomes very weird, like "cows are kissable" as a
safe solution to "how to repair motor cars". This service fac will turn out
to be intimately related to "solution" or "domination", etc., in the PC's
mind. When you try to run it, the PC may not be able to fit it in on
"right/wrong", so check it over on the other buttons. He may well cognite on
it and blow the charge. You could then see how it is a solution, how it would
make or has made him right and others wrong, around and around on the buttons,
until the PC is out of answers and the buttons are clean. Do an 18-button
prepcheck, and it will all cool down.

The auditor is always in danger of grabbing the GPM accidentally, getting
the goal instead of the service fac. This has advantages too, since the PC's
goal is hard to sort out from implant goals. The PC's own RI's are probably
what make implant goals read. They read off the top of the PC's own RI's.
The service fac doesn't have to rocket read. You can accept one that does,
but be equally prepared to take one that just ticks.

The PC's service fac is his current solution, his current RI, monitored
by the goal. It is a very aberrated stable datum. It is an unexamined
solution that keeps the PC from doing anything. It was a decent solution when
the thetan first got hold of it, but then it started running his life.
Therefore, it does not even vaguely take care of environmental enturbulation.
[The rule: "When in doubt, communicate," is an attempt to overcome the effect
of service facs.]

You have to work at it to do R3SC wrong. The best way to do it wrong is
to be completely unthorough, to leave everything unflat. The PC will get very
confused, from having all his stable data pulled away. When you handle a
service fac, all the incomplete cycles that the service fac has caused hit the
PC at once. This generates confusion. When the service fac running is not
completed, the confusion gets even worse. So it is a good idea, from time to
time, to clean up what you have done. Get it all finished up. Some service
facs won't run quite in the order given for R3SC (see p. 509). It may start
on a later step than "right/wrong", or earlier, at "solutions". A real
service fac behaves outrageously, in that regard. Something else that isn't
a service fac may be far more mannerly, while still giving TA action.

Keep your eyes peeled for the PC's goal, since this is the best means of
finding it that we have developed. Keep running service facs until the case
is in good shape and the PC's goal has shown up. You get the best TA on the
PC's own GPM channel. You can use R3M2 when you get his goal, but that is not
your immediate purpose. R3SC is for destimulating the PT environment factor.