I'm wondering... is there a way to inhibit dirty tracking and automated saving with NH?

It could be usefull to explicitly mark and entity to be saved rather than saving it automatically, and I'm not taling about evicting the object because lazy loading should be available.

This way it would be easier for a custom layer above NH to validate all data because there would be no danger to edit an entity and forget to validate it.

If there is how do cascades work in such a case?

It's not exactly what you are asking for, but you can set ISession.FlushMode to FlushMode.Never, then the session will not execute flushes until you explicitly tell it to. (Except for entities which use identity id generation.)

Yap it's not _exactly_.

What I want is to be able to acknowledge saving for each and every entity whether transient or persistent...there's not way...right ?

Can you simply put whatever logic you want in IInterceptor.FindDirty()? From what I understand, that method lets you decide for each entity in the session's cache, whether it should be saved/updated by the impending flush. Is this what you want?