Форма отчёта одитора должна содержать следующее:

Дату.

Law: When one or more of the four flows of an item or grade are left unrun, when used in later processes the earlier unrun ones restimulate and make mass.

Имя одитора.

This tells you that high TAs, heavy pressures and even illness can come from by-passed flows.

Имя преклира.

Время начала сессии.

Example: Dianetic Singles have been run on 7 items. Now the Auditor begins to run new items Triple without running Triple on the already run items. The result will be 7 unrun Flow 2s and 7 unrun Flow 3s. These will restimulate and form mass and by-passed charge.

Состояние преклира в начале сессии.

Example: Now let us say all 7 previous items have been run Triple. And the Auditor now runs a new item Quadruple. This leaves 7 unrun Zero chains. These can restimulate and form mass and by-passed charge.

Какой процесс проводился - ЗАПИСАТЬ КОМАНДЫ ДОСЛОВНО.

Example: Now let us say that Dianetics was all run Single and Grades were run Triple. This will restimulate the Dn chains F2 and F3.

Были ли какие-либо трудности или расстройства. Подзывался ли супервайзер.

Example: Let us say that Dianetics and Scientology Grades were all run Triple. An Interiorization Rundown is now run Quad. This will throw all Dianetic and Scientology unrun Flow Zeros into restimulation and give by-passed charge.

Был ли завершён процесс.

Any later grade run with more flows than used in earlier actions can throw the earlier unflat flows into restim, pile up mass giving high TA and BPC giving ARC breaks.

Время завершения сессии.

Состояние преклира в конце сессии.

The more the condition is repaired by L1C, L4BR, etc, etc, the worse the Mass gets.

Достижения или комментарии преклира.

Продолжительность сессии.

Thus High TAs have three principal sources:

1. Overruns

Рабочий протокол должен быть полной, непрерывной записью того, что происходит в сессии от начала до конца.

2. Auditing Past Exterior

Рабочий протокол всегда имеет формат А4 либо 8½ на 14 дюймов, записи ведутся на обеих сторонах каждого листа, и каждая страница нумеруется. Имя преклира пишется на каждом отдельном листе.

3. Earlier Unrun Flows restimulated by those flows used in later actions.

Одитор не должен перескакивать со страницы на страницу, а должен писать страницу за страницей на протяжении всей сессии. Одитор записывает в рабочем протоколе формулировку команд и вопросов проводимого процесса. При проведении большинства объективных процессов одитор и преклир передвигаются, поэтому нецелесообразно одновременно пытаться вести рабочий протокол и проводить процесс. Но когда процесс завершён или когда время сессии истекло, одитор должен записать, что произошло во время проведения процесса, включая все озарения, о которых сказал преклир, все встреченные трудности, и т.д.

There are other minor ones such as Drug Background, illness, etc, as per Hi-Lo TA Assessment.

Некоторые объективные процессы состоят более чем из одной части. Проводя один из таких процессов, одитор может делать заметки перед тем, как перейти от одной части процесса к следующей.

Страницу рабочего протокола можно разделить на две колонки - в зависимости от того, насколько крупный у одитора почерк.

One must not recklessly or continuously rehab a past major action. This causes overrun. The thetan is placed at the end of the incidents not yet in restimulation or run and the bank gets more solid.

Проводя в сессии различные процессы, чётко обозначайте каждый, отмечая время, когда он был начат и закончен.

Когда сессия завершена, любые дополнительные данные одитор вписывает в рабочий протокол ручкой другого цвета. Листы рабочего протокола от начала до конца сессии складываются в должном порядке и скрепляются степлером, сверху к ним прикрепляется «форма отчёта одитора».

The whole trick of this universe is contained in thetans copying or picturing incidents and then getting stuck in the later portion of them.

Время отмечается с равными интервалами на протяжении всей сессии. «Формы отчёта одитора» и рабочие протоколы никогда не копируются. Одитор должен всегда прочитать свои рабочие протоколы перед тем, как передать папку супервайзеру и, если какие-либо слова или буквы пропущены или их невозможно прочесть, их нужно вписать ручкой другого цвета.

“Incidents” is the keynote. A thetan is incident hungry.

ВСЕ ОТЧЁТЫ ВСЕХ СЕССИЙ ИДУТ В ПАПКУ ПРЕКЛИРА. Иначе прошлый одитинг нельзя проверить и кейс нельзя просупервизировать.

This is what traps him.

