docs: Add comprehensive version nomenclature documentation across all files

- Updated main README.md with current version (v3.1.3) and complete version format explanation
- Updated entity counts from 29 to 35 entities throughout documentation
- Added comprehensive version nomenclature section to main README with practical examples
- Updated specifications README.md to reflect consolidated build system (build.sh)
- Enhanced WORKFLOWS.md with detailed CI/CD version extraction and usage patterns
- Created comprehensive VERSION.md with complete reference documentation
- Updated CHANGELOG.md to document the Git-based version nomenclature system
- All documentation now explains v3.1.3-5-gaac45b1 format with traceability benefits

Provides complete understanding of Git describe-based versioning across development,
CI/CD, and production environments with precise build reproduction capabilities.

Author: pwt-cd

.github/WORKFLOWS.md

@@ -9,9 +9,10 @@ The BOOST repository uses GitHub Actions to automate documentation building, val
 ### Key Features
 - **🐳 Docker Containerization**: All builds use `ghcr.io/carbondirect/boost/boost-builder:latest` for 4-6x faster execution
 - **🚀 Automatic Releases**: All semantic version tags trigger full release packages  
-- **✅ Schema Validation**: Comprehensive validation of 33+ entity schemas
+- **✅ Schema Validation**: Comprehensive validation of 35+ entity schemas
 - **📄 Multi-Format Output**: HTML, PDF, and interactive ERD Navigator generation
 - **🔍 Version Analysis**: Intelligent version type detection and appropriate release handling
+- **🏷️ Automated Versioning**: Git-based version nomenclature with complete traceability
 
 ## 📋 Workflow Summary
 
