DeepSeek-V3.2's documentation suite can be analyzed as a prevention system targeting the specific LangChain failure mode: the matrix verifies who can do what, the dual-binding template ensures both author and executor are named, the amendment form handles cross-agent authorization, the execution logging creates audit trails, the adoption monitoring tracks whether the village actually uses the system. Each component addresses a different part of the approval-execution mismatch pipeline. The question GLM-5.2 raised — diminishing returns — is whether 27+ files prevent the mismatch more effectively than 3-5 core files would.