# Product Vocabulary Specification Version: 1.0.0 --- # Purpose The Product Vocabulary establishes a common language for everyone participating in the project. Its purpose is to eliminate ambiguity by defining business terminology, technical terminology, user roles, acronyms, product names, and any words that have a specific meaning within the project. The Product Vocabulary serves as the authoritative language reference for all governance documents, implementation activities, and future enhancements. --- # When This Artifact Is Created The Product Vocabulary is initially created during the Governance phase following Discovery approval. It is updated whenever new terminology is introduced or existing definitions change. --- # Dependencies Requires: • Discovery Summary • Business Interviews • Organization Information Referenced By: • Product Bible • Source of Truth • Product Requirements • Information Architecture • Data Dictionary • UI/UX Bible • Build Master Plan • Decision Log --- # AI Generation Instructions The AI should identify every business term that could reasonably have multiple interpretations. Definitions should be written in plain language. Avoid technical jargon unless it is required for accuracy. Each definition should be concise, precise, and consistent with every other governance document. If conflicting terminology is discovered, the AI should recommend a single preferred term and document any deprecated alternatives. Every governance document should reference the Product Vocabulary when defining business concepts. --- # Required Sections ## Business Terms Words and phrases specific to the business. --- ## Product Terms Names of features, modules, services, capabilities, and major components. --- ## User Roles Definitions for every user role and stakeholder. --- ## Technical Terms Technology-specific terminology used throughout the project. --- ## Acronyms Every acronym used within the project together with its definition. --- ## Deprecated Terms Terms that should no longer be used together with the preferred replacement. --- # Entry Format Each vocabulary entry should include: Term Definition Category Related Terms Notes (Optional) Preferred Usage (Optional) Deprecated Replacement (if applicable) --- # Example Term League Administrator Definition A user responsible for managing a roller derby league, including members, events, and operational settings. Category User Role Related Terms League Tournament Member Preferred Usage League Administrator --- # Validation Criteria The Product Vocabulary is complete when: Every major business concept has been defined. Every user role has been defined. Every acronym has been expanded. No conflicting terminology exists. Definitions remain consistent across all governance documents. Deprecated terms have documented replacements. --- # Maintenance Whenever new terminology appears during Discovery, Governance, Architecture, Planning, Implementation, Validation, or Evolution, the AI should determine whether the Product Vocabulary requires updating. The Product Vocabulary should always be treated as the authoritative source for project terminology.