# VM0033 Integration > System for leveraging existing VM0033 documentation and requesting only Guardian-specific implementation details ## Overview This system ensures accurate VM0033 references by: 1. **Using existing parsed documentation** in `docs/VM0033-methodology-pdf-parsed/` for basic methodology questions 2. **Requesting user input only** for Guardian-specific implementation details, screenshots, and current system status ## Available VM0033 Documentation ### Parsed VM0033 Content The system can access comprehensive VM0033 methodology content from: * `docs/VM0033-methodology-pdf-parsed/VM0033-Methodology.md` - Full methodology text * `docs/VM0033-methodology-pdf-parsed/VM0033-Methodology_meta.json` - Structured metadata and table of contents ### What NOT to Ask Users **Basic methodology information available in parsed docs:** * VM0033 definitions and terminology * Applicability conditions and scope * Baseline scenario determination procedures * Carbon pools and GHG sources * Monitoring requirements and parameters * Mathematical formulas and calculations * Tool relationships (AR-Tool02, AR-Tool03, AR-Tool14) * Blue carbon significance and methodology overview * Temporal and geographic boundaries * Stratification requirements ### User Input Required For #### Guardian Implementation Details * [ ] Current Guardian VM0033 implementation status * [ ] Guardian UI screenshots showing VM0033 features * [ ] Guardian architecture diagrams for VM0033 * [ ] Specific Guardian configuration examples * [ ] Guardian API endpoints used for VM0033 * [ ] Guardian database schema for VM0033 data * [ ] Guardian workflow implementations * [ ] Guardian user role configurations for VM0033 #### Development Environment & Setup * [ ] Current development environment requirements * [ ] Installation and setup procedures * [ ] Guardian-specific VM0033 configuration files * [ ] Testing procedures and validation scripts * [ ] Deployment considerations #### Real Implementation Examples * [ ] Actual Guardian VM0033 project examples * [ ] User experience challenges with Guardian implementation * [ ] Performance considerations and optimizations * [ ] Integration issues and solutions ## Content Integration Guidelines ### Using VM0033 Parsed Documentation **For methodology content, reference the parsed documentation directly:** ```markdown According to VM0033 Section 3 (Definitions), a "Tidal Wetland" is defined as: [Reference: docs/VM0033-methodology-pdf-parsed/VM0033-Methodology.md] VM0033 applicability conditions (Section 4) specify that projects must: [Reference: docs/VM0033-methodology-pdf-parsed/VM0033-Methodology.md] ``` ### Guardian Implementation Request Template **Only use this template for Guardian-specific details:** ```markdown ## Guardian Implementation Detail Needed **Chapter**: [Chapter Number and Title] **Section**: [Specific Section] **Guardian Feature**: [Specific Guardian capability or implementation] **Required Information**: - [ ] Current implementation status in Guardian - [ ] Screenshots of Guardian interface - [ ] Configuration files or code examples - [ ] API endpoints or database schema - [ ] User workflow in Guardian system **Context**: How this Guardian implementation supports VM0033 methodology **Note**: Basic VM0033 methodology details will be referenced from parsed documentation ``` ## Content Validation System ### VM0033 Content Integration Checklist For each VM0033 reference: * [ ] **Basic methodology content**: Referenced from parsed documentation (`docs/VM0033-methodology-pdf-parsed/`) * [ ] **Specific section citations**: Include section numbers and page references * [ ] **Guardian implementation**: User input obtained for system-specific details only * [ ] **Context appropriate**: Content serves both maintenance and learning audiences * [ ] **No assumptions**: No hallucinated methodology details ### Guardian Integration Checklist For each Guardian reference: * [ ] **Current status confirmed**: Implementation status verified with user * [ ] **Screenshots obtained**: Current Guardian interface examples from user * [ ] **Code examples validated**: Guardian-specific configurations from user * [ ] **Documentation links**: References to existing Guardian documentation * [ ] **Feature availability**: Current Guardian capabilities confirmed ## Implementation Guidelines ### Content Creation Process 1. **Check Parsed Documentation**: First, check if VM0033 information is available in parsed docs 2. **Reference Methodology Content**: Use parsed documentation for basic methodology details 3. **Identify Guardian Gaps**: Determine what Guardian-specific information is needed 4. **Request Guardian Details**: Use templates to request only Guardian implementation details 5. **Integrate Content**: Combine methodology references with Guardian implementation 6. **Quality Check**: Ensure no methodology assumptions or hallucinations ### Content Integration Examples ```markdown ## VM0033 Baseline Scenarios According to VM0033 Section 6.1 "Determination of the Most Plausible Baseline Scenario", the methodology requires [specific requirements from parsed documentation]. {% hint style="info" %} **Guardian Implementation**: The following shows how Guardian implements VM0033 baseline scenario determination. {% endhint %} [USER INPUT NEEDED: Guardian screenshots and configuration for baseline scenario implementation] [USER INPUT NEEDED: What are VM0033 baseline scenario requirements?] ``` ### Methodology Reference Pattern ```markdown **VM0033 Reference**: Section [X.X] - [Section Title] **Source**: `docs/VM0033-methodology-pdf-parsed/VM0033-Methodology.md` **Content**: [Direct reference to methodology requirements] **Guardian Implementation**: [USER INPUT NEEDED: How Guardian implements this VM0033 requirement] ``` ## Quality Assurance ### Content Review Process 1. **Methodology Source Check**: VM0033 content referenced from parsed documentation 2. **Guardian Input Validation**: Guardian-specific details obtained from user input only 3. **Documentation Integration**: Guardian references link to existing documentation 4. **Accuracy Check**: No methodology assumptions or hallucinations 5. **Completeness Review**: All Guardian implementation details obtained ### Error Prevention * **Use Parsed Documentation**: Always check VM0033 parsed docs before asking users * **No Methodology Assumptions**: Never assume or hallucinate VM0033 content * **Guardian-Specific Requests**: Only request Guardian implementation details from users * **Source Attribution**: Always reference specific VM0033 sections from parsed docs * **Clear Boundaries**: Distinguish between methodology content and Guardian implementation ### Common Mistakes to Avoid ❌ **Wrong**: Asking user "What does VM0033 say about blue carbon?" ✅ **Right**: Reference VM0033 parsed documentation for blue carbon definition ❌ **Wrong**: Asking user "What are VM0033 applicability conditions?" ✅ **Right**: Reference Section 4 of parsed VM0033 documentation ❌ **Wrong**: Assuming Guardian implementation details ✅ **Right**: Request specific Guardian screenshots and configurations from user ## Maintenance ### Ongoing Updates * **VM0033 Changes**: System for handling methodology updates * **Guardian Updates**: Process for updating Guardian references * **User Feedback**: Integration of user corrections and improvements * **Documentation Sync**: Keeping Guardian documentation references current ### Version Control * **Content Versioning**: Track changes to user-provided content * **Reference Updates**: Maintain current links to Guardian documentation * **Accuracy Tracking**: Monitor and update VM0033 references as needed *** {% hint style="success" %} **Key Principle**: Use existing VM0033 parsed documentation for methodology content. Only request Guardian-specific implementation details from users. {% endhint %} {% hint style="warning" %} **Critical Requirement**: Never ask users for basic VM0033 methodology information that's already available in the parsed documentation. This prevents unnecessary interruptions and ensures efficient content creation. {% endhint %}