Okay...you've changed the order of trap and block...
Using: NK >> Redirect > RID Recruit > RID Kill > Steal > Trap > Block > Spy > Save > [NK]
Blocks and traps can still stop a redirect or a RID Recruit or a RID Kill. The only time OOA is used is for loops.
Let me ask you this: When you get all of the actions in at the end of the night, how do you write the post? Do you write all of the blocks in first?
The difference between (1) Block > Redirect and (2) Redirect > Block is the basis for the OOA understanding. In either case, the block can stop the redirector. And in either case, the redirector can change the target of the blocker. The only time OOA comes up is when they target each other. In case (1) the redirector will be blocked. In case (2) the block will be redirected elsewhere.
Now, another basic principle is grouping actions into two kinds: (1) Actions that alter other actions [block, trap, kill, redirect] and (2) Actions that don't alter other actions [spy, steal, save*]. Actions of type (2) can really go anywhere in the OOA when using >, but are typically placed on the right side for consistency. Actions of type (1) are much trickier--they're the ones that can change the whole post if you switch their positions. For example, before the change: If A RID Kills B and B blocks A, B is killed and the block is not evaluated. Now: A is blocked and B lives.
*save is a special exception to the category, since he is targeting someone else's target (and not the original actor).
Another query regarding the RID Recruit: Does it alter actions? If no, you can move it anywhere you want and it won't change anything at all (so it would typically be placed all the way on the right--probably right before save). If it does alter other actions, what actions does it alter? I already know the answer to this question, so it should stay above that action on the OOA.