Если эти правила выполняются, то это сделает работу супервайзера намного более лёгкой и отчёты одитора более ценными.

For some reason he has to be at the earliest end of incidents to erase them. The later he is in incidents and the later he is on the track the more solid he is.

И в качестве очевидного добавления к вышесказанному: проводить любую сессию или ассист, не сделав отчёт одитора, или снимать после сессии копию с настоящего отчёта и подавать копию вместо настоящего отчёта – это ПРЕСТУПЛЕНИЕ. Отчёты о проведённых ассистах, если проводились только контактный ассист или ассист-прикосновение, можно написать после сессии и послать в отделение квалификации.

This also applies to the “auditing time track”.

By omitting things like flows on the auditing time track, the thetan thus becomes massy.

Пересмотрено при содействии Отдела технических исследований и компиляций ЛРХ

The whole theory of the Interiorization Remedy is based on having gone out (later) after he went in (earlier). So Exteriorizing can stick him. (People buy the Int RD to Exteriorize but the remedy is only done to permit further auditing. They Ext of course when the bank is handled.)

When flows of items are by-passed and then later restimulated by auditing them, mass occurs.

When doing additional flows on earlier items or processes one must also check or rehab those flows marked as run to F/N in worksheets.

This again will leave unflat flows and BPC unless it is done.

And if it is overdone it will raise the TA by overrun.

So if one had a case that had Single Dianetics and was later run on Triple for new items (but the Singles not done into Triple) one would have to run first the missing unrun flow or flows if they read and then check the first Single Fl for flatness, then check other previously run flows.

The rule is run the previously unrun one or ones first if they read to get charge off, then verify or run the ones listed as run already.

Then one would do the same for the next item. Run the previously unrun flow or flows if they read and then verify or run those listed as already run to be sure they F/N.

All items, in chronological sequence, and all processes, would have to be run Quad.

It would be a waste of time now to run in only Triples.

Whether you have the Quad commands or not they are easy to figure out as you are only missing the Zero Flow, self to self.

So all C/Ses and auditing actions are “Rehab or Run Fl, F2, F3, F0 if they read” when getting in all flows on things run to date.

When you are sure an Int RD has been done correctly and its 2wc went F/N and the TA later goes high, you check the Int RD. That is the most usual reason. This simple action is amazingly subject to flubs.

If the TA goes high later you can do a C/S Series 53 or a Hi-Lo TA Assessment and handle.

If the TA is still high or low, you had better check the state of flows. Were more flows run on later actions than were run on earlier actions?

If so, your pc has felt massy, sometimes even ill.

The right action is to get in all flows from the beginning. And do it Quad. Bring all his auditing up to Quad.

(If his folder is not available, he has kind of had it. I know of no way, at this writing, to recover lost Dn items but will have to work something out.)

If the pc is not in trouble, his best bet is to get on up the grades to Expanded OT III.

If he is massy and is having trouble the best bet is to:

1. Be totally sure of his Int RD.

2. Check O/Rs particularly of a major grade twice or by-passed F/Ns, locate and indicate them.

3. FES, list the items and grades and do a Full Flow action from the beginning of his auditing, raising them all to Quadruple.

The Zero Flow in Dianetics is a bit strange. It can be done by full R3R but it often depends on the decision the pc made and may F/N very suddenly. It is easily overrun and can be very fast.

A pc can be gotten into trouble on Zero Flows if the Auditor is slow and is not alert to his meter and misses the F/N and gives R3R commands after the flow has blown.

The Auditor getting in Zero Flows can also ARC Brk the pc by failing to verify if the previously run flows are flat. All the Auditor wants is to see them F/N on the command. If they don’t he runs them.

Sometimes when he has “run them” again he finds they are being overrun or run twice and has to rehab them by finding this out. The pc sometimes doesn’t know until he actually starts to run them. Then he finds they are already run. The clue to this is a climbing TA. If the TA goes up, get off that flow and rehab it.

Example: Pc at first thinks “Pain in shoulder” F2 was never run. Starts to run it. TA goes up. Auditor must pull him off of it by finding out if it is being run twice and rehab it to F/N.

The moral in all these reruns is don’t firefight, keep an L1C List and an L3RD List handy and use them.

The results of straightening up the Int-Ext RD, rehabbing O/Rs and putting in all flows on a pc are fantastic.

Getting an All Flows Rundown done correctly gives one all the latent gain the pc has been begging for.

So send to Cramming all C/Ses and Auditors who flub.

Program it right.

C/S it right.

Audit it right.