29 lines
1.6 KiB
Markdown
29 lines
1.6 KiB
Markdown
## MODIFIED Requirements
|
|
|
|
### Requirement: Endpoint resolves exactly one tool-call decision using cloud-held provider configuration
|
|
The Cloud Control Plane SHALL use its own configured LLM provider, model, and
|
|
credentials -- not any value supplied by the requesting Host Agent -- to
|
|
resolve a planner-decision request to exactly one tool name and one arguments
|
|
object, within the request's timeout. The endpoint SHALL resolve the active
|
|
database-managed Provider profile for every request and use its provider,
|
|
model, timeout, OpenAI-compatible base URL when applicable, and encrypted
|
|
cloud-held credential. It SHALL NOT read Cloud API planner Provider/model/
|
|
timeout/API-key environment variables.
|
|
|
|
#### Scenario: Provider returns a usable decision
|
|
- **WHEN** the configured provider responds to a planner-decision request
|
|
with a tool call
|
|
- **THEN** the Cloud Control Plane returns exactly one resolved tool name
|
|
and arguments object to the requesting Host Agent
|
|
|
|
#### Scenario: Configured provider is unreachable or misconfigured
|
|
- **WHEN** the Cloud Control Plane's configured provider call fails (for
|
|
example, invalid credentials, provider error, or timeout)
|
|
- **THEN** the endpoint returns a structured failure response rather than a
|
|
fabricated decision, and does not crash the Cloud Control Plane process
|
|
|
|
#### Scenario: Database profile is the only planner configuration source
|
|
- **WHEN** the Cloud API process has legacy planner environment variables
|
|
- **THEN** subsequent planner-decision requests use only the active database
|
|
profile and do not read a legacy Provider credential for that decision
|