Paul giving a session

R3X Int RD: 06 Can't Get In — 4 Flow Commands

AUDIO: "Fair enough. Follow the instructions to the right of the screen."

Response Options:

INT BUTTON: CAN'T GET IN

Run the flows in this order (skipping ones that are not charged):

F1: Locate a time when you couldn't get in.

F2: Locate a time when you caused another to be unable to get in.

F3: Locate a time when others caused others to be unable to get in.

F0: Locate a time when you caused yourself to be unable to get in.

This Int button is flat right now

Shutting down | Don't want to continue | Realization

Write on Report:

Write the time every now and then
Write the Int Button name (not just the number)
Mark each instance you execute a command
Write brief comments as needed

For example:

R3X Int Rundown (Ownership: Generally)
11:31 am
CAN'T GET IN
Flow 1 . . .

(Write usual R3X notes as you run the incident)

Notes:

Running R3X

The link will open up an R3X screen in a new window. The command on that screen is a generic one showing the appropriate flow but not a specific button. For example, the Flow 1 command is OK. Locate a time when you _____ [Int Button].

Keep in mind the appropriate command as shown on this page.

Overall outline of rundown:

  1. Assess the 12 Int buttons to find the hottest
  2. Run with R3X all four flows re that button
  3. Repeat above two steps until done

(Note: You have the option of running these actions addressing ownership issues if you wish.)

Rub & Yawn when needed as usual