If you want the index, start here: Projects for Work.
The goal of Projects for Work is to make the experience legible. A lot of claims sound good in isolation. Projects force the question: under what constraints did this actually work?
This taxonomy is the set of engagements and builds where thinking met external stakes: deadlines, customers, reliability constraints, budgets, teams, and outcomes that had to hold up in the real world. It exists as a navigable backbone for the site so you can trace systems ideas and decisions back to the projects that produced them.
The mechanism is cross-linking by structure. Each project term page describes what the work was, why it mattered, what made it hard, and links out to the related posts, system domains, tools, and skills that show up across the rest of the site.
The trade-off is that not everything can be public. Some pages are necessarily abstracted or incomplete. The intent is still the same: preserve the structure and the constraints so the lessons remain usable.
How To Use It
Browse alphabetically, open any project, and use the cross-links to explore the surrounding context (ventures, tools, skills, and systems patterns).
