Spaces:
Running
Running
Commit History
-
Fix eval judges and publish first scorecard results Running
- Relevance and groundedness judges now see the full retrieved context; they were given truncated excerpts and penalized grounded answers - Correct two reference answers against the docs: full backups are kept 90 days (not 7), and stop-writes thresholds are documented - Add results/eval_results.json: correctness 84%, groundedness 92%, retrieval relevance 87%, out-of-scope handling 100% Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>bb393d8 -
Fix OOM on startup ingest; halve analysis latency; add About modal
- Embed SPLADE 4 chunks at a time during ingest: the default batch ran the HF container past its 16 GB limit (now peaks ~3 GB); allow a 1h startup for the first boot after a docs change - Extract questions and triage in two parallel calls so research starts ~5s in; shorter triage fields and ~150-word answers (29.7s -> 14.6s end to end in local Docker, 5.1c -> 4.3c per analysis) - Reply drafts are plain text with no markdown - Load backend/.env.local for local runs - About modal: how the pipeline works, hosting and budget limits, privacy Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>bdf34b2 -
Rebrand as Halyard Cloud ticket analyzer; add triage, replies and personas
Branding - Replace Aerospike with the fictional Halyard Cloud product across the UI, prompts, eval set and scraped docs; drop source URLs and the crawl index - Rename the HF Space to tomeese/support-ticket-analyzer in both workflows Fixes - Spend cap: always record spend, block the next request once over the cap - start.sh: ingest fallback never ran under set -e; also re-ingest when the docs fingerprint stored in Qdrant doesn't match the docs folder - Run endpoints in the threadpool and answer questions concurrently - Structured outputs for triage, answers and the eval judge - Input size limits; remove the unused /chat endpoint and chat UI - Pin dependencies; embed with fastembed (ONNX) instead of PyTorch Features - Customer persona (account, experience, mood) shapes triage and replies - Triage card: severity, category, sentiment, escalation - Streamed progress, "needs review" flag from documentation coverage - Clickable citations with a source viewer that highlights the passage …d0954af
-
UX updates.
swapped out chroma_db for qdrant. Added w&b1d67421