The first goof relating to Releases is the one done for 15 years — running past a free, floating needle on any type of process. THIS is the goof that held back all Scientology. And if it continues to be done, known as well as it is now that you mustn’t, one can only consider it suppressive — not just ignorant — as who now doesn’t know you wreck a Release by running past the floating needle?
Not doing a Rehabilitation by the book, HCOB 30 June 1965, HCOB 21 July AD15 and now this one would constitute a breach of tech.
To say you are "Rehabilitating a Former Release" and yet do only current rudiments is, of course, a lie.
Rehabilitation is an exact series of actions covered in the above HCOBs and NOTHING ELSE.
I have seen a case being given an assist on PTPs and current ARC Breaks and had the auditor say, “Oh yes, I’m following orders. I’m rehabilitating a former release."
Rehabilitation of a Former Release is a PRECISE SET OF ACTIONS covered only in the above HCOBs and this one.
One only does THOSE actions given in these HCOBs.
The roughness of the Auditor’s Comm Cycle can prevent, not only a Release from occurring but can prevent rehabilitation.
All auditing is best done muzzled with the auditor drilled on Mutter TRs.
In Step 1 of HCOB 30 June 65 it says, "Loosely locate the session or time in which it (Release) occurred."
This means a METER DATING.
By “loosely" is meant to the year, month and day, not the minute. You can of course locate to the hour.
ADD AS THE PRIMARY STEP TO HCOB 30 JUNE 65
1. LIST AND EXACTLY DATE BY METER EACH AND EVERY TIME THE PC HAS ATTAINED A STATE OF RELEASE IN THIS LIFETIME.
That should dispel any doubts about what rehabilitation of former release is aiming to do.
ADD ALSO AS A PARAGRAPH IN HCOB 30 JUNE 1965:
IF THE PC’S NEEDLE GOES FREE WITH THE TONE ARM BETWEEN 2 AND 3 ON A CALIBRATED METER, CEASE REHABILITATION AT THAT INSTANT AND DECLARE. DO NOT CONTINUE BEYOND THE FLOATING NEEDLE ON A REHABILITATION EITHER.
IF A PC’S NEEDLE FLOATS DOING THE HCO POLICY LETTER FORM 26 JUNE 65 CEASE AT THAT INSTANT AND SEND TO GET THE STATE DECLARED. DO NOT KEEP ON DOING THE FORM PAST FLOATING NEEDLE EITHER.
IN FACT DON’T CONTINUE ANY PROCESS OR AUDITING BEYOND A FLOATING NEEDLE. YOU CAN SHIFT FROM PROCESS TO PROCESS, A FREE NEEDLE ATTAINED ON EACH ONLY IN POWER PROCESSING AND ONLY ON R6-GPMI.
An auditor must also realize that handling current matters and all on a former release in a rehabilitation is violating further the rule DON’T AUDIT PAST A FLOATING NEEDLE. The whole trouble with the pc was auditing beyond Release. Therefore in rehabilitation even ruds are just more auditing aren’t they? You can only do HCOB 30 June 65 and its further HCOBs.
Floating needle, free needle are the same thing. What does one look like? Once you’ve seen one you’ll never make a mistake on one again. For it floats. It ceases to register on the pc’s bank. It just idly floats about or won’t stand up even at low sensitivity.
The TA goes to any place between 2 and 3 and the needle floats.
Differences in cans used as electrodes and not keeping the meter calibrated with 5,000 ohm and 12,500 ohm resistors clipped between the two cans and setting the TA to (F) and (M) can lead an auditor to "find" a floating needle at TA 3.8 but ignore it because the meter is out.
Also, two meters used can both be out. Particularly if the wrong cans are used.
Steel cans, chromium plated or tin plated (like ordinary vegetable soup tin cans) are the best electrodes.
Not getting every time the pc has been a Release in this lifetime can be a big goof.
Sometimes the last one is just yesterday, but omitting it can halt rehabilitation.
Getting whole track (before this lifetime) former release periods is of questionable benefit but cannot be ruled out.
The leader in making a high state of being collapse (given an R6 bank) is the pc’s own purposes.
A person shot up scale can postulate. Postulating going down scale or an attack on something can collapse a state of release.
Protest, wanting to get even, revenge are some things that a pc postulated that made him go back into the bank.
It’s a goof for a pc to postulate himself down scale or to postulate himself right by showing another he is wrong.
This is why Class IV processing (Service Fac) can so easily make a 1st Stage Release.
Sometimes a pc is not rehabilitated yet is so declared. This causes a serious upset.
Sometimes the Examiner fails to detect the flaw that the pc doesn’t think he was released and passes the pc.
Sometimes the Examiner challenges and fiddles about too much. This is a withhold of acknowledgment of the state and will cause an upset before it can be awarded.
An org which is not alert to the way SPs go for new releases when the release is still finding his or her "feet" will make very few that remain stable.
If an org develops a lazy attitude toward auditor and personnel discipline then two things happen:
(a) Auditors and execs alike think it is all right to audit past a floating needle on a form, action or process or
(b) Start declaring people who aren’t released.
Either way is catastrophe. The middle road of honest and precise tech is vital.
Auditors with sloppy comm cycles almost never release anyone to floating needle. Such begin to believe it is "all gas" so it doesn’t matter what they do.
An org not alert to what a bad comm cycle can do to prevent release is "for it" as tech will fade.
For fifteen years auditors have made and then undone keyed-out-clearing all over the world.
We can then assume that, as they had the data about floating needles in 1958 and did not heed it, we will have this battle with us from here on.
The end product of all auditing right up to clear is a floating needle.
There is no other end product from the auditors’ viewpoint.
So, shall we get on with it, see it when it occurs and declare it?
Please?