mirror of
https://github.com/hoshikawa2/rfp_response_automation.git
synced 2026-03-03 16:09:35 +00:00
first commit
This commit is contained in:
@@ -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
|
||||
|
||||
Reference in New Issue
Block a user