Add advanced-rag module: Easy RAG, query compression and expansion, routing, minScore, content injection, chat-memory cost and sources, each with a captured transcript
Co-Authored-By: Claude Sonnet 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_017ic4b85ApxQRK2Z8yuzC5r
This commit is contained in:
@@ -0,0 +1,51 @@
|
||||
Off-topic: What is the capital of France?
|
||||
minScore 0.0 (default):
|
||||
0.696 deployments.txt
|
||||
0.670 rate-limits.txt
|
||||
0.669 account-security.txt
|
||||
minScore 0.75:
|
||||
(nothing)
|
||||
|
||||
Message sent to the LLM with minScore 0.0:
|
||||
What is the capital of France?
|
||||
|
||||
Answer using the following information:
|
||||
Acme Cloud Deployments
|
||||
|
||||
A standard deployment takes about 4 minutes from push to live. The first 5 percent of traffic goes to the new version as a canary for 2 minutes before the rest is shifted.
|
||||
|
||||
A rollback takes about 30 seconds because the previous version stays warm for one hour after every deployment. After that hour, a rollback is a normal 4 minute deployment of the older build.
|
||||
|
||||
Deployments are blocked automatically when the error rate of the canary is more than 2 percent above the baseline.
|
||||
|
||||
Acme Cloud API Rate Limits
|
||||
|
||||
Every API key is limited to 600 requests per minute, with a burst allowance of 100 requests per second. Requests over the limit receive HTTP 429 with a Retry-After header giving the number of seconds to wait.
|
||||
|
||||
Limits are per key, not per organisation, so a noisy integration cannot starve the others. Batch endpoints count as one request regardless of how many items they contain.
|
||||
|
||||
To raise a limit, open a ticket with the key id and the peak traffic you expect. Increases are applied within one business day.
|
||||
|
||||
Acme Cloud Account Security
|
||||
|
||||
Password reset links expire after 30 minutes and can be used only once. If a link has expired, request a new one from the sign-in page.
|
||||
|
||||
Two-factor authentication is mandatory for organisation owners. Supported methods are authenticator apps and hardware security keys. SMS codes are not supported.
|
||||
|
||||
SSO via SAML 2.0 is available on the Business plan. After SSO is enforced, password sign-in is disabled for every member except the organisation owner, who keeps a break-glass login.
|
||||
|
||||
Message sent to the LLM with minScore 0.75:
|
||||
What is the capital of France?
|
||||
|
||||
On-topic: How long does a refund take to show up on my card?
|
||||
minScore 0.0:
|
||||
0.906 refund-policy.txt
|
||||
0.868 hardware-returns.txt
|
||||
0.782 webhooks.txt
|
||||
minScore 0.75:
|
||||
0.906 refund-policy.txt
|
||||
0.868 hardware-returns.txt
|
||||
0.782 webhooks.txt
|
||||
minScore 0.85:
|
||||
0.906 refund-policy.txt
|
||||
0.868 hardware-returns.txt
|
||||
Reference in New Issue
Block a user