6301C15 SHSpec-231 R2-12 Nevers
Never represent a rockslamming item, i.e. anything that ever rockslammed,
because a rockslamming item comes from some source, and if you don't know what
the source is, it could be wrong. An arbitrary source is dangerous. This is
the most dangerous point in R2-12. Never use an arbitrary list. Don't try to
oppose some rockslamming word that just comes from nowhere.
Never abandon R2-12. Nothing else will patch up R2-12, if it gets fouled
up. R2-12 is an ultimate process, i.e. a process that repairs itself. Never
try to patch up R2-12 with something else, because it will fail.
Never let someone lose records or keep records inaccurately. There is a
way to straighten out a case whose records are lost, however. Using the meter,
find when the PC's case caved in, the session in which it occurred, and put
mid-ruds in on that session. This will get the PC's memory improved to the
point where he can give you data about the list, or whatever. But this is a
very arduous approach.
Never attribute a violent ARC break to anything but a wrong item or an
incomplete list. It is not caused by a missed withhold, except in the sense
that the missed item is the withhold. This datum applies in the workaday
world as well as it does in session. Somebody has missed an item on the U.S.
government. Probably, the ARC break is from no-auditing and missing all their
items.
Never run a PC darker and massier. He won't get lighter. Come off it at
once.
Never give a PC an item and then do something else at once. This is very
distracting to the PC, and if it is a wrong item, the ARC break will be
compounded. You must allow a minute or two of observation. Just put the
meter aside and make a little routine of it and say, "Well, apparently your
item is _______ ." Watch him like a hawk. Does his face get dark? Does mass
come in? If so, don't let it go any longer. Tell the PC that you want to
continue listing. Never lead a PC to believe that you are giving him an item
when you are not. There can be a funny condition where all the indicators
look right, but after the PC cognites, the rock slam will vanish as the lock
blows, after which the wrong-item indicators start to show up. So don't shift
the PC's attention. This will save lots of trouble. The longer you let a PC
keep a wrong item, the more trouble it will be to patch it up.
Never persist with a wrong action that is worsening the case, just
because you don't know what to do. It is far better to end off or take a
break to straighten things out. It is good sense to know what you are doing
before you do it. This does not mean somatics. That's not a sign of the PC's
getting worse at all.
Never let case errors accumulate or multiply. When you are aware of an
error on the case, fix it without forgetting that it is an error to fail to
complete a cycle of action on the case. But also don't interrupt a PC that is
doing well. If the case isn't running OK, repair earlier mistakes.
All lists stem from some arbitrary point. It can't be helped. The three
universes from which you list are:
1. The PC's PT session environment.
2. His PT non-session life and livingness environment.
3. The parts of existence.
Each of these can be listed positive or negative, oppterm (+ or -) and
terminal (+ or -). Thus you have twelve sources. One way to make auditing
with these less risky is, when clearing the command, to test it for rock
slams. This can include testing words or segments within the command for rock
slams. Never represent it if it rockslams. Clear the command and vary it
around until it makes sense to the PC, until it's real to him. Never try to
list a list question that the PC cannot answer, i.e. clear it with him and get
his agreement to answer it.
Choosing the wrong universe to list will get you missed withhold
phenomena, including ARC breaks, because the PC's attention is fixated on the
universe that you are not asking him about.
Never, in your anxiety to clear someone or pacify someone, fail to get
his PTP's and hidden standards out of the way. That is all, in general, that
has been wrong with clearing.
Wyszukiwarka
Podobne podstrony:
SHSpec 228 6301C10 R2 12SHSpec 224 6212C13 R2 12 Data Needle BehaviorSHSpec 221 6211C29 R2 12 Theory and Practice (Part II)SHSpec 222 6212C11 R2 12 DataSHSpec 220 6211C29 R2 12 Theory and Practice (Part I)SHSpec 226 6301C08 R2 10 and R2 12SHSpec 225 6212C13 Repair of R2 12SHSpec 232 6301C16 TR 0SHSpec 229 6301C10 How to AuditSHSpec 230 6301C15 Dead HorsesSHSpec 219 6211C27 Routine 2 12 (Part II)SHSpec 242 6302C21 R2 and R3 Current Auditing RundownSHSpec 218 6211C27 Routine 2 12 (Part 1)2015 06 23 Dec nr 231 MON 12 Szczecińska DZ odznaka pamiątkowaSHSpec 12 6403C19 Flattening a Process248 12Biuletyn 01 12 2014więcej podobnych podstron