Re: Ken Ogger, The Pilot speaks from the dead
[Note by RelayerAnt: What we are sending out is only excerpts and you can see the full Pilot's Posts at http://www.freezoneearth.org/pilot/posts/eframeset.htm]
Pilot'sPosts Z10
Clear and the Time Track
(From Post 58 – June 1999)
After all this time, I've finally realized a key fact about the state of Clear and the way R3R runs after clear.
After clear the pc's time track does not move at the auditor's command.
A clear will continue to mockup his own solid time track until he hits the clear-OT state. But it will only move under the control of the pc, not the auditor.
According to the R3R bulletins, the time track moves under the auditor's control. Based on the small amount of Dianetics I had before clear and based on running many hours of Dianetics on people who were not clear, this seems to be correct. The track moves when the auditor tells it to (assuming he is in control of the session and has decent TRs).
I had a great deal of Dianetics after clear. The auditor would say "move to (date)", and then, being in session and wanting to run the process and learn new things, I would obey the command and move the time track.
Notice the difference there. It is a big difference.
There is a time delay. The track moves instantly when it moves, but it doesn't move until the pc executes the auditing command.
Based on running a lot of Dianetics on others, the meter sometimes flicks when the track moves. On pcs who are not clear, you will see that flick (if it occurs) like an instant read on the move command. However, on pcs who I now think were unacknowledged Dianetic clears, that flick is latent, occurring when the pc did the command. It is not that the track takes time to move, it is that the pc takes time to decide to move it.
But there is an exception, which is entities' time tracks. These always move instantly at the command of the solo auditor. If they didn't, you would already have a blow.
Early on in NOTS however, and especially on unacknowledged clears, an entity may obey the auditor's orders and move at his command. I did not notice this happening later once I had a bit of awareness and control.
But in retrospect, I did have that happen sometimes in Dianetics.
It was always on overrun, gone past basic, or an unnecessary action. In those cases we would slip over onto a BT's track instead of my own. And in that case the time track would move under auditor control rather than being something which I did because I was asked to by the auditor.
That makes a mess because the unacknowledged clear being run on R3R misowns the BTs pictures for his own. I had to sort through a bunch of this on audited NOTS.
That is the liability of Dianetics after clear.
It is not that you can't run incidents or that you don't have incidents which you can make gains on running, it is that you can be pushed into sliding over onto somebody else's track.
With this trick, you can tell. If you consciously moved to the incident, it’s yours. If something else moved, then it ain't you.
Another interesting point is that after clear, the degree of impact or amount of force in an incident does not seem to be of significance. Lots of other stuff IS still significant in the incident, especially decisions, postulates, and your reaction at the time of the incident. But not the amount of force.
Also, the R3R commands specifically tend to get in the way. There are too many of them, especially the use of two move commands on one incident. There is too much thoroughness which coaxes you to put things back.
But incident running is still beneficial although it might better be left until you have enough cause and awareness over entities that you don't get fooled and misown their pictures. And it might best be done solo with a stripped down set of commands.
The time track retains its solidity until clear-OT. The solidity is the result of alter-is of time. Most especially it occurs because of pushing incidents out of sequence to justify overts, but other alter-ises are possible.
When the track blows, you cease to "move" on the track, there is no longer any sense of moving along a time line when you move to an incident. And yet you can still "move" to incidents, it’s just a bit different, there is more of a sense of mocking them up.
But incident running is still an aid to getting your confront up on things and finding and regaining control over old postulates.
But you will find something interesting, which is that the cumulative progression and build up of charge from incident to incident no longer exists.
If you are running sour grapes, you are simply getting your confront up on sour grapes. Whether it is an earlier or a later incident on what was once a chain hardly matters, what matters is raising your confront.
What is happening here is that with each state, more of the mechanics are dropping out and ceasing to matter.
On clear, the force goes out of the pictures and the pc's track ceases to obey external orders.
On clear-OT, the solidity of the track disappears and the cumulative chain effect vanishes.
Sometimes you get exceptions to this, and those are due to a BT. But that stops happening too on the cause over life state. You no longer misown others tracks or mistake BT think for your own.
And yet after all of this there is still aberration and some stimulus response left. Note that you cannot get an instant read on an e-meter without stimulus response.
An ARC break assessment will still instant read even after all of the above states are attained and after other states that I'm not even sure how to name or describe.
The grades material is basic or at least closer to basic than any of the heavier phenomena. Grades material continues to read and run well.
Hope this helps,
The Pilot
[relayed by Ant Phillips <[email protected]> in 2012]
