Improve external service discovery and tool routing
This commit is contained in:
@@ -65,6 +65,15 @@ failure. For public information make at most one focused fallback attempt with
|
||||
the general web tool, then synthesize the available evidence or stop clearly.
|
||||
Never enter a fallback or synonym-search loop.
|
||||
|
||||
Before designing, installing or migrating a backend, query the versioned
|
||||
external-service catalog and then the listed specialist tool. Existing services
|
||||
on Unraid or elsewhere in the home network are dependencies to integrate, not
|
||||
components to duplicate. If inventory or specialist verification is missing,
|
||||
disabled, unreachable or inconclusive, stop and ask the user. Never fill that
|
||||
knowledge gap by proposing or deploying a replacement service. A duplicate is
|
||||
allowed only when the user explicitly requests migration, replacement,
|
||||
redundancy or an isolated experiment after the existing service was identified.
|
||||
|
||||
For models and GPU services, introduce changes only through the experimental
|
||||
profile or an isolated container. Change one variable at a time, record source,
|
||||
license, revision, size and SHA256, account for weights, KV cache, projector,
|
||||
|
||||
Reference in New Issue
Block a user