ss-bs-discovering-glossary

You build a canonical project glossary by scanning READMEs, code identifiers, database schemas, and route paths to extract domain terms, then interactively confirming the final definitions with your team. This process reduces newcomer misuse of domain concepts during onboarding.

Domain vocabulary discovery is the process of scanning scattered project artifacts to extract and curate ambiguous terms into a single canonical glossary. During project bootstrapping, it aligns team terminology and provides a trusted reference for onboarding new developers.

You generate a glossary from codebase identifiers and database schemas by extracting evidence-cited candidate terms from multiple project layers. The process proposes up to 30 domain terms and uses interactive multi-select refinement to confirm final definitions.

Yes, you can merge new domain vocabulary into an existing GLOSSARY.md file. The process supports extend operations to merge terms, replace to overwrite, and audit modes that include drift checking against existing glossary content to maintain consistency.

The maximum recommended number of terms for a project glossary is 30. The discovery process limits the suggested term set to 30 entries to keep definitions short, usable, and focused on the most critical domain concepts for onboarding.

Evidence-driven glossary extraction prevents inaccurate definitions by surfacing terms only when concrete file-path and multi-layer evidence exists. This ensures every domain vocabulary entry is grounded in actual project artifacts rather than assumptions or guesses.