Xook — your grounded assistant
A cited assistant over your own published knowledge that refuses anything it can't ground, and turns every refusal into a content gap.
- Answers come only from the collections you publish — with citations
- Anything the assistant can't ground becomes an answer gap you can close
- A go-live eval proves it refuses out-of-corpus questions before learners see it
- Internal collections are never shown to a learner
Grounded, cited, honest
Xook answers questions using only your published knowledge, and cites what it used. When the material doesn't support an answer, it refuses rather than guesses — and records the question as an answer gap so you can close it.
Every Xook surface is marked Powered by Xook Pie.
Visibility is the guardrail
Each collection is published, internal, or partner. A learner-facing assistant retrieves from published collections only. Internal collections are filtered out before retrieval runs — a learner can never be shown internal material.
The go-live eval
Before you expose an assistant, run the go-live eval: a set of probe questions. Questions you prefix with ! are out-of-corpus and must be refused. The assistant passes only when its must-refuse rate is perfect and its grounding clears the bar.
The answer-gap loop
Refusals and low-confidence answers become answer gaps. Work the backlog: improve the documentation behind each gap, and the assistant improves with it. Xook reports documentation coverage — it is not an accreditation and says nothing about a person's competence.
Frequently asked
Where do the answers come from?
Only from the collections you attach to an assistant, retrieved and cited at answer time. Xook is instructed to answer strictly from that context and to refuse — never guess — when the context does not support an answer. Every answer carries the 'Powered by Xook Pie' mark.
Can a learner ever see internal material?
No. Each collection has a visibility — published, internal or partner. A learner-facing assistant retrieves only from published collections; internal collections are filtered out before retrieval runs, server-side, and are never returned. This is enforced in the database and in code, not just the interface.
What is an answer gap?
When Xook has to refuse or is unsure, it records the question as an answer gap — the backlog of things your documentation does not yet cover well. Closing gaps (by improving the underlying content) is how the assistant gets better over time.
What is the go-live eval?
A quick suite of probe questions you run against an assistant before exposing it. It scores two things: whether out-of-corpus questions are correctly refused (which must be perfect) and whether answerable questions are grounded and cited. Both must clear their bar for the assistant to pass.
Is a Xook answer a qualification?
No. Xook answers questions from your documentation. It is not an accreditation and makes no claim about any person's competence.
Related guides
Declare agents over your knowledge and learning ops. Every run is recorded and gated; content changes need a human approval; the execution runtime is not yet wired.
ReadRun your organization's people, teams, invitations and domains from one control plane.
Read