Glossary

The why-attached-to-code

The why-attached-to-code is CatWrangler binding each decision and its reasoning to the exact code it shaped, so two days or two years later you (and your agents) can see not just what the code does, but why it’s that way.

Where it shows up

It’s the heart of “decisions are the artifact”: the reasoning isn’t in a doc that drifts — it’s bound to the exact code it shaped, so it’s still there, and still true, two years later.

This definition is reused verbatim everywhere the term appears.