Almost all the errors in an Interiorization Rundown are Dianetic errors. Most are very ordinary, even corny. It is vital to correct an Int RD error as a first action.

There is one Int Rd error that is not a purely Dianetic error and that is the error doing anything else at all before an Int Rd is done properly or an Int Rd error is fully corrected.

The Int R/D error may be simply that „went in“ and „go in“ did not read on the meter yet Int. was run. This classifies as „running an unreading item. “

Or the Int R/D could have been overrun. It goes flat on Secondary F2, let us say. The auditor keeps on going past the win. This will hang up the Rundown. One of the ways an overrun occurs is the pc goes exterior during it. Yet the auditor keeps on. Another way is pc has a big cog, big win, auditor keeps going on with the R/D.

When a pc is exteriorized by auditing and is then audited further without being given an Interiorization Rundown, his TA will go high or low and he may be very upset. Heavy masses may come in and he may also get ill. Int RD errors may also may go back to earlier Dianetic errors. A number of unflat Incidents invite the overrun of these if they also occur on a Dianetic Chain.

To clean up a balled-up Int RD chain or incident, one may have to find and clean up the Dianetic error it is sitting on during the clean up of the Int RD error.

Int R/D errors, goofs, etc. are handled by using an Int R/D Correction List Revised HCOB 29 Oct. 71.

Auditors who can’t run ordinary R3R with great success should not be let near an Interiorization RD as their lack of smoothness in handling Dianetics will wreck the Int RD.

An excellent Class IV HDC Auditor can easily repair a messed up Interiorization rundown after a folder study and by use of an Int R/D Correction List Revised HCOB 29 Oct 71.

A Class IV HDC Auditor with an excellent Dianetic record of wins can be given an Int RD to do or to correct if he is starrated on the ext pack and the two way comm pack.

Wherever you see a TA high and a PC in trouble, your first suspicions should be:

1. Audited past Ext in Auditing without and Int RD being done.

2. Int RD botched by being unnecessary (‘went in’ didn’t read) or overrun or Auditor goofs in the session.

3. A previously messed up Dianetic action has gotten fouled up with the Int RD.

4. The Int command was improperly cleared (such as “means go in and out again,” “means trapped,” “meant leaving,” etc.)

5. Firefights and worries over the high or low TA have ensued after an Int ball-up has occurred.

6. Some major action like grades or items or Power have been run twice.

7. A C/S has hopefully kept on getting the PC audited without detecting the real reason as a flubbed Int RD.

The percent of misrun Int RDs is high, many being unnecessary or overrun. The liability of leaving them unrepaired is high,

Reasons for high TA are averaging out close to 100% as an unrun or a flubbed and unrepaired Int RD.

When a pc Exteriorizes in session it is the End Phenomena for that process or action. One gently ends off in any case. Then if after the fact of going exterior in auditing, pc’s TA goes high, then you do an Int R/D. You test Int for a read, (test ‘went in’ and ‘go in’ per HCOB 24 Sept 71 Int R/D) and if it reads you do an Int R/D. You just don’t do one because a pc goes exterior.

Maybe it wasn’t needed. So if it wasn’t needed it will eventually have to be repaired.

If even years after an Int RD the pc has a high TA or a low TA then Int trouble is at once suspected and the original Int RD and any repair of it is suspect and must be handled.

The Int R/D Correction List Revised, HCOB 29 Oct 71, has been designed to straighten out Int R/Ds. L3B handles the Dianetic errors.

There is no real trick to either running a correct Int RD or repairing a flubbed one.

The whole clue is whether or not the auditor can audit plain ordinary garden variety R3R.

So when ANY auditor audits a pc past Exterior and the pc’s TA goes high he should be checked out fully on the Int RD checksheet so he won’t continue to commit the error.

And when anyone is going to run an Int RD he must:

1. Be an expert Dianetic Auditor and Class IV.

2. Be starrated on all the Int RD pack.

And when any C/S is confronted with high TAs or low TAs and doesn’t handle at once by getting an Int RD properly run or properly repaired he must be re-checked on the Dianetics Pack and the Int RD pack.

A very careful Dianetic C/S-1 must be done on a previously unindoctrinated pc before he is run on an Int RD.

Otherwise it’s all too new.

A CS-1 isn’t auditing.

The pc who can’t do what the auditor says or can’t correct an erroneous action is lost.

A fully safe pc would be one who when he goes Ext in Auditing is made to do an HDC at once before he even gets any ruds put in and not audited again until he is an HDC. He’d be a pc who was relatively safe.

A pc who does what an inexpert auditor says without question can really get fouled up. Uneducated PCs require really flawless top notch auditors. The auditor who can audit an uneducated pc is a jewel. He really has to know his business. Because the pc does whatever he says. And if he says wrongly, then there goes the session.

Ever notice pc corrections in a worksheet? „I think you by-passed an F/N. “ „This feels overrun. “ „I had Grade 1 last year. “ Such auditors are not fully enough trained to handle wholly green PCs.

Honest fellows, it’s as easy to run an Int RD as it is to run „an ear pain. “

It isn’t even mysterious or tough.

It is only very important to detect when it needs to be done or repaired.

There are no mysteries.

Some auditors have got me feeling like I’m trying to teach them to chew soft bread!