Interesting, and a good justification of the need for architectural responsibility when producing software. Presumably though, this does not need an architect as such, providing the appropriate skills, knowledge and authority are present within the team.
I felt that your characterisation of "smart developers" as being capable of everything except architecting for non-functionals a bit disingenuous. Good hands-on architects do not spring into existence fully formed, but instead grow from good developers who have an understanding of architecture. Therefore at any time there must exist some number of developers who are capable of making sensible architectural decisions, despite not having the official role or job title of "architect".
E-mail addresses are not publicly displayed, so please only leave your e-mail address if you would like to be notified when new comments are added to this blog entry (you can opt-out later).