Jonathan,

I just want to say sorry for today.   I was upset and I should have just shut-up.  It had nothing to do with you...

It's funny: working in the architecture business, I understand some of the language in the first document. It sure sounds like M runs a tight ship when it comes to the design process. I would not want to be the sorry architect who has to explain a change order or cost overrun to Rawat. For a man who pretends to know about peace, I'll bet he has melted more than a few architects!

Funny you said that.  You hit the nail on the head.  When I worked on Maharaji's B707 airplane project in 1979-1980 I worked in the design dept. with the project architect, designers, engineers.  M came into the design room very often (at least daily) for nearly a year.  Maharaji has what I term the "impeccability imperative."  He demands everything to be beyond perfect and there was never a reasonable deadline for his requests.  Working several days in a row pulling all-nighers was common too.  Micomanager.

I've seen M meltdown his architect/designers many times and it's really not pretty.  He melted down everyone else in his wake, too.  One day, Maharaji was in a nasty mood and said to the project architect:  You've only designed one small house, what do you know about jet aircraft!"  The little shit.

Oh.  There were no C/Os that didn't generate first from Maharaji but, the number of them was almost infinite. 

Sorry again for my mood...

Cynthia