How source citations work in creekX Agents
Follow the source, not just the number
Evidence chunks retain source identifiers, offsets, content hashes and reproducible chunk IDs. Responses include numbered citations. An operator can inspect the material in the published snapshot rather than guessing which later document revision a customer saw. Review both the excerpt and the source metadata before accepting a response.
Provenance is not factual correctness
Evidence mode quotes excerpts from up to two distinct sources; it does not synthesize a model answer. A matching chunk can still contain obsolete advice, omit a condition or describe another product. A citation establishes where the text came from. It does not independently prove relevance, factual accuracy or permission to disclose the material.
Offsets refer to saved text
Start and end values are UTF-16 indices in the saved source text, not bytes or line numbers. Keep the profile version and source hash in the review record. A matching title alone is insufficient because a title can stay the same across major edits. Compare an old response against its snapshot before comparing it against the current source.
Test the boundary
Ask a supported question, inspect matched terms and score components, then ask an unsupported question. Expect explicit abstention instead of an invented answer. Save both cases in the benchmark. Remember that archiving a source does not revoke older published/session copies. Transcripts, exports and backups need their own access and retention review.
Product and guides
Explore creekX Agents · Quick start · Documentation. Written for v0.10 early access, 23 October 2026.
Frequently asked questions
Where should I start?
Read the separate Agents quick start and evaluate v0.10 in a private local workspace before a customer pilot.