BRE Business Rule Composer Error

The other day I came up with the awkward error when I tried to load a BRE Policy version in Business Rule Composer. The Error looked like this.

Well, I still dont know why it came up. Generally these kind of errors came up when you try to open or load a policy which is using many vocabularies and some of the vocabularies are not deployed or deleted acciently. This also applies to different versions of same vacabularies where the Rule within the policy are reffering to a vocabulary version which is deleted and you have a later version of same vocabulary available. It may also happens if you have used .Net helper class facts in the policy/vocabulary and you have not deployed the reffered version of the helper class in GAC. These are among many other things which needs to be exmined but there are some behaviour still mysterious to me. This is an example of such a mystry of BRE:

We 3 developers were working on a BRE project and each one is assigned a single Policy to develop and separate vocabularies for each policy. And finally when all were done, we need consolidate in one machine and I have got the exported version of each Policies and reated vocabs from my peers. I imported all of them successfully in my machine and also successsfuly deployed and published. After that, when I tried to open one such Policy in BRE composer, it bombed out thowing an error as above.

I analyzed and could see nothing wrong in it. All vocabularies are imported, deployed and published properly. If the artifacts got deployed and published, then how come there could be an error!!! I dont know... I scratched my head for 2 days, rebooting the box many times.
The interesting things is, it worked after 2 days!!! When I tried to open same policy after 2 days... WOW it opened. I still wonder.. is there a GHOST in my machine ?? :-)

Well, I got a reply from a senior .Net guy.... and he said that the Policy got deployed as all the files/vocabs are there, and BRE Runtime engine would have worked normally. But BRE Composer was still searching the .net assembly in its original .net project location where the reference was made to BRE composer initially. This sounds a good anwer, but its not correct as the policy and all its dependencies(vocabs/helper classes) were created by my peer in diff machine and were imported into my machine, deployed and published.... Mysterious...isnt it.