Atlas Gateway
Waiting on youllm.atlas.internal / atlas-core · LiteLLM · https://llm.atlas.internal · europe-west4
Waiting on you. 6 workloads discovered — merge, split and name them before this connector is usable. Open discovery →
Context questionnaire
Asked here, at registration — not mid-assessment
Every question names the downstream decision it can flip. A question that cannot change a decision is not asked. Answers record their basis, and “I don't know” is a first-class answer that travels to the report as a declared gap rather than a silent default.
4 questions · 0 answered · 0 recorded as a gap
Is there a response-time SLA on any application here?
What this flips: Sets the latency gate threshold in stage C. Without it, latency is not gated at all.
Expected traffic growth over the next 12 months?
What this flips: Projections carry a growth midpoint if answered, and a range if not.
Which data region must analysis stay within?
What this flips: Pins the connector's residency and blocks replay against models not served there.
Are any deployments fine-tuned or distilled from a base model?
What this flips: Routes those workloads to specialist referral instead of a recommendation.