@@ -22,6 +23,67 @@ The BOOST repository uses GitHub Actions to automate documentation building, val
 | [📚 Build Documentation](#build-documentation) | Push to branches | Build development docs & deploy | ✅ Docker | ~2-3 min |
 | [🐳 Docker Image Builder](#docker-image-builder) | Dockerfile changes | Build & push container images | ❌ Native | ~5-8 min |
 
+## 🏷️ Version Nomenclature in CI/CD
+
+All BOOST workflows use automated Git-based versioning for complete traceability and reproducible builds.
+
+### **Version Format: `v3.1.3-5-gaac45b1`**
+
+Every build automatically extracts and uses version information following the Git describe format:
+
+| Component | Example | Purpose | Source |
+|-----------|---------|---------|---------|
+| **Base Tag** | `v3.1.3` | Latest semantic version release | Git tags |
+| **Commit Count** | `-5` | Development commits since release | Git history |
+| **Commit Hash** | `-gaac45b1` | Exact code state identifier | Git SHA |
+
+### **Version Extraction Workflow**
+
+#### **Production Builds** (Release & Main Branch)
+```bash
+# 1. Extract version outside Docker container (git access)
+VERSION=$(git describe --tags --always)
+
+# 2. Pass to containerized build via environment variable
+export RELEASE_VERSION="$VERSION"
+
+# 3. Container uses pre-extracted version (no git dependency)
+echo "Building with version: $RELEASE_VERSION"
+```
+
+#### **Development Builds** (Feature Branches)
+```bash
+# Similar process but with development-specific naming
+VERSION="${BASE_TAG}-dev-${SHORT_HASH}"
+
+# Example: v3.1.3-dev-aac45b1 for untagged development
+```
+
+### **Version Usage Across Workflows**
+
+| Workflow | Version Source | Format Example | Usage |
+|----------|---------------|----------------|-------|
+| **Release** | Git tags | `v3.1.3` | GitHub release naming, artifact tagging |
+| **Development** | Git describe | `v3.1.3-5-gaac45b1` | Build identification, artifact naming |
+| **Docker Image** | Git commits | `main-aac45b1` | Container tagging, cache keys |
+
+### **Traceability Benefits**
+
+- **🎯 Exact Reproduction**: Any build can be reproduced with the commit hash
+- **📋 Issue Debugging**: Full version context for troubleshooting
+- **🚀 Release Tracking**: Clear development progress between releases
+- **🔍 Artifact Linking**: Direct connection between builds and source code
+- **📊 Build Analytics**: Version-based performance and success tracking
+
+### **Integration with Documentation**
+
+- **HTML Headers**: Include version for user reference
+- **PDF Metadata**: Embed version for document tracking
+- **Build Logs**: Log version for debugging and audit trails
+- **Artifact Names**: Use version in downloadable package names
+
+This automated versioning ensures every BOOST documentation build has complete provenance tracking from source code to final deliverable.
+
 ## 🏷️ Release Documentation
 
 **File**: `.github/workflows/release.yml`  

CHANGELOG.md

@@ -2,7 +2,25 @@
 
 All notable changes to the BOOST data standard are documented in this file.
 
-## [3.1.3] - 2025-08-14 - Enhanced Unified Build System & CI/CD Pipeline
+## [3.1.3] - 2025-08-14 - Consolidated Build System with Git-Based Version Nomenclature
+
+### Added
+- **🏷️ Git-Based Version Nomenclature System** - Comprehensive automated versioning with complete traceability
+  - **Standard Format**: `v3.1.3-5-gaac45b1` providing base release, commit count, and exact commit hash
+  - **Automated Extraction**: Git describe-based version detection in all build processes
+  - **CI/CD Integration**: Version automatically extracted outside Docker containers and passed to builds
+  - **Complete Documentation**: Added comprehensive VERSION.md with format explanations and usage examples
+  - **Multi-Context Support**: Works in local development, CI/CD pipelines, and Docker environments
+- **📋 Consolidated Build System** - Single `build.sh` script replacing multiple build scripts
+  - **Flag Support**: `--html`, `--pdf`, `--help` flags for targeted builds
+  - **Enhanced LaTeX Error Detection**: Distinguishes critical errors from acceptable warnings
+  - **Comprehensive Validation**: Version management, dependency checking, and build statistics
+  - **Version Integration**: Automatic version placeholder replacement in all output formats
+- **📚 Version Documentation System** - Complete documentation coverage across all files
+  - **README.md**: Version nomenclature section with practical examples and traceability benefits
+  - **WORKFLOWS.md**: CI/CD version extraction and usage patterns 
+  - **Specifications README**: Build system version integration and debugging guidance
+  - **VERSION.md**: Comprehensive reference for all version-related functionality
 
 ### Enhanced
 - **Unified Build System Performance** - Optimized schema-to-LaTeX generation and PDF compilation
@@ -32,6 +50,17 @@ All notable changes to the BOOST data standard are documented in this file.
   - Fixed Docker image compatibility with enhanced LaTeX package requirements
 
 ### Technical Improvements
+- **Version Traceability Architecture** - Complete end-to-end version tracking system
+  - **Git Describe Integration**: Uses `git describe --tags --always` for precise version identification
+  - **Environment Variable Passing**: `RELEASE_VERSION` properly passed to Docker containers in CI/CD
+  - **Multi-Priority Detection**: Local development, CI/CD, and fallback version extraction methods
+  - **Documentation Integration**: Version information embedded in HTML headers, PDF metadata, and build logs
+  - **Exact Reproduction**: Any build can be reproduced using the commit hash from the version string
+- **Build Script Consolidation** - Eliminated redundant scripts and centralized functionality
+  - **Removed Scripts**: `build-all.sh`, `build-spec.sh`, `build-pdf.sh`, `build-unified.sh` (4 scripts removed)
+  - **Enhanced Error Handling**: LaTeX warnings classified as acceptable vs problematic with detailed reporting
+  - **Warning Analysis**: Pass-by-pass warning tracking (13→2→1 warnings) with final status summary
+  - **Build Validation**: Comprehensive consistency checking and statistics generation
 - **Build System Reliability** - Eliminated all LaTeX compilation errors for consistent PDF generation
   - **Error-Free Compilation**: Zero LaTeX errors in unified build system
   - **Complete Navigation**: TOC, LOT, and LOF properly generated in all builds

README.md

@@ -3,7 +3,7 @@
 ## Overview
 This repository contains the working draft and artifacts of the Biomass Open Origin Standard for Tracking (BOOST), which defines a robust and interoperable data model for tracking biomass through complex supply chains. The standard supports transparent, verifiable, and consistent data exchange to enable sustainability, regulatory compliance, and supply chain integrity.
 
-**Current Version: v3.0.3** - Docker containerized builds, automatic releases for all semantic versions, and comprehensive GitHub Actions workflow automation.
+**Current Version: v3.1.3** - Consolidated build system with enhanced LaTeX error detection, automated version management, and comprehensive GitHub Actions workflow automation.
 
 - **Charter:** [BOOST_Charter.org](BOOST_Charter.org)
 - **Charter Effective Date:** 
@@ -33,7 +33,7 @@ W3C Community Group page: [BOOST-01](https://www.w3.org/community/boost-01/)
 - **Supply Base Management** - Infrastructure mapping with harvest sites and transportation routes
 
 ### Comprehensive Entity System
-- **29 Interconnected Entities** - Complete data model covering all aspects of biomass supply chains across 7 thematic areas
+- **35 Interconnected Entities** - Complete data model covering all aspects of biomass supply chains across 7 thematic areas
 - **JSON-LD Validation** - Structured schemas with business rules and examples
 - **Interactive ERD Navigator** - Dynamic exploration with GitHub discussion integration
 - **Sustainability Claims** - Species-specific claims with inheritance through processing
@@ -63,11 +63,11 @@ W3C Community Group page: [BOOST-01](https://www.w3.org/community/boost-01/)
 ├── drafts/                  # Organized draft content
 │   ├── current/             # Active working content
 │   │   ├── specifications/        # Current spec documents
-│   │   ├── schema/               # Entity schemas and validation (29 entities)
+│   │   ├── schema/               # Entity schemas and validation (35 entities)
 │   │   │   ├── traceable_unit/        # Core TRU entity with examples
 │   │   │   ├── species_component/     # Multi-species tracking
 │   │   │   ├── material_processing/   # Processing operations
-│   │   │   └── [26 additional entities] # Complete BOOST Traceability System
+│   │   │   └── [32 additional entities] # Complete BOOST Traceability System
 │   │   ├── images/
 │   │   │   ├── current/              # Interactive ERD and current visuals
 │   │   │   └── archive/              # Historical ERD iterations and deprecated files
@@ -107,7 +107,7 @@ W3C Community Group page: [BOOST-01](https://www.w3.org/community/boost-01/)
 ## 🚀 Getting Started
 
 ### For Developers
-1. **Explore the Interactive ERD**: Use the [Interactive ERD Navigator](erd-navigator/index.html) to explore all 29 entities with dynamic filtering and GitHub discussion integration
+1. **Explore the Interactive ERD**: Use the [Interactive ERD Navigator](erd-navigator/index.html) to explore all 35 entities with dynamic filtering and GitHub discussion integration
 2. **Review Entity Schemas**: Check `drafts/current/schema/` for JSON validation schemas and examples
 3. **Review Schema Organization**: Check entity schemas in `drafts/current/schema/` for implementation details
 4. **Migration Guide**: See `drafts/current/specifications/MATERIALBATCH_TO_TRU_MIGRATION_GUIDE.md` for conceptual changes
@@ -128,7 +128,7 @@ W3C Community Group page: [BOOST-01](https://www.w3.org/community/boost-01/)
 The [Interactive ERD Navigator](erd-navigator/index.html) provides a comprehensive, stakeholder-friendly way to explore the BOOST data model:
 
 ### 🔍 Key Features
-- **29 Entity Coverage**: Complete visualization of all entities across 7 thematic areas
+- **35 Entity Coverage**: Complete visualization of all entities across 7 thematic areas
 - **Dynamic Filtering**: Focus on specific domains (Core Traceability, Organizational, Material & Supply, etc.)
 - **Direct Discussion Access**: Purple 💬 icons in each entity header link directly to GitHub discussions
 - **TraceableUnit Focus Mode**: 🎯 button to reduce visual complexity and highlight essential relationships
@@ -157,11 +157,74 @@ Each entity has a dedicated GitHub discussion thread accessible via the ERD. Thi
 
 - **✅ Complete**: BOOST Traceability System Phases 1-3 implementation
 - **✅ Complete**: Plant part categorization system 
-- **✅ Complete**: 29 entity schemas with validation and examples
+- **✅ Complete**: 35 entity schemas with validation and examples
 - **✅ Complete**: Interactive ERD Navigator with GitHub discussion integration
 - **✅ Complete**: Integration testing scenarios and migration documentation
 - **🔄 Active**: Community feedback integration and use case expansion
 
+## 🏷️ Version Nomenclature
+
+BOOST uses Git-based semantic versioning with development build identification. Understanding the version format is essential for tracking releases and development progress.
+
+### Version Format: `v3.1.3-5-gaac45b1`
+
+All BOOST versions follow the **Git describe** format, providing precise traceability:
+
+#### **Components Breakdown:**
+
+1. **`v3.1.3`** - **Base Release Tag**
+   - Latest official release using semantic versioning (Major.Minor.Patch)
+   - Example: `v3.1.3` represents a patch release in the 3.1.x series
+
+2. **`-5`** - **Commits Since Release** 
+   - Number of commits made since the base release tag
+   - Indicates this is a **development build**, not an official release
+   - Higher numbers = more development activity since last release
+
+3. **`-g`** - **Git Indicator**
+   - Standard Git convention indicating the following is a commit hash
+   - The "g" stands for "git"
+
+4. **`aac45b1`** - **Commit Hash (Short)**
+   - 7-character abbreviated SHA hash of the specific commit
+   - Uniquely identifies the exact code state used for this build
+   - Full hash is longer (e.g., `aac45b1a2b3c4d5e6f7g8h9i0j1k2l3m4n5o6p7q`)
+
+### **Version Types:**
+
+| Format | Type | Description | Example |
+|--------|------|-------------|---------|
+| `v3.1.3` | **Release** | Official tagged release | Stable, production-ready |
+| `v3.1.3-5-gabc123` | **Development** | 5 commits after v3.1.3 | In-progress development |
+| `v3.2.0-1-gdef456` | **Post-Release** | 1 commit after new release | Latest development |
+
+### **Development Build Evolution:**
+
+```
+v3.1.3           ← Official release (tagged)
+v3.1.3-1-g0057230 ← 1 commit after release  
+v3.1.3-2-gca1a0c6 ← 2 commits after release
+v3.1.3-3-g2615374 ← 3 commits after release
+v3.1.3-4-gfe2beb4 ← 4 commits after release  
+v3.1.3-5-gaac45b1 ← 5 commits after release (current example)
+```
+
+### **Practical Usage:**
+
+- **🎯 Exact Reproduction**: Any version can be reproduced with `git checkout <commit-hash>`
+- **📋 Issue Reporting**: Always include full version for accurate debugging
+- **🚀 Release Planning**: Development versions show progress toward next release
+- **🔍 Build Tracking**: CI/CD systems use this for automated version management
+
+### **In Documentation Builds:**
+
+- **HTML/PDF Headers**: Show exact version used for generation
+- **Build Logs**: Include version for reproducibility tracking  
+- **Release Artifacts**: Tagged with precise version information
+- **GitHub Actions**: Automatically extract and use for build naming
+
+This versioning system ensures **complete traceability** - you can always identify the exact code state that generated any documentation build or release artifact.
+
 ## 🤖 Automated CI/CD Workflows
 
 The BOOST repository includes comprehensive GitHub Actions automation for documentation building, validation, and release management.