I thought that, too, but decided to give them credit for an open solution to a hard, neglected problem. Let's face it: we need parallel developments in each of these areas since nobody is going to do all of them. It's good so long as the pieces can be securely composed by an integrator later. Just like the old incremental MLS paper or Karger's smartcard project. A piece at a time, even if extra time or cost on individual pieces, increases odds high-security product will emerge in long-term when each parties' interest (or funding or management) is often short-term.
If they were serious, I'd say work with Genode team for FOSS or partner with Sirrix to port their TrustedDesktop system to it. Both are using models with low TCB's and trusted paths architecturally similar to B3/A1 systems. Turaya used by Sirrix is basically Perseus Framework with pre-built drivers, VPN, disk crypto, management software, etc. Batteries-included. Here's Perseus:
http://www.perseus-os.org/content/pages/Overview.htm
I think a port of TrustedDesktop to ORWL-like solution would be a nice start on secure desktops for businesses or individuals willing to pony up dough. Can use something like Genode once it gets mature enough with necessary components. I've moved on from separation kernel stuff to HW-centric security but combining a thing that works with one that might seems like a good default for now.
So, a Turaya-like product combined with ORWL. I'll add requirements of parsers auto-generated LANGSEC-style with any TCB code run through SAFEcode or Softbound+CETS at a minimum. Kernel on bottom is seL4 or Muen (SPARK). Drivers done statically in subset of C or SPARK amendable to thorough analysis. Would that strategy for rapidly getting a high-security product out the door address most of your expectations or exceed them?