All the more reason why your point doesn't make sense in context. But I'd argue that the architect maps out the interactions between the various systems but does not, IME, get involved in the nitty-gritty details of the implementation that can really make the difference between a good developer experience and a horrible one.