6108C11 SHSpec-38  Basics of Auditing -- Matter of Factness

     A lot of auditors are doing something besides auditing:  they are
pressing through, introducing something in an effort of make auditing work.
Probably it's because of LRH saying that the auditor has to make the auditing
work, that he should be on the ball, etc.  A certain apathy about results
creates in itself a "grind atmosphere".  Desperation or apathy alike are
counter-productive.  LRH audits with no doubt about what he's doing, no
withdraw, no question about purpose.  His auditing is very matter-of-fact
because he has no doubt that he can help the PC, no doubt about the
effectiveness of the process he's going to run, no doubt about the fact that
the process is working, so he has a relaxedness about auditing that gives him
results five times as fast because he doesn't get in his own road.

     The reason an auditor doesn't flatten a process is anxiety to get the job
done, which gets in the way of getting the job done.  LRH doesn't
artificialize the way he feels about the PC; he keeps it real, unlike other
auditors, whom he heard being stilted and artificial.  Be effective; help the
PC; don't be hidebound.  This should give faster results more easily.

     Not-know and forget would have run out engrams in 1950 if they had been
used then.  This would have avoided a lot of grinding and sweat.  You'd use a
command form which includes as many dynamics as necessary, e.g.  "What should
remain unknown about this to the public / the government / a family / your
superiors, etc.?" The occlusions that auditors were struggling with were the
result of self-motivated efforts to withhold.  The hang-ups in any engrams are
from a desire to make these things [parts of the engram] unknown or
forgotten.  The pretense of knowing about it (dub-in) also blows on the
not-know processing.  Running engrams should not be discounted as of benefit
to the case.  If you get someone clear and stable, they may still find
themselves with an engram there.  It won't take long to run it, since he's
clear.  During stabilization, they're unsnarling track; they are still bumping
into things which can be run.  Using not-know on it makes it run even faster,
since it pops the sticky point into view.

                 [Application of not-know to Goals processing]