Tribal Knowledge

Every team has it. The reason the batch job runs at 2am and not 3am. The one customer whose contract quietly bent a validation rule three years ago. None of it is written down anywhere the system can produce on its own, it lives in a few people's heads, and it evaporates the moment those people change teams.

Tribal knowledge isn't a character flaw. It's what happens by default when documentation lags behind decisions. The trouble starts when an engineer, or an AI agent, needs to change that code and has no way to ask why it's shaped the way it is.

The toolkit exists to convert as much tribal knowledge as possible into contracts. Seelegibility for how that gets measured, andContract-Driven AI Developmentfor the discipline built around doing it on purpose.