SPIKE on adding target functionality under the same repo
I'm finding on !1 (merged) that there could be some significant benefit to adding target processing into the same repo - or at least in developing both sides in tandem. I may open up a new PR to explore what this would look like.
If we did decide to put tap and target functionality into the same repo (either for the base classes or the derived actual classes), this would certainly cause a big headache in repo naming and discovery. For this reason, I think we'll probably ultimately still keep these separate. However, in the meanwhile, if and when it's convenient to test both sides of this process together, I may temporarily add in target-based functionality in order to (1) establish proper end-to-end testing and (2) build out the complete end-to-end inheritance vision.