Stuck Picture Handling

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.

Handling of Stuck Picture
on Pre-OT III

The following data are from some research Ron Hubbard did on Engram running in 1968. It is another way to handle Buttons when Incident Two or Incident One won't run on an entity.

A picture is stuck because of:

(a) An effort to withdraw from it or something in it.
(b) An effort to stop or stop something in it.
(c) A stop-withdraw combination.
(d) An effort to suppress the picture or something in it.
(e) An effort to invalidate the picture or something in it.
(f) A protest against the picture or its content.
(g) An effort to hold on to the picture.
(h) An ARC Break about the picture.
(i) A Present Time Problem about the picture.
(J) An overt picture of which the stuck one is the motivator.
(k) Too late on the chain of similar pictures.

One first checks the above Buttons for read on the BT/CL in question. If the Button is found charged, one "runs the BT/CL through the incident with the Button", i.e. projects the incident with the concept of the Button at the same time.

You never simply force a BT/CL through an Engram (such as Inc 2 or Inc 1). This would be an invalidation and is against the Auditor's Code. But you can make it possible for the BT/CL to go through the incident without using force or pressure by using this method.

The above method can also be used if the incident hangs up in one portion. Find out what Button is out and project the BT/CL though that part using the above method. If you hit a new snag the assessment and procedure can be repeated.

(h), (i) and (J) would be handled as an out rudiment before proceding. (k) would be handled by finding the earlier beginning or earlier incident and run it normally.