JUnit 4 Life-Cycle (Intercepts)

We are struggling a bit building a JUnit wrapper (framework) around using @ClassRule / @Rule / RuleChain / Runner / extending the 8 concrete Rule classes available etc.
 

 The root cause is a lack of clarity regarding the JUnit life-cycle.  For example, back when using Struts we had a clear list (diagram) of the 20/21 steps of the life-cycle.  So it was obvious when you could intercept/override the life-cycle.  Same with JSF, the six phases were clearly diagrammed as were the intercept options.
 

 We are finding it appears there are numerous opportunities (a feature) to intercept the JUnit life-cycle that the flexibility provided can turn into a liability without a model of those options.
 

 Is anyone aware of such an artifact?
 

 Thanks,
 _Marvin