I hasten to give you advanced information on Routine 3D Commands and use.

Do not be discouraged on 3D. The routine behaves in a most disconcerting way after Steps 1 to 5 are completed.

The preclear should experience an enormous case gain just by reason of assessment. However, the Tone Arm may, by assessment end, be reading higher than usual or the needle stickier than usual. Don’t let this worry you as long as you’re sure Ruds are in. You have, by assessment, brought into view the Goal Problem Mass.

If the pc has never had any mental masses before, he will have them now.

The goal has been baulked for eons by opposing forces. The goal pointed one way, the opposing forces point exactly opposite and against it.

If you took two fire hoses and pointed them at each other, their streams would not reach each other’s nozzles, but would splatter against one another in mid air. If this splatter were to hang there, it would be a ball of messed up water.

Call Hose A the force the pc has used to execute his goal. Call Hose B the force other dynamics have used to oppose that goal. Where these two forces have perpetually met, a mental mass is created.

This is the picture of any problem — force opposing force with resultant mass.

Where the pc’s goal meets constant opposition, you have in the reactive mind, the resultant mass caused by the two forces — goal=force of getting it done, opposition= force opposing it getting done.

This is the Goal Problem Mass. When contacted it raises the Tone Arm and sticks the needle.

In Routine 3 you did not run head on into this mass. You pushed around, more or less hit or miss, and may have keyed it out (on which you would have made a first dynamic clear) or you may have run into it and not keyed it out or erased it (at which time the case would have bungled along until it did key out).

In Routine 3D, the Goal Problem Mass is thrown into view in the assessment itself. The running of the case keeps banging away at the Goal Problem Mass.

In Routine 3D, the Goal Problem Mass is erased, not keyed out.

In assessment, the relief afforded the case by discovery of the items of the Goal Problem Mass tends to keep the Tone Arm more or less down most of the time, even though assessment heads the pc more and more at the mass.

You may not be aware of this until you start to run your first Pre-Hav level. And then you may not get more than two or three commands in before the Tone Arm rises and sticks.

In any event, finish the bracket. By that time you will be sure the arm is stuck. The needle may still twitch in the pattern of the 3D Items. Ignore it. Except for that the needle too will look stuck.

Reassess the G + M terminal on the Pre-Hav Scale (never assess an opposition terminal) and form another bracket.

Once more stick the arm. It may go more or less commands than the earlier level. In any event the arm will shortly stick, the needle freeze and only the twitch characteristic of the level or the goal will be seen.

Reassess the G + M terminal on the Pre-Hav Scale. Once more form a bracket. Once more run it. And once more stick the Tone Arm and needle as above.

Continue to do this level by level. You will find pc’s Tone Arm goes high and sticks. This is the Goals Problem Mass doing this. It is one of the bogs of the reactive bank. However, on subsequent runs you will notice that the pc’s needle loosens faster after a level is finished and that the TA comes down quicker and lower after the level is flattened (even though the level appeared to stick it very hard indeed).

Eventually the G + M terminal is flat and levels if found produce neither a TA stick nor Tone Arm action.

Using the goal again, assess for a new 2, 3, 4 and 5 for that goal and try to run the result on the Pre-Hav Scale.

It is important to complete any 3D assessment started.

Get all 3D items. If you can find opposition terminals that react, you can find all subsequent items even if they are reacting minutely, for a Goals Problem Mass exists.

Assess on the Pre-Hav and run any item found just as above, no matter how minute the reactions are, level by level.

When you can no longer find even minutely active opposition terminals for the goal, with meter sensitivity at 16, assess for a new goal and repeat the whole procedure as above.

Do not be fooled into thinking that as there is a tiny reaction on a goal it can be left. Any reaction left must be run into a complete 3D, all steps.

The by-word in 3D is once started, complete it all on all items.

Also, there is no other process known that runs on the Auxiliary Pre-Have 3D Scale (HCO Bulletin of 23 Nov ‘61 or as amended) that will free a Goals Problem Mass.

The task of assessment is to get the rudiments in, keep them in and make sure the pc is in session before assessing anything (or later, running anything).

Out rudiments stem from:

1. Withholds.
2. Present Time Problems.
3. Invalidation of Items.
4. Slow Assessment.
5. Distrust of Auditor.

All in that order of importance.

