Since everyone here is a coder, the favourites gotta be the hells-yeah answer - and you'll get no disagreement from me.
But the finer grained answer is more correct in my opinion, because it appropriately values domain expertise. People who know little bout software, but just use it are so valuable.
How the architectural roles are divided up seems to depend on the size and nature of the organization.
If I had it my way, I'd give the client a role of Story Architect if they write good, useful, detailed stories and use-cases.
