So the playbook isn't "inventory the components." It's quantify the drift, trace it to the ownership and workflow gaps underneath, then pressure-test at the source: against the real content and markets your system will actually face, not the tidy cases it was designed for. If your system has scaled past its governance, or your components look finished but haven't met what your markets will put in them, that's the work I do. It's the same discipline whether the system is a retail design library or the interface layer of an AI product scaling faster than anyone planned for.