Test 1

business_continuity.py

@@ -122,56 +122,26 @@ class RecoveryStrategiesResponse(BaseModel):
 def clean_json_response(response_text: str) -> str:
     """Clean and extract JSON from API response"""
     logger.info("Cleaning JSON response")
-    
     if not response_text:
         logger.error("Empty response text provided")
         raise ValueError("Empty response text")
-    
-    # Remove common markdown formatting
     cleaned = response_text.strip()
-    
-    # Remove code blocks more aggressively
     patterns = [
-        r'```json\s*',          # Matches opening fence with optional spaces after ```json
-        r'```',                 # Matches closing or generic triple backticks
+        r'```json\s*',
+        r'```',
     ]
     for pattern in patterns:
         cleaned = re.sub(pattern, '', cleaned, flags=re.MULTILINE | re.DOTALL)
-    
     cleaned = cleaned.strip()
-    
-    # Try to find complete JSON by counting braces
-    json_start = cleaned.find('{')
-    if json_start == -1:
-        logger.error(f"No opening brace found. Response preview: {cleaned[:300]}...")
-        raise ValueError("No JSON opening brace found in response")
-    
-    # Count braces to find the matching closing brace
-    brace_count = 0
-    json_end = -1
-    
-    for i in range(json_start, len(cleaned)):
-        if cleaned[i] == '{':
-            brace_count += 1
-        elif cleaned[i] == '}':
-            brace_count -= 1
-            if brace_count == 0:
-                json_end = i
-                break
-    
-    if json_end == -1:
-        logger.error(f"No matching closing brace found. Response preview: {cleaned[:500]}...")
-        # Try using the last closing brace as fallback
-        json_end = cleaned.rfind('}')
-        if json_end == -1 or json_end <= json_start:
-            raise ValueError("No valid JSON structure found in response")
-    
-    json_str = cleaned[json_start:json_end + 1]
+    # Use regex to extract the first valid JSON object
+    match = re.search(r'\{[\s\S]*\}', cleaned)
+    if not match:
+        logger.error(f"No JSON object found. Response preview: {cleaned[:300]}...")
+        raise ValueError("No JSON object found in response")
+    json_str = match.group(0)
     logger.info(f"Extracted JSON length: {len(json_str)}")
     logger.info(f"JSON preview: {json_str[:150]}...")
     logger.info(f"JSON ending: ...{json_str[-50:]}")
-    
-    # Validate that it's at least syntactically correct JSON
     try:
         json.loads(json_str)
         logger.info("JSON syntax validation passed")
@@ -179,7 +149,6 @@ def clean_json_response(response_text: str) -> str:
         logger.error(f"JSON syntax validation failed: {str(e)}")
         logger.error(f"Problematic JSON: {json_str}")
         raise ValueError(f"Invalid JSON syntax: {str(e)}")
-    
     return json_str
 
 
@@ -262,23 +231,26 @@ def generate_recovery_strategies(request: BusinessContinuityRequest):
         
         system_prompt = """You are an expert business continuity consultant. Your task is to generate specific, actionable recovery strategies for business processes.
 
-CRITICAL INSTRUCTIONS:
-1. Respond with ONLY a valid JSON object
-2. Do not include any markdown formatting, code blocks, or additional text
-3. Each strategy must be 2-3 detailed sentences with specific actionable steps
-4. Each reasoning must be 1-2 sentences explaining why the strategy fits the specific process
+**CRITICAL INSTRUCTIONS:**
+1.  **MUST** respond with a single, valid JSON object and nothing else.
+2.  The JSON object must be the only content in your response. Do not include any text, explanations, or markdown formatting (like ```json) before or after the JSON object.
+3.  Ensure the JSON is perfectly formed with correct syntax, including matching curly braces, quoted keys, and properly escaped string values.
+4.  Each strategy must be 2-3 detailed sentences with specific, actionable steps.
+5.  Each reasoning must be 1-2 sentences explaining why the strategy fits the specific process.
 
-Required JSON format (no deviations allowed):
+**Required JSON format (no deviations allowed):**
+```json
 {
-  "people_unavailability_strategy": "Detailed strategy for handling personnel unavailability with specific steps",
-  "people_reasoning": "Clear explanation of why this strategy suits this specific process",
-  "technology_data_unavailability_strategy": "Comprehensive strategy for technology and data failures with actionable steps",
-  "technology_reasoning": "Explanation of why this technology strategy is appropriate for this process",
-  "site_unavailability_strategy": "Detailed strategy for site/facility unavailability with specific actions",
-  "site_reasoning": "Why this site strategy is suitable for this specific process",
-  "third_party_vendors_unavailability_strategy": "Comprehensive strategy for vendor/supplier disruptions",
-  "vendor_reasoning": "Why this vendor strategy is appropriate for this process"
-}"""
+  "people_unavailability_strategy": "Detailed strategy for handling personnel unavailability with specific steps.",
+  "people_reasoning": "Clear explanation of why this strategy suits this specific process.",
+  "technology_data_unavailability_strategy": "Comprehensive strategy for technology and data failures with actionable steps.",
+  "technology_reasoning": "Explanation of why this technology strategy is appropriate for this process.",
+  "site_unavailability_strategy": "Detailed strategy for site/facility unavailability with specific actions.",
+  "site_reasoning": "Why this site strategy is suitable for this specific process.",
+  "third_party_vendors_unavailability_strategy": "Comprehensive strategy for vendor/supplier disruptions.",
+  "vendor_reasoning": "Why this vendor strategy is appropriate for this process."
+}
+```"""
 
         user_message = f"""Generate business continuity recovery strategies for this specific process: