Paul giving a session

Ruds: Invalidation — Question

AUDIO: "OK. Has there been an invalidation?"

Response Options:

Yes

Yes, there is an invalidation

Yes, there is an invalidation. Ownership check please (in extra window)

No

No, I feel fine. Let's get on with the main action! • Close this extra window •

No, I don't see one. Back to the main options

Other

Shutting down | Don't want to continue | Realization

Write on Report:

Write the time at the start of the rudiment
Write the command if you haven't already done so
Answer the question (but no more)
For example:

5:18 pm
Inval?
Yes

Notes:

Procedure for handing an inval

Usual handling

The standard way of addressing the inval rudiment in Scn auditing is for the person to simply talk about it, saying what it is, and if that doesn't free up his attention to look for an earlier similar inval and state what that one is. And maybe an even earlier one.

Key out

An inval, like any rudiment, can also simply key out (disappear from one's attention) by merely looking at it momentarily. If this happens, no further handling is needed or even desirable.

General instructions for L1C/Rudiments

(Full details here)
  • Thoroughly understand the command and what it entails
  • No slacking off!
  • Go with what flashes to mind
  • Don't flog a dead horse
  • Write comments
  • Run till key-out and don't try to go on for some other end phenomena
  • Use the Robot commands

Add in Rub & Yawn if you wish