Mapping Domain Vocabulary

Overview

The fastest index into complex cross-subsystem code is not the call chain — it is the domain vocabulary. Read the code as a dictionary: exhaustively extract every domain word (models, enums, fields, actions), give each a one-sentence role, and organize them into an ASCII tree grouped by subsystem → module → word.

Core principle: vocabulary before mechanism. Newcomers don't get stuck on flows; they get stuck on nouns. Once hold, entitlement, subminor are understood as words, the call chains read themselves.

When to Use

• The user asks to "survey the code for X" / "help me quickly understand domain Y" (梳理/盘点)
• The domain spans 2+ directories/services/packages (e.g. commerce + billing + sdk)
• You need a panoramic grasp of a subdomain before design or refactoring

NOT for: single-file/single-module questions (just read it); questions about one specific flow (explain the call chain instead).

Process