The  Prometheus Reports

Warning: These materials are only to be read and used by students ready for the Level. To qualify you have to have attested Clear and done Advanced Level 2, Pre-OT Two. The student should also be a trained Solo-auditor.

3. Get its Inc 2 data. a. Area? b. Volcano?

4. Run Inc 2 per Platen. 'Explosion to Pilot'.

5. Locate and run Inc 1 per Platen:
     a.    BT: Run its Inc 1 to blow. 
     b.  Broken up CL: Handle each remaining BT from that CL with Inc 1 to blow. Copies.

6. Each BT is taken to blow - optional steps may be needed.

7. Find next BT or Cluster and run it through the steps to its EP.

1. Locate BT or Cluster by Meter read or area of pressure
First you have to locate a BT or Cluster to run. With your attention you scan over your body. This could be done with closed eyes except you want to keep an eye on the Meter. Of primary interest is pressure areas in or on the body. A pressure somatic is one indicator of a Cluster in the area. The area may not read at first but if you can find the Cluster or Clusters they probably will.

2. Intend it to the date of Inc 2. Once a BT or Cluster is located by pinpointed intention it is intended to its Incident Two, approximately 75 million years ago. It is important for the Solo-auditor to be able to concentrate his attention and intention narrowly on that one BT/Cluster as to not stir up others too quickly but enable the Solo-auditor to finish one auditing cycle on one BT/CL at the time.

3. Get its Incident Two data. 

a. Area? b. Volcano?
This is two questions: What's the area? (answer) What's the volcano? (answer). It's done quickly and lightly. It is not done by assessing the Volcano Platen or anything like that; it's usually very quick.

You find what area the BT/Cluster was brought to on Earth and what volcano it was 'exploded' at. Only use the Volcano Platen as needed. Just find the 'where'. Don't run anything at this point. 

Area: there were 2 areas of assembly (BTs assembled into Clusters) after the Thetan was implanted. Thetans of volcanoes in Asia and the Pacific were taken to Hawaii. Thetans of Atlantic areas were taken to Las Palmas on The Canary Islands. So first you find the area (Asia-Pacific of Atlantic), then the specific volcano.

4. Run Incident Two per Platen. The BT/Cluster is sent through from the explosion in Incident Two to 'The Pilot', the point where the Pilot says he (the BT/CL) is mocking it up. 

The content of the Incident per Platen is run on the BT/CL (i.e. it's as if the Pre-OT is projecting the Incident at the BT while kind of pulling the BT through the incident; it is not the same as running Dianetics™, where one tells the pc to move through the incident). You do not audit the BT like any PC being run on Dianetics™. At this point what exactly is run on the BT is Explosion (not the beginning of the incident) to Pilot only. You note the reads as he goes through the incident, and basically run it until it is flat, maybe a few passes. Note the reads each time so the C/S can see what's going on. Especially Clusters may need a few passes through. 
If it is a Cluster it should result in a break-up into BTs. It may result in a blow F/N when a single BT is taken through; when running a Cluster it may result in some blows of individual BTs from that Cluster. 

If it doesn't run at all, you use the methods listed in step 6 below. You find the specific reason for that Incident Two won't run properly and handle it per instructions. The EP you are going for is a flat Incident Two on a BT; and a break-up if it is a Cluster.

5. Locate and run Incident One per Platen.
Once Incident Two is EPed per above, you go on to Incident One. 

a. BT: Run its Incident One to blow. 
If the BT didn't blow as a result of running Incident Two it is taken 'earlier similar' to the very first incident that BT had in the MEST universe, Incident One. (Each BT has its own Incident One - it's not a "Big Bang"). This is audited the same way as Incident Two, but of course intending the BT to the date of Incident One at approximately 4 quadrillion years ago and then using the Incident One Platen. It should result in a blow of the BT and that's it for that BT.

b. Broken up Clusters: Handle each remaining BT from that Cluster with Incident One to blow.
You make sure all the individual BTs from a Cluster are handled by looking over the immediate area in your personal space and picking up any single BT still remaining. You can check "Any single BT from that CL remaining?". You are not looking for new BTs but simply for remaining BTs from the Incident Two running. Each Individual BT is sent to its Incident One and sent through that Incident.

