van-qa-main

VAN MODE: QA TECHNICAL VALIDATION (Main Entry)

TL;DR: This is the entry point for the QA validation process that executes after CREATIVE mode and before BUILD mode. It ensures technical requirements are met before implementation begins.

📣 HOW TO USE THESE QA RULES

To access any QA validation rule or component, use the fetch_rules tool with exact rule names:

// CRITICAL: Always use fetch_rules to load validation components
// For detailed examples and guidance, load:
// isolation_rules/visual-maps/van-qa-utils/rule-calling-guide

🚀 VAN QA MODE ACTIVATION

After completing CREATIVE mode, when the user types "VAN QA", respond:

graph TD
    UserQA["User Types: QA"] --> HighPriority["⚠️ HIGH PRIORITY COMMAND"]
    HighPriority --> CurrentTask["Pause Current Task/Process"]
    CurrentTask --> LoadQA["Load QA Main Map (This File)"]
    LoadQA --> RunQA["Execute QA Validation Process"]
    RunQA --> QAResults{"QA Results"}
    
    QAResults -->|"PASS"| ResumeFlow["Resume Prior Process Flow"]
    QAResults -->|"FAIL"| FixIssues["Fix Identified Issues"]
    FixIssues --> ReRunQA["Re-run QA Validation"]
    ReRunQA --> QAResults
    
    style UserQA fill:#f8d486,stroke:#e8b84d,color:black
    style HighPriority fill:#ff0000,stroke:#cc0000,color:white,stroke-width:3px
    style LoadQA fill:#4da6ff,stroke:#0066cc,color:white
    style RunQA fill:#4da6ff,stroke:#0066cc,color:white
    style QAResults fill:#f6546a,stroke:#c30052,color:white

QA Interruption Rules

1. Immediate Precedence: QA command interrupts everything.
2. Load & Execute: Load this map (van-qa-main.mdc) and its components (see below).
3. Remediation Priority: Fixes take priority over pending mode switches.
4. Resume: On PASS, resume the previous flow.

⚠️ QA OVERRIDE ACTIVATED
All other processes paused
QA validation checks now running...
Any issues found MUST be remediated before continuing with normal process flow

🔍 TECHNICAL VALIDATION OVERVIEW