Reading the EOS white paper, I was just wondering if you've declared a dynamic array for the "named permission levels". If I was writing this I might be inclined to create an array with a TPermission class where each TPermission object is dynamically allocated/freed and has properties such as...

PrivateKey: array of char(0..x);
PublicKey: array of char(0..x);
Permission: TAuthority; // class with range of permission scope with boolean vars for each area of access

...

But then defining the capabilities of the contract types eludes me. Custom contract design is not easy to account for in code unless a lawyer writes the code for each situation.