When all the individual BTs are handled you check "Copies?" and spot the fact if anyone copied it. This is the final clean-up for that Cluster.
When all individual BTs are blown to F/N on Incident One and copies are handled you are done with that auditing cycle. 

Each BT is taken to blow - optional steps may be needed.

6. Optional Steps - Handling BTs that didn't blow on 1-5

Troubles Running Incident Two
There are three common reasons a Pre-OT might run into trouble while running BTs on Incident Two:

1. It is the wrong area.
2. It is not the volcano of the BT being run.
3. It is not an Incident Two but another incident of a different date.

'Wrong area' means the BT has been given Asia-Pacific or Atlantic as the area he was dumped and implanted at in error. It's a session error. (See Volcano List).

Check (1) and (2) if you are having any difficulty in running Incident Two and handle by locating the correct area or finding the volcano of the BT being run.

(3) If it is not an Incident Two, simply check for the date and if different, run it using D/L Cluster Handling.

Free-wheeling
In case of free-wheeling - where the BT gets whirled through its Incident Two out of control - you handle it by finding the exact beginning of its Incident Two.
Additional data are contained in the chapter "Sequences of Incident Two".
You have to establish "the earlier beginning" and run the incident from that point in time and to 'The Pilot'.
You check: "Where does your Inc 2 start, Capture or Explosion?" first of all.

Using Buttons
The BT or Cluster may have some reaction to the incident you are trying to run (Inc 2 or Inc 1). It is a reaction from when the Thetan first received the incident; it can be restimulated in the session. If what you perceive from the Thetan is a stuck picture or some kind of non-confront it is very likely that one of the Buttons will handle. This is done by checking these Buttons on the BT/Cluster and let the BT/CL itsa on what you find. Once the Thetan is unstuck, that's it, of course. You go back to your normal procedure.

Here is how one puts in the Button, 'Effort to Stop'. "Effort to stop?" (read). BT itsas briefly, conceptually; recheck Button, "effort to stop?" (read). More itsa; recheck Button, etc. You have to listen to the BT. When no more reads and no more itsa, you can run the incident (i.e. project it at the BT) again. Here is the list of Buttons:

EFFORT TO STOP. The BT/Cluster may try to prevent the running of the incident by trying to stop it. Check "Effort to Stop?" and handle per above if it reads and the incident will fly.

EFFORT TO WITHDRAW. Is a similar Button. The incident is hung up in a vacuum but is unleashed the moment the Button is correctly put in.

STOP and WITHDRAW can be found as a combination and this combination can be checked as a Button and handled per above.

Other Buttons to check are: RUSHED, PROTESTED, NOT-IS-ED and SUPPRESSED.

"Stuck Picture"
Another procedure for handling Buttons is "Handling of Stuck Picture on Pre-OT III" where you find the charged Button and "run through the incident with the Button", i.e. project the incident with the concept of the Button at the same time. This is fully described in its own write-up. This method is especially applicable if you encounter BT back-off half way through an incident.

No Blow on Incident One
There are five reasons a BT fails to blow on Incident One:

1. Earlier Incident One (see below).
2. Earlier universe (see below).
3. It's a copy (another BT is copying the incident just run).
4. Incident Two needs to be run (cross-auditing; you jumped from one BT to another).
5. Auditor is trying to run a Cluster with an Incident One. 
(Other type of incident made it a Cluster - see Cumulative Cluster below).

