From 4e69ce6174e5e07ac4a2630868b5f0fb276ae205 Mon Sep 17 00:00:00 2001 From: Cristiano Hoshikawa Date: Tue, 13 Jan 2026 22:51:39 -0300 Subject: [PATCH] first commit --- files/graphrag_rerank.py | 6 ------ 1 file changed, 6 deletions(-) diff --git a/files/graphrag_rerank.py b/files/graphrag_rerank.py index 9ba141d..320b455 100644 --- a/files/graphrag_rerank.py +++ b/files/graphrag_rerank.py @@ -667,9 +667,6 @@ def chat(): 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 @@ -840,9 +837,6 @@ Ambiguity rules: 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