diff --git a/files/graphrag_rerank.py b/files/graphrag_rerank.py
index 3730bec..95fc12c 100644
--- a/files/graphrag_rerank.py
+++ b/files/graphrag_rerank.py
@@ -637,6 +637,13 @@ def chat():
       - Keywords are vague (e.g. "support", "integration", "capability")
       - Evidence does not clearly bind to subject + expected value
     
+    Service scope rules (MANDATORY):
+    - Evidence is valid ONLY if it refers to the SAME service category as the requirement.
+    - Do NOT use evidence from a different Oracle Cloud service to justify another.
+    - PaaS services (e.g. Autonomous Database) MUST NOT be used as evidence for IaaS/Compute requirements.
+    - If the requirement is under Compute/IaaS, evidence MUST explicitly mention Compute, IaaS, VM, Bare Metal, or equivalent infrastructure services.
+    - Cross-service inference (vendor-level capability applied to another service) is strictly forbidden.
+    
     OUTPUT CONSTRAINTS (MANDATORY):
     - Return ONLY a valid JSON object
     - Do NOT include explanations, comments, markdown, lists, or code fences
@@ -803,6 +810,13 @@ Ambiguity rules:
   - Keywords are vague (e.g. "support", "integration", "capability")
   - Evidence does not clearly bind to subject + expected value
 
+Service scope rules (MANDATORY):
+- Evidence is valid ONLY if it refers to the SAME service category as the requirement.
+- Do NOT use evidence from a different Oracle Cloud service to justify another.
+- PaaS services (e.g. Autonomous Database) MUST NOT be used as evidence for IaaS/Compute requirements.
+- If the requirement is under Compute/IaaS, evidence MUST explicitly mention Compute, IaaS, VM, Bare Metal, or equivalent infrastructure services.
+- Cross-service inference (vendor-level capability applied to another service) is strictly forbidden.
+
 OUTPUT CONSTRAINTS (MANDATORY):
 - Return ONLY a valid JSON object
 - Do NOT include explanations, comments, markdown, lists, or code fences