Please reference these docs:
Tags should be a descriptor to an object -a contact, a note, or anything else. It's based off of attaching a paper "tag" to a thing to describe it.
Because we're in the digital world of integration, accessibility, and simplification, it's both equally important that tags have meaningful names as well as specific descriptors.
Because we live in an automated age, tags can also be used to perform certain actions or keep track of information for integrations, so there must be a clear delineation between tags used for this purpose and tags used for a more human-readable one.
When creating a tag, it's best to use the TAGGING ARCHITECTURE doc here: https://docs.google.com/document/d/1jX7VsJ63m8B1nBvGZYYeTs4ESHQYHGWRlbsWtrbmn4k/edit as a guideline.
Special tags that pertain specifically to Michael Lennox and may be used by other processes are noted below ; there may be tags or classes that aren't listed, but follow these patterns.
purchase_class_shadow
purchase_class_findingyourvoice
purchase_class_jumpstart
purchase_class_forgiveness
purchase_class_dreamcircles