Agree with pfehre - N1QL views must not be modified. It actually enforces this by adding a checksum to the views and stops using views where the view definition has been modified.
So in general, the views generated by N1QL must be considered an implementation/machine artifact and not intended to be read or modified by the developer.
It is a very interesting problem to allow developers to define views, and have intelligence in N1QL to introspect and utilize them, perhaps with some assistance from the developer. This is one of the features we’re considering but don’t have a concrete plan at the moment for it.