I just realized it might be useful to look at the Chromium OS documentation for some inspiration.http://www.chromium.org/chromium-os
First off, I think this could provide us with a template for structuring Webian's documentation.
Secondly, it gives us an existing implementation of a 'webos' to design against.
Third, I wonder if it would be useful to fork ChromiumOS, strip out all the Chrome while leaving all the other WebOS infrastructure in place and put Chromeless+Webian on top. I imagine there's alot of useful code that runs in between the chromium and core operating system that might be useful for Webian.http://www.chromium.org/chromium-os/chromiumos-design-docs/software-architecture
From an architectural level: If we start with the scopes of the Chromeless and Webian Projects and overlay them on top of the architecture for Chromium OS, what does this imply needs to be stripped from Chromium OS? What kind of foundation does this give us to build from, and what gaps would need to be filled?
I'm not necessarily suggesting this is the best route to take, but it might be a useful thought experiment. Might as well learn from the mistakes Google's already made, right?