An ARC breaky pc is best handled by flattening Routine 1A (or as amended) complete with Sec Checks, before a 3D is attempted. This handles (I) Withholds and (2) Present Time Problems. It also handles to some extent (5) Distrust of Auditor.

In actuality the items, 3, 4 & 5 are dependent upon the auditor doing a fast, expert job of listing and assessing by elimination.

In assessing, the less chat with the pc the better. You want the lists. In goals and other items you want the discreditable ones by meter. In goals listing you want the withheld, anti-social, secret goals by meter. In others you want the “unseemly” or “discreditable” items by meter.

Once you’ve got a complete list by meter, that’s the list. You don’t add to it every time you cover it. You add, of course, things the pc asks you to add when he asks you, but always at the bottom of the list.

You always add to lists, using the oldest known list. You don’t make brand-new lists, discarding the old.

If rudiments out have killed all reads (the whole list nuls) you cover the whole list again, every item, when you’ve got the rudiments in again. Because a list nuls does not mean the wanted item isn’t on it. It means the rudiments were out. Get them in by Sec Checks and various means and do all items on the list newly as though never before nulled.

You can copy lists. You never discard them.

Keep present time or present life names off opposition terminals lists. They foul up the reading.

When you assess, do so briskly, saying the item three times, acknowledging the pc, saying if it’s in or out, marking it and going on to the next. You should be able to do 400 items per hour, new or old. It takes about 8 seconds to cover an item.

During nulling a pc should be made to sit back, relax and be silent. He can originate new additions. If he does, add them to list end, ack and go rapidly on. Don’t ask pc what he’s thinking about or looking at during assessment. An attitude of relaxed irresponsibility should be cultivated in the pc during nulling.

The target of the auditor is the pc’s Reactive Mind.

Once a list is made and complete by Meter, the auditor has the meter, himself and the reactive bank of the pc. That’s all he or she works with. Don’t ask any help from the pc. Never ask him for the answer. That makes him “help” and wrecks the nulling. The pc who has been brought by inexpertness to “help” is put on a self-audit of anxiety and the whole operation goes to pieces.

In “bleeding the meter” for more items on a list, beware of mistaking a reaction denoting ARC Break for more items present. Check by eliminating out all ARC Breaks.

Remember that when a pc has an ARC Break he is out of auditor control and an ARC Break question does not always react because the “rudiments are out”. To be sure you have to vary the ARC Break question. To be very sure, run a few ARC Break process commands varied to “Have you been unable to tell me something” and see if these react on the meter.

When a heavy ARC Break is present, the meter can remain inactive until the ARC Break is out. An ARC Break is the only rudiment that can be undetectable on the meter, as then the pc is totally undetectable to the auditor who is auditing him or her. Hence, nul rudiments, nul lists.

Best detection method for an ARC Break is to talk with the pc in a friendly way for a moment. Friendliness is greeted by friendliness, easy and unfeigned = no ARC Break. Friendliness greeted by no answer = ARC Break.

Pc not setting goals for session denotes heavy ARC Break. It will be heavy enough to nul the whole meter.

This is the only real frailty of an E-Meter. But it’s humanly detectable. Other 3D items are not humanly or spiritually detectable by any means other than a good meter. Telepathy and intuition used to locate 3D items are disastrous! Use the meter!

In end rudiments, for all sessions of assessment, or that had any session or level to be found, always add “Have you done anything to influence the E-Meter?” And clean it. Pcs, even Scientologists, try to throw assessments and sell items.

If you buy what the pc thinks it is, you’re sunk. So’s the pc. If you purchase sells done by finger flicks, etc, the pc is sunk indeed. 100 hours of wasted auditing has been traced to this on one pc.

25% of pcs will do “selling” by efforts to influence the meter, and wreck a 3D assessment in an effort to “help”.

Short session restive pcs. 2 sessions in 2 hours gives you 4 cracks at rudiments!

If you’re going to run 1A or Sec Checks or Problems Intensives on a pc, do it before you start Routine 3D. Only Sec Check when a 3D is in progress and before you start running levels.

A Sec Check question that always works when ordinary questions fail is “What have you done that______doesn’t know about?” And use various known proper names involved with the pc. This runs on any pc. Don’t abuse it. It’s the last shot in the locker.

The Auxiliary Pre-Have Scale (HCO Bulletin 23 Nov ‘61 or as amended) is the correct 3D list of levels.