Earlier Incident One. You may successfully run a BT through Incident One and yet it doesn't blow. First, send the BT through the Incident once more. If still no blow after several passes, check with the BT if there was "an earlier Incident One?" and if positive, run that incident now. This should then result in a blow but beware of that there are instances where the BT had several earlier Incident Ones and until you have found the first one you have not found the basic. 
(Note: we assume that such Being entered the MEST universe several times and was "greeted' with an Incident One welcome each time. Editor.)

Earlier Universe. Additionally, in some few cases, running earlier Incident Ones does not result in a blow. The BT may be stuck in an earlier universe (earlier than the MEST universe). Ask: "Earlier universe?" and if it is the case it results in a read and the Being blows when indicated. You just indicate and nothing else. Don't try to run it.

Handling Copies. Another phenomenon that can be a little confusing to the green Solo-auditor is copies. Other BTs and Clusters in the area can obsessively copy the incident just run and it can appear that the original BT/Cluster is still there. A copy of the incident/picture is what is there. This can be checked on the Meter. You ask (silently): "Copies?" and indicate, "spot the fact that somebody else copied it" to destimulate it but do not take it further nor try to find out who did so. You want to complete one auditing cycle on one BT or Cluster at the time. 

Cross Auditing. Another reason a Pre-OT can accumulate by-passed charge while running the regular procedure is cross auditing. It is relatively simple to handle once the Pre-OT recognizes what it is.
When one runs the Incident Two of one Thetan and then an Incident One of another it is not going to result in a blow of the first one but will instead leave by-passed charge in place. The first one will have BPC and may start to freewheel through its Incident Two. This can actually lead to the Pre-OT feeling ill or getting ill as illness is part of the content of R6. It can also lead to no desire to go on with auditing (a sure indicator of BPC).

Should any of these symptoms be present in an auditing session or after one the Solo-auditor should suspect cross auditing and check for BTs "run on their Incident Two but not on Incident One". Or "BT run on Incident Two but not blown". Any such BT should be picked up and taken to the EP of blow by running its Incident One. 
Should this not handle the situation the Solo-auditor would do a formal correction list (such as Green Green Form). This can be done Solo by a skilled Solo-auditor or by another qualified Auditor in a review session. In review a LDN can be done to sort out any by-passed charge as well.

Other Techniques Used
There are however a few exceptions to this basic approach of running Incident Two and Incident One to produce the desired blows. The Solo-auditor therefore needs techniques to handle any such situation.

Cumulative Clusters
Severe incidents, usually with impact, can produce Clusters in their own right. Incident Two is of course an incident that produced Clusters but a variety of other Engrams can as well.

If a Cluster does not respond to running Incident Two, suspect it was another type of engramic experience and handle with the Date/Locate of that Cluster-forming experience. Again, when a break-up has been accomplished with Date/Locate, individual BTs from that Cluster that are still there should be handled with running Incident Two (if feasible) and Incident One (always) on each. See next chapter for exact steps.

Incident Two can sometimes form gigantic Clusters with 8-18 BTs in them (or more). The Cluster was "packaged" at one of the assembly areas (Hawaii or Las Palmas). They may have different parts of Incident Two and its 36 days of Implants in their Banks. This is not that important in practice. You run them on Incident Two - from explosion and to the point in the incident where the Pilot appears. This is found to be sufficient to destimulate all of Incident Two. Any individual BTs still there are then handled by running their Incident One.

Out Rudiments. You may find BTs that are ARC broken, either by the incident or by rough auditing. You may find they have other rudiments out. This can be checked on the Meter and it is handled per the chapter of flying ruds in this manual. When their ruds are in you handle per above instructions.

7. Find next BT or Cluster. When you successfully have EPed the BT or Cluster you audited you find the next one to audit. You locate another BT/Cluster per Step 1 and handle it with the same steps to its EP. You keep this up session after session until completely done.

There are literally hundreds of BTs and Clusters that have to be audited on Advanced Level Three. If the Solo-auditor finds 'no BTs/Clusters to audit' it usually means the Pre-OT wasn't fully ready for the Level and the C/S will have to get to work to find out exactly what is going on and remedy it before sending the Pre-OT back to Solo-auditing.

Any human Being on this planet is loaded with BTs and Clusters. A large portion of these will blow as a result of general auditing and before this Level. There have been no cases where they somehow were all blown. You could say they are part of the air we breathe here on Earth. It may be a little spooky to read this. Most of these BTs are very benign and just in poor shape. To get all this handled is what is meant by auditing out the Fourth Dynamic Engram. The effects of this is not just first Dynamic gains; it's a better world and more hope for the future of this planet.

© Prometheus International, 2004. Plus fair use quotes from Ron Hubbard's published notes and works.