Put another way, the question you are faced with when entering the client is,
WHERE DO I LOOK NEXT?
Waves have a rich capacity for internal structuring, and it works well for constructing narratives. But the current Google Wave client lacks just such a narrative itself.
Ideally, we should be able to specify that overarching UI narrative as a Wave. Or more precisely, a information structure derivable from a Wave.
This came to me because I was trying out the Wave Embedding tutorial. In Firefox 3.5 the sample complains:
An invalid or illegal string was specified" code: "12
Well, when I go to the Google Wave client, how would I find the answer to my dilemma?
If "Search" is the first answer, that may be well and good, but it shouldn't be the answer to every such use. Otherwise, the Wavishness of the client is irrelevant -- I could just Google it.