This is going to be a toy OS; definitely 32-bit, probably 64-bit in the future, (when I bring my Athlon 64 machine to my dorm)
As for intented use, I'm looking at the kind of person who would want the most spiffed-up, sexiest, most chock-full-of-eye-candy text console you could imagine.
As for the asrchitecture, in microkernel/monolithic/etc, my plan is for it to consist of a "core" (called XCore) that is small and light enough to be used just about anywhere.
One particular "appliance" built around XCore will be a desktop "operating system" (Xenon) that would keep external processes out of ring 0, provide virtual memory, and so on.
Ideally, XCore would be the only code in ring 0, and drivers, appliances (like Xenon) and the like will exist in rings 1-2.
Of course, at this point I have a IDT, a printf routine, and some other basic console stuff... and a double fault handler that is getting REALLY well tested.
In the future, maybe posix compliance, or something like that will come... but no firm plans yet.
The main reason for the XCore/appliance split is how much people love painting bike sheds; with enough sheds to paint, actual work can get done on the important stuff.