More Data on Int
Out-int is a remedy - not
Int Handling Is a Remedy
There may exist a number of false ideas about what the Int handling is designed to do. Let us spell it out: It is a remedy for pc's after having gone exterior. It handles any charge in connection with this and permits the pc to be audited further. Out-Int leads to a number of symptoms and discomforts. To try to handle anything else on a pc with Out-Int than that is actually very hard on pc's and harmful to their case. Out-Int is the heaviest 'Out Rud' condition on a case and needs to be checked out and handled when suspected. All manner of physical and mental discomforts can result.
The list of symptoms are: Headaches, odd body aches and pains. Effort, Pressures from environment. It can also be unwillingness to go into things, down to a physical back-off (claustrophobia). An urge to leave can also sometimes be traced back to Out-Int. The main symptom is high TA at session start or TA up at Examiner after EP at session end. Not all Out-Int cases suffer from high TA, but all who have high TA after lots of auditing should first of all be checked for audited past exterior.
you see it is a quite an impressive list of things that need urgent attention.
To audit a pc over Out-Int will cause him to get more stuck in this charge by
plowing in. If the auditor suspects the pc went exterior and now displays any of
these symptoms he should check for Out-Int. If that is the case that is the
first and only action that should be handled next. If it proves to be uncharged
he can safely go on with whatever program he was doing.
On the other hand, it must be understood that the Engrams Int RD or Recall Int RD are not actions that exteriorizes the pc or is run to cure headaches or claustrophobia. It has only one technical function: to deal with the charge of Out-Int. It may hold the key to many benefits and great wins for the pc, but it is only delivered as a remedy when it has been found that the pc has charge on the subject of Int per C/S 53 and other correction lists. To try to use it for anything else will result in auditing an uncharged subject and no gains for the pc.
Out-Int and Blows
We saw at Level 2 that Overts and Withholds is a primary factor behind leaving an area in a hurry or unexpectedly. It was discussed as an urge to leave. But the fact is that many people may have Overts and Withholds and not blow. Some people have minimal or no Overts and Withholds and blow anyway.
But we also touched on another cause, Out-Int. A case audited past exterior tends to get stuck in exteriorizing. This can especially be seen when the condition isn't acknowledged. This can cause the dramatization, that the person takes himself away. They feel uncomfortable from the symptoms of Out-Int (headaches, etc.). Failing to get out of their bodies they dramatize the action and leave the area instead. You can see people in need of an Int handling and getting one, change their minds on this point when handled. The dramatization simply lost its basic motivation and ceased. You can hear all kinds of excuses, enough to fill books. But what they are really trying to do is to "exteriorize" by leaving. Once the Out-Int is handled this dramatization and urge to leave will stop.
Complete on an Intensive Basis
Since Out-Int is the worst 'Out Rud' and the number one thing to handle of 'the worst tangle' no other auditing can be delivered until it is handled. As a result of this there has to be a certain level of discipline present when delivering it. Ideally the whole RD would be delivered in one session and one follow-up session (the one-week rule). But this is of course not always possible to predict or do. Therefore the rule is, that you make sure the pc and auditor have plenty of time for the first session of the RD and have plenty of time available to do daily sessions after that until it is complete. You want to complete it on an intensive basis to avoid the out ruds of daily life to become a problem and also simply to handle the charge completely once you get started on taking it apart.
Another thing related to this is, that you complete a button until you have an F/Ning Assessment on the flows in one session. You do not run Flow 1 and then end off. You end off by assessing the flows for one button and finding them F/Ning. Also due to the serious out rud situation you are handling, it is important that the auditor has smooth TRs and accurate metering. Rough TRs and taking up non reading items or not finding the reading ones quickly are all a lot tougher on a pc with Out-Int than under normal circumstances.
Word clearing and clearing commands are held to an absolute minimum due to the Out-Int situation. For most pc's they will have cleared the buttons as part of earlier auditing. But you do it this way: You assess the actual Int buttons without clearing them. You take up the one with the largest read. You ask the pc what the button means. You have to make sure of two things. (1) That the read you got was not due to an MU or a false or protest read. You can check the buttons Misunderstood, False, Protest if you suspect an invalid read. You must ensure you have a valid read before taking it up. (2) Auditor also has to ensure, that the pc understands it is the action of Going In (in one form or the other per the buttons) and not simply being in, which does not contain a motion or action. If the pc understands it this last way it won't run the charge out.
The EP of the Int handling is not going exterior. If that happens the auditor of course acknowledges it as a big win and ends off that session. But he is not done yet. The EP is "No trouble with going into things". This should be achieved, when the Int buttons F/N's when assessed. This is described in the RD itself and elsewhere in the previous chapter. Let us just once more point out another way this comes about. If the auditor suddenly sees a big BD which goes into a wide F/N or a Floating TA, it means the stuck flow of 'Going into things' has become unstuck completely and blown. The auditor lets the pc have his win and ends off gently without giving another auditing command. That is quite a spectacular and sudden EP which must be recognized and respected.
The two biggest errors in doing Int handlings are:
1) Running anything else when the Out-Int is the problem or not fully handled.
2) Overrunning the EP of the action or running unreading items on the RD.
It is not a difficult action to do, but it has to be done right the first time as any errors are tough on a pc sitting in this type of charge.