Страница 1 из 1


Добавлено: 14 июл 2012, 07:38
Web auditing at any place of the planet http://webauditing.org/




Many examples could be given which show how a case can be messed up by running unreading Dianetic items, wrong items or by going past erasure. Going past erasure will jump a guy into the chain of a BT or cluster who has been dead for a long time. BTs and clusters will unknowingly mock up the incident they're stuck in (or the incident the PreOT is intending them to mock up). Needless to say, this is not ideal. This is the bug one can run into on AAV.

The early steps of the rundown take up these possible errors, although at any point in the rundown when a PreOT bogs, the auditor should suspect that he's run into some more BPC on past auditing to be handled. It may be an obvious area of auditing or an auditor that the PreOT has brought up throughout his auditing, or it may require a reassessment of all the auditors the PreOT has had. Usually it is handled simply by asking the PreOT if "an error in earlier auditing has been restimulated?"

On the action of repairing past auditing, during the beginning program steps, interest is checked. The reason for this is that PreOT (or pc) interest is an indicator that charge is available and can and should be handled. By checking PreOT interest in the auditing action, the auditor can avoid over-repairing.

The steps for handling the repair of past auditing are:

A.What was being run?

B.What was the error (BPC) in the auditing? (or use the appropriate correction list to find it)

C.Indicate the by-passed charge.

D.Check to see if the BT or cluster that this was run on is still around (as it often will have blown by now), and if so, take the remaining steps to blow it.

E. Check for any copy.

You can also check for a "BT or cluster messed up in running_______?" (whatever type of auditing is being addressed.) Then complete steps B through E on what is found.

You can over-handle past auditing to the point that what you are correcting on one will start uncorrecting on another; that is, BTs will begin to copy errors they didn't have, hence the rule about going by PreOT interest and not continuing on past the point where the PreOT ceases to be interested in the action being done.

If, later during the rundown, it becomes evident that there is more BPC to be handled on past auditing, the auditor simply takes up that subject again.

If one runs into a bog in a session later on in the rundown, first check for any error in the current session and if that doesn't handle the trouble, then check for a restimulated error (or BPC) from an earlier session or earlier auditing and repair that using the steps above.

Although the above may sound like a lot of repair, it makes the auditor's job easier and more effective. These repair actions are usually very easy to do and quite spectacular in result.

David Mayo

Web auditing at any place of the planet http://webauditing.org/english.html