cristiano.hoshikawa/rfp_response_automation
1
0
Fork 0
mirror of https://github.com/hoshikawa2/rfp_response_automation.git synced 2026-03-06 02:10:41 +00:00
Code Issues Packages Projects Releases Wiki Activity

first commit

Browse Source
This commit is contained in:
Cristiano Hoshikawa
2026-01-13 22:51:39 -03:00
parent 8424c42d1a
commit 4e69ce6174
1 changed files with 0 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
files/graphrag_rerank.py
View File

@@ -667,9 +667,6 @@ def chat():
Service scope rules (MANDATORY): Service scope rules (MANDATORY):
- Evidence is valid ONLY if it refers to the SAME service category as the requirement. - 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. - 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): OUTPUT CONSTRAINTS (MANDATORY):
- Return ONLY a valid JSON object - Return ONLY a valid JSON object
@@ -840,9 +837,6 @@ Ambiguity rules:
Service scope rules (MANDATORY): Service scope rules (MANDATORY):
- Evidence is valid ONLY if it refers to the SAME service category as the requirement. - 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. - 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): OUTPUT CONSTRAINTS (MANDATORY):
- Return ONLY a valid JSON object - Return ONLY a valid JSON object