Русская версия

Site search:
ENGLISH DOCS FOR THIS DATE- CS Rules (CSS-042) - B710609-2
- CS Rules (CSS-043) - B710609-3
- CS Tips (CSS-041) - B710609-1

RUSSIAN DOCS FOR THIS DATE- Правила КС (Серия КС 42) - Б710609-2
- Правила КС (Серия КС 43) - Б710609-3
- Советы КСам (Серия КС 41RA) (2) - Б710609RA77
- Советы КСам (Серия КС 41RA) - Б710609RA77
CONTENTS C/S RULES TROUBLE FOR THE PC OVERREPAIR AUDITOR INVAL
HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex
HCO BULLETIN OF 9 JUNE 1971
Issue III
Remimeo CS Series 43

C/S RULES

TROUBLE FOR THE PC

Never make trouble for the pc.

When a pc is running well let it roll. The C/S can spot a possible error but the pc is Wide F/N VGIs at the Exam, let it go.

Chew the auditor, send to Cramming. But don't throw the well running pc into extensive repair — don't break into a winning program harshly. It gives the pc a loss.

The pc who isn't running well is the one you repair. Don't keep a pc going on and on, running badly with no case study. Study the case folder, find the right why by going back to where the pc was running consistently well and then come forward for the error. It will be in the exact next session.

If the pc wasn't ever audited before, you go into his life of course, with a GF + 40 Method 5 and handle and other Life repairs.

OVERREPAIR

Any Repair or Progress action has reached its End Phenomena when the pc is running well again.

This is peculiar to the Repair or Progress program.

Wrong Example: Pc was on Grade III, fell on his head. C/S studied case, found out lists, wrote an extensive Repair Program and C/S. Half way through repair the pc again was flying. C/S continued the repair. Pc bogged. C/S C/Sed the pc to flying again. C/S continued the repair. Pc bogged.

Right Example: Pc falls on his head on Grade III. C/S writes a Repair Program and C/S. Auditor finds the out list, corrects it. Pc flies. C/S puts pc at once back on Grade III to complete.

AUDITOR INVAL

An auditor can be invalidated by a C/S by having a lot of questionable tech points thrown at him.

The auditor's data gets shaky.

If no decision was ever made — is not in HCO Bs and tapes — is not to hand and can't be referred to by HCO B and tape, then a C/S should not be making the point.

Example: Auditor extends a list three more items beyond an F/N. C/S chops him. There is no such rule. The pc maybe wouldn't accept the item until he listed a few more. Result is a firefight between C/S and auditor, simply because it isn't a valid point.

HCO Bs and Tapes are the stable data that form the agreement between the auditor and the C/S. "If it isn't written (or spoken on tape) it isn't true. "

Don't wander off known tech points in C/Sing.

Never shake an auditor's data by advancing data not on HCO Bs and Tapes.

Always know your data, your HCO Bs and Tapes and refer the auditor to them in Cramming.

Cramming must have a library of all materials.

A hidden data line can build up in C/S-Auditor lines (or course lines or Cramming lines) that can unstabilize all tech and deny further results.

The decay of tech in areas begins with hidden data lines that are not true.

So use and refer to HCO Bs and Tapes and leave all other points alone. Your auditors will become confident and certain and Tech will improve.

It's enough just to insist on the usual.

Then auditors and cases will fly.

L. RON HUBBARD
Founder
LRH:sb.rd