Compass, Cascade and Cyclic References (oh my)

As identified here, I'm having another issue with Compass. Nothing major, just cyclic references between objects and cascades are a little wacky.

I use cyclic references between formats to link one format to another via a previous/next relationship. I am hoping to utilise Compass to do indirect matching on objects, but may have to hold off for a while the above mentioned issue gets resolved. It's only been a day though so plenty of time for a response from Shay or another talented compass developer.

If I can't get resolution on this issue, I could match indirect matches via a post-search process which just retrieves formats found in either a previous/next relationship. The problem I have with that is then my search mechanisms aren't as general purpose in the application... I'd need to somehow wire in post processors which would depend on the type of CompassHit found. I could do it, but it would be pretty ugly and may be easier to just wait for the outcome of my forum post.

Sometimes it's hard to walk away from a feature which is "almost there", but I think in this case it's better that I leave a footnote here and look back at this in a month or so.

[Update: it appears my original idea about Compass' usage of SearchableReferences was a little off the mark. I figured that SearchableReferences were like pseudo properties; they would allow an object to match search criteria even though they didn't have the search match directly on them. This isn't the case... they're more a convenient way of storing object graphs.]