The aerospace world has always marked its real transitions with symbols — a wing pin for a first solo, a patch for a mission flown, a seal for a command handed over. None of that is decoration. It's how people recognize where they stand, and where others have stood before them.
AeroGlyph started from a simple frustration: most of those symbols get designed once, by whoever's available, with no shared vocabulary connecting one to the next. A squadron patch and a retirement seal end up speaking entirely different visual languages, even when they're marking the same career.
So we built one library instead — 253 symbols, organized into 17 families, documented well enough that a design decision made this year still makes sense five years from now. Everything we do, whether it's a course module or a client commission, draws from that same source.
A process implies a finish line — follow the steps, get the certificate, done. We don't think about symbol design that way. A first-year learner and a twenty-year practitioner are doing the same fundamental work: reading what a mark actually communicates, and to whom. The learner is earlier in that practice, not doing a lesser version of it.
That's why our curriculum is structured as a progression rather than a course catalogue, and why our consulting work always starts from the same documented vocabulary a student would learn in Module 2. There isn't a "simple version" of the library for beginners and a "real version" for clients — it's the same one, used at different depths.