The moment of blankness
November 19, 2012
From post to DianeticR3X Yahoo group
When running an incident that is heavily charged I will invariably run across a blank moment. It may show up when running the moment of shock, but if it does, by then it becomes a new incident in itself within the incident and needs to be opened up from the beginning again. It's of course not a truly new incident, but it is treated as if it were.
This blank moment is actually the unconscious period that every engram contains. Every engram can be counted on to have force and blankness which corresponds to pain and unconsciousness. So if the incident the PC is running does not contain these then it isn't really an engram. It may be a secondary or lock, but it's not an Engram.
So when I'm running a PC on a heavily charged incident, I will normally question that person about the transition period between when he was feeling like himself or good at the beginning of the incident and when he started feeling worse after the incident. I will do this some time around the running of the "hidden" or "force" buttons. I normally refer to that as the blank period to the PC it may seem like blackness or overwhelm or any of a number of words that would describe that particular traumatic period.
The reason I do this is to ferret out all of the hidden aspects of the incident, leaving no mystery behind. I want to know all the details, like what was the mechanism of the implant device like, • what type of force was used during the implanting, • what were the implant commands, • what postulates were made, • How many beings were involved in the implanting, • who was the beingness behind the implant and keeping it there, perpetrating and perpetuating it (that's a very important one which often resolves the incident)
When viewed this way, the incident often resolves before the whole list of special attention buttons have been called off. Sometimes because the whole secret about it has blown, sometimes because an the energies of the earlier incident on the chain starts to creep in. In either case it's time to end that phase of the incident running and either end session or move on to running the earlier similar incident.
Here is an example of what I'm talking about:
Pc has finished running the 6-directions after the "hidden buttons" command.
Auditor says something like "in that incident, is there a moment of blankness or blackness, or unconsciousness?"
What the auditor is looking for is the force and the cause of the force necessary to cause the thetan to go at effect and become "permanently" less able, i.e. less able from that point forward to present time.
The auditor then runs runs the before/after process on the blank area (or whatever wording indicates to the Pc). If the term "blank area" or "blank period" is used, it is done with the understanding with the Pc that it is just a convenient term that will still be used even when it is opened up and no longer really blank any more.
Afterwards, 6-directions is run on the blank area. This is followed by the usual R3XD commands applied to the blank area rather than the incident.
After the R3XD commands on the blank area have reached the same point as was applied to the incident as a whole, the commands then revert back to applying the incident as a whole, which includes the blank area.
If any other areas afterwards crop up, like the Pc suddenly says "and then a flash of light came out of nowhere"... well, that should alert the auditor that there is another area that needs uncovering. The auditor would then proceed to treat the "flash of light" period or area in exactly the same way as he did the "blank period", until it can be incorporated into the incident as a whole.
Also of interest to the auditor is 'how did the Pc meet up with his antagonist in the first place?'. Here there is an earlier beginning which should be inspected with the R3XD procedure starting with the before/after process.
I'll ask "how did you feel before you met up with that being who talked you into joining his group within the MEST universe?" Oftentimes the Pc was "bored", or "curious", and a whole area of disenchantment with existence and an entire earlier beginning which turns out to be a self-to-self. (flow four) issue. By then the Pc will often see an entirely earlier issue on the track which then becomes the subject of the next session where the earlier similar incident is taken up.
On the other hand, if this turns out to be the basic-basic incident on the chain, one can then handle it until it resolves on the basis of an entirely self-generated event.
Oftentimes a feeling of profound embarassment will ensue on the part of the Pc where he will finally recognize himself as the ultimate source of his problem - one which had been operating as a service fac all that time. This is always a good sign and a suitable end point for any incident or session.
This part of the incident is the part that is almost never addressed with "standard dianetics", whether R3R or R3RA or book-1 style. Book-1 comes closest though, but it's not very structured and so is more prone to variable results.
The general idea behind this whole step is to bring all the hidden elements of the incident out into the open for the Pc to finally view, confront and inspect after all these eons of sidestepping its core. One has to appreciate the seriousness of such an incident if so much time has elapsed between its inception and present time without inspection. Just taking the incident and doing a creative process on it, as has been often suggested by others, is not a substitute for direct, thorough and detailed inspection. I invite anyone to try the two approaches and compare the results.