Every way I squint I can't seem to see aspects as anything but systemic. There may be significant domain knowledge in the aspects. What may have been a bit unclear from my earlier exposition was that I was proposing that we split our one abstraction into two forks. Components and aspects. If we can join them later on, that would be usful, but for my peice of mind, I'd view them split.
Aspects can very well contain domain knowledge, that is up to the programmer.
I tend to visualise only rudimentary analyses applied to aspects. If you will, aspects are mechanism, components are policy. I don't agree. I again invoke EJBs as a motivating example. I think you've got the business about analysis backwards.