A support ticket moves through eight explicit stages. Each stage narrows what the system is allowed to do, and every decision remains visible after the run.
Approved Markdown is split by heading, chunked, embedded, and upserted into Postgres. Each run receives a corpus version that follows every citation.
Approved Markdown is split by heading, chunked, embedded, and upserted into Postgres. Each run receives a corpus version that follows every citation. This behavior is exercised by the guided demo and recorded in its audit history.
A fast deny-list and a small classifier separate genuine questions from off-topic or manipulative requests before retrieval, generation, or a costly database write.
A fast deny-list and a small classifier separate genuine questions from off-topic or manipulative requests before retrieval, generation, or a costly database write. This behavior is exercised by the guided demo and recorded in its audit history.
The ticket is embedded and compared with every indexed passage. Ranked passages return with similarity scores and stable IDs; retrieval alone never decides that a question is answered.
The ticket is embedded and compared with every indexed passage. Ranked passages return with similarity scores and stable IDs; retrieval alone never decides that a question is answered. This behavior is exercised by the guided demo and recorded in its audit history.
The model drafts only from retrieved passages, leaves the answer empty when support is missing, and is explicitly warned not to conflate adjacent policy concepts.
The model drafts only from retrieved passages, leaves the answer empty when support is missing, and is explicitly warned not to conflate adjacent policy concepts. This behavior is exercised by the guided demo and recorded in its audit history.
The draft is decomposed into factual claims. Each claim receives an entailment score plus a lexical sanity check so one weak statement cannot hide inside an otherwise grounded answer.
The draft is decomposed into factual claims. Each claim receives an entailment score plus a lexical sanity check so one weak statement cannot hide inside an otherwise grounded answer. This behavior is exercised by the guided demo and recorded in its audit history.
Verified drafts become cited answers. Missing or ambiguous evidence goes to human review. Unsafe instructions remain blocked before the answer pipeline begins.
Verified drafts become cited answers. Missing or ambiguous evidence goes to human review. Unsafe instructions remain blocked before the answer pipeline begins. This behavior is exercised by the guided demo and recorded in its audit history.
Customer sending is simulated, while the inbox and optional Slack notification carry evidence, reason, and approve or reject controls into the operator workflow.
Customer sending is simulated, while the inbox and optional Slack notification carry evidence, reason, and approve or reject controls into the operator workflow. This behavior is exercised by the guided demo and recorded in its audit history.
Every stage writes a persisted event. A committed 45-case development suite runs the same pipeline and reports route accuracy, false refusal, and fabrication by category.
Every stage writes a persisted event. A committed 45-case development suite runs the same pipeline and reports route accuracy, false refusal, and fabrication by category. This behavior is exercised by the guided demo and recorded in its audit history.
The verifier initially allowed a liability passage to support an insurance-coverage claim. The development suite exposed the concept conflation, leading to stricter generation and entailment instructions.
Submit a support question and watch the system screen, retrieve, verify, and select a responsible route.
Run the demo ↗