This is assessed by reading each item only once to the pc and reversing flows, terminal to pc, pc to terminal. Several levels can be called off on one flow without mentioning the terminal except on the first level of that flow.

Cover the whole list, one read each level. Use a symbol on each level that reacted.

Go back up the list on only those levels that did react, reading levels only once each

time. Come back down, reading only those that reacted the second read, etc, until only one level is left.

Let the pc have his own Aux Scale in his folder. Note the level symbols and date on it each time it’s used. Use different symbols each time you use it.

The Model Command (and the only one used for 3D) is:

Always use MIGHT in Commands. Example: Pc’s Terminal — Waterbuck.

Opposition Terminal — Tiger. Level — Interest.

Commands:

How might you interest a Waterbuck? How might a Waterbuck interest you? How might a Waterbuck interest a Tiger? How might a Tiger interest a Waterbuck? How might a Waterbuck interest self?

In running 3D commands be as careful to get your rudiments in as if you were assessing.

1. If an auditor can’t assess accurately and quickly the obvious auditing error is that he or she can’t read an E-Meter fully. Bad or slow assessments are best countered by (a) Getting the auditor the know-how to read a Meter and stop covering up his or her ignorance and (b) Getting the auditor through 3D on his or her own case.
2. The pc’s goal and the opposition goal, taken together, look like a problem to anybody. The pc’s terminal and the opposition terminal taken together look like a conflict.
3. Never suggest a 3D item to a pc or lead him by suggestion into one. Let the meter, listing and assessment find it. An auditor who suggests is covering up an inability to read a meter with confidence or is dramatizing.
4. Always complete a full 3D on anything you start, even when the needle is floating too free to be read. This applies to clears, half clears, new people, late in clearing and always. Complete a 3D in all sections. Always complete all 3D actions on any item that has been started on 3D, particularly past goals from Routine 3.
5. Don’t take clearing for granted. Only when you, the auditor, have assessed and run out everything you can think of and have been unable to find any further way to halt a floating needle, should you state you’ve cleared someone and only then when you have watched the Life and Livingness activity of the case for three months after the end of auditing.
6. Until an auditor can do a perfect Class II auditing job, he or she should not attempt a 3D. All the skills needed in 3D are to be found in Class II activities — Sec Checking, rudiments, a Problems Intensive. When an auditor can do these flawlessly, it’s time to permit him or her to run 3D. Yank a certificate if you find an unqualified auditor using Routine 3D. He’ll kill somebody.
7. Always get a 3D item (sections 1, 2, 3, 4, 5) (except Pre-Hav levels) checked by another skilled auditor.
8. The moment you find the Pre-Hav Scale getting more items alive on any one assessment than it did on the previous assessment, scrap the run. Go back and complete everything from section 1 forward. There’s an error of magnitude. Example: In assessing Interest, 10 other levels were alive. Next assessment, Withdraw, finds 38 levels alive. Wrong 3D Assessment or pc self-auditing on other terminals at home. If not latter, scrap the run.

In doing 3D keep a pc’s papers all in one folder. Don’t be sloppy about it.

Keep the goals lists, Sec Checks, all 3D lists, a 3D form for the pc (filled in) and a Pre-Hav Scale for this pc only and auditor’s reports and check sheets all together.

To lose a pc’s records, not to make a proper clean copy of the goals list all in the pc’s own words, to fail to keep the pc’s 3D form or forms filled in to date, failure to keep all added assessment sheets, can result in a case ball-up of magnitude. You need these things.

The pc’s own Pre-Hav and Have Scales must be marked in so anyone can tell if more levels came alive on subsequent runs.

One can’t straighten out a pc’s 3D run case without records. We have to do it on elsewhere assessed pcs all the time. (We have yet to find a correct assessment on Routine 3 here at Sthil where the pc was assessed elsewhere.)

Further, in filling out auditor’s reports, use correct terminology. Don’t call the Opposition Goal “The goal” or the Opposition Terminal “The terminal”. Shorthand it if you wish, but so it can be understood. Opp goal, Opp term, Pc’s Goal, Mod, G + M, are all valid symbols. Call an Opp goal a “goal” and a case reviewer can’t figure out what you were doing.

Keep good records. It will save the cases of a lot of pcs even if they’re mis-run.

And you yourself will need them to run 3D.