I like the way you've communicated how the codes have developed (or perhaps proliferated) over time. This is a classic moment in qualitative analysis -- when you realize that the "master" code you've developed needs to be broken down and then you find myself making a gazillion codes and ponder if it is time to roll things back up. In terms of process issues: the definitions you've provided in this short memo are pretty concise and it may be as you push yourself to more thoroughly define codes you'll discover which can be easily combined or which really aren't different after all. And then a substantive thought: you seem to have some codes which are pretty rich and analytic and others that are a bit more concrete and descriptive. It may be worth clustering those groups together (or seeing if other clusterings emerge). These types of codes do different things in a project. Often you need both types but it is also typically helpful to be clear about which is which.