6310C16 SHSpec-313 The Itsa Maker Line

     The itsa-maker line is the line you are guiding as an auditor, which
sorts out the things in the case and gets the material that is reported to the
auditor as itsa.  The itsa occurs at the end of this line.  The line from the
PC to the auditor is the itsa communication line.  Itsa is the identification
of isness (or wasness).  It is a simple commodity.  Until an itsa is
recognized, it is only a potential itsa.  Auditors can make a mistake by
thinking that there is a potential itsa, where there is only a nothingness.
This is the commonest method by which an auditor refutes itsa.  The meter
version of it is cleaning a clean.  This is demanding more than the PC's got.
If you repeat the question, this makes the PC feel as though you haven't
accepted his itsa.  When you do this, in effect, you deny the itsa that you
have received.  You have cut the itsa comm line by refuting the itsa that was
offered.  You may think that the ARC break was caused by your cutting the comm
line, but it was really the invalidation of the PC's itsa that did it.  The
auditor is likely to try to cure this situation by asking whether he has
interrupted the PC.  That is also cleaning a clean, so the ARC break
intensifies.  You haven't interrupted the communication.  You have enforced
it; You have to keep in mind what you are trying to do, which is to get TA
action.  All the significance on the case will have to be handled at Level IV
anyway, so at Levels I, II, and III, what counts is TA action. [For a
description of these levels, see p. 462, above.  See also recent tape on Level
IV: pp. 524-526.  above.] Everything wrong with the PC, except how and why he
started to make a time track in the first place, comes out of his GPM's
anyway.

     Level IV is the scientologist's level.  The preceding levels mainly set
the PC up for Level IV.  "I don't think ... that anyone will make OT except a
trained auditor." A trained auditor's confront is up.  He knows what he is
dealing with. Etc.  Probably the basic barrier on the track, in mental
sciences, has been specializing in results without also trying to make
everyone into a pro, a causer.  PCs have been audited on Level IV in HGC's.
They have no understanding of what is occurring.  They ARC break easily.  They
don't have the confront.  Mainly, they aren't educated enough to understand
what is going on, so they get upset by reason of unknownnesses.

     There is only one way that GPM's can be run.  You must find and run the
PT GPM first, then keep going on down the track to prime postulate, then
repair.  You can't do it as you have been previously told to because you will
get items out of other GPM's.  You can't repair a GPM until you have gone
through the whole thing.  But you can't afford to make a single mistake,
because you will spend amazing amounts of time correcting it.

     You've got tremendous processes at Levels I, II, and III.  So you should
be able to sit down with a raw public PC and turn out 35 divisions of TA in
your first 2 1/2 hours, on any PC, anyplace.  If you can't do this, it is
because of lack of understanding of one of the basic points of auditing, like
the itsa-maker line.  You might have some wild idea about something basic.  It
might even be a scientology datum, magnified out of all proportion to its true
importance.  For instance, you may think, "PCs never answer the auditing
command," so you always get the itsa from the meter and leave the PC out, thus
destroying the itsa-maker line.  You and the meter can act as a "substitute
thetan", "perceiving" things in the bank that the PC isn't perceiving.  At
Level IV, the material is sub-itsa.  You have to depend on the meter at Level
IV, because the PC can't itsa what is in the GPM without some assistance.  The
auditor can undercut this with the meter and find out what the goal is,
because it rocket-reads.  But if we rely too much on the meter, we cut the
PC's itsa-maker line.  You still have to stay in comm with the PC and avoid
invalidating his itsa and cutting his itsa-maker line.  This doesn't mean that
you should be very careful.  It just means that you should know what you are
handling and how to handle it.  Get observant, so that you can tell when the
PC is introverted, when he has said all he wants to say, etc. "In session"
means:

     not only 1. Interested in own case,

     but also 2. With the itsa-maker line in on his case, not on the auditor,
                 but under the auditor's control.

     (The top of the GPM is hard to run; it is resistant to processing.)

     Since the itsa-maker line is invisible to the auditor, the auditor has to
"synthesize" what is going on.  The itsa-line is not a unit area
think-think-thinking.  It is an actual line between the thetan and a real
thing: the bank.

     An auditor who attracts or rapidly shifts the PC's attention to himself
has moved the itsa-maker line to himself, and it has become a whatsit:
"What's wrong with the auditor?", etc.  The itsa-maker is what makes TA
occur.  It is the PC's attention line.  An ARC break is caused by a sudden
shift of attention.

     You should be aware that perfection in the control of the PC's attention
and perfect handling of the itsa-maker line is impossible.  You will make a
couple of mistakes in this per session, even if you are an expert.  What
counts is how adroitly you can wriggle out of whatever you get into, not how
careful you are to stay out of trouble.  It helps to spot the birth of an ARC
break well in advance of its overt appearance.  An ARC break is much easier to
handle, early on, and you won't have audited over the out-rud.

     If, even implicitly. you give the PC an order to shut up and let you
write, the PC will do it and keep doing it.  PC's and the bank generally do
what the auditor apparently wants.  Non-verbal behavior may communicate an
auditor's desire to the PC.  Auditors' main goofs consist of giving apparent
orders that they aren't aware of and don't intend, like, "Stop inspecting your
bank and put your attention on the E-meter." This may occur when the auditor fiddles with the meter a lot.  Fumbling takes away the auditor's control of the
itsa-maker line by shifting the PC's attention to the auditor and the goof.
The bank always does what the auditor orders.  It takes a combination of the
auditor's orders and the PC's inspection to get the bank handled.  Randomity
will occur.  The auditor who is allergic to unforeseen circumstances would do
better to go to an old ladies' home.

     To get a bank inspected:

     1. The auditor must direct the itsa-maker line.

     2. The PC must put in the itsa-maker line.

     How does an auditor straighten these things out?  For one thing, he can
audit smoothly, getting good TA, so that he has a cushion [to use in working
with the PC].  Don't fix something when the PC is running well.  Something
that upsets you does not need to be handled, if the PC wasn't concerned, as
long as the itsa-maker line isn't affected.  In other words, don't repair a
nonexistent situation.  If you try to repair something that didn't upset the
PC, you are cleaning a clean, and you will get an ARC break.  Sometimes the
auditor gets conscience-stricken.  This should not be.  Remember that when you
ask a PC about something, you put his attention on it.  You can also put a PC
on a whatsit by being so conscientious that you are always looking for what is
wrong.  You should only repair auditing when auditing isn't occurring.  Case
repair is otherwise an interruption of auditing.

