6304C18 SHSpec-258 Directive Listing [Part I] [Details on running R3M] Gobbledygook to comply with the form isn't right. The PC sometimes gives it, knowing that it should be such-and-such a form. Don't use it, since it will result in no rocket read. Something odd, but conceptually right, e.g. "Catholicness", is OK. It is up to the auditor to direct the PC's attention to what should be there and get him to find it. The liabilities of getting wrong items, wrong goals, missed items, etc., are so great that you should do everything possible to prevent these things from happening. You have a bank pattern that is at least close to the perfect pattern. The upper fourteen to eighteen and the lower twelve items (omitting the two lowest oppterms, which vary on every goal) are very set and patterned. The pattern is that of LRH's fifteenth GPM. He realized that we needed the basic fundamentals of the bank, and that the PC was in a bank so far back and so beefy that it was vital to get its character and its right pattern, or get killed as a PC. There is more to the GPM than appeared earlier, because no one could confront it all until a lot of charge had been taken off. The goal of that bank is "to create". To LRH's amazement, the pattern holds true later on the track and on other PCs. If the PC isn't run closely guided to this pattern, his rocket read goes off. So the pattern has value. There will be other patterns for other types of goals, but they can be extrapolated from this one. Directive listing has to do first with the accuracy of the pattern. When the auditor doesn't know what he is trying to do, it is not very successful. Directive listing is kind; permissive listing wastes time and PCs. The main thing that will give you trouble is the top oppterm and the top terminal. These are characterized as the final achievement of the goal (the top oppterm) and the negation of the goal (the top terminal).