Keeping rudiments in looms to great importance with the realization that endless goals assessments occur only when rudiments are out. If rudiments are in, the goal invariably occurs in the first 100 goals the pc gives.

If rudiments are out the goal, terminal or assessment level vanish when found or won't appear at all.

Therefore, even better rudiments processes are necessary. Over the past month or so I have worked out and tested these for your use.

These rudiments processes supersede all earlier rudiments processes. They do not alter basic Model Session. They do alter all rudiments commands used in Model Session as noted:

Rudiments on the:

ROOM: TR l0 or pc's havingness process. (Run only until question about room produces no needle reaction.)

AUDITOR: What would you be willing to be? What would you rather not be? (Run needle action out only.)

PT PROBLEM: (When pc has stated it and who) What is unknown about that problem with......? (Run until needle no longer reacts on terminal, check any other PTP and run it as necessary.)

WITHHOLDS: To whom wasn't that known? To whom shouldn't that be known? (Run until needle no longer reacts.)

ARC BREAK: What didn't an auditor do? When? What weren't you able to tell an auditor? When? (Run needle action out only.)

Alter Model Session Script to include the above.

Limit two-way comm to asking what, where, when questions.