GURUIngest and describe
Every source needs an owner, date, language, URL, status, and an explicit use boundary.
Transparent workflow
How Janus.Guru builds a verifiable answer
Janus does not look for a ready-made answer on the open internet. It works inside a selected collection: retrieve evidence, assemble a response, and show the basis. When the basis is insufficient, a bounded answer is better than a confident guess.
The path
Five controls between a question and a response
Split into evidence units
Fragments preserve enough context to be useful without turning every page into one opaque block.
Retrieve and rerank
Semantic and lexical signals are combined before the strongest candidates reach generation.
Generate with guardrails
The assistant is told which language, format, source policy, and refusal boundary apply.
Review the result
Sources, date, edition, and responsibility stay visible for the person who will use the answer.
Scientific basis
What the evidence status means
Janus uses established retrieval-augmented generation, information-retrieval evaluation, and data-provenance practices. QazKnowledge is still reviewing the product's claim-to-evidence passport, so this page does not call the system scientifically proven.
Already testable
Metrics and coverageTechnical evidence
Source contracts, importer tests, retrieval benchmarks, query logs, and public collection limits.
QazKnowledge review
Open QazKnowledgeResearch passport
Claims, bibliography, applicability limits, and periodic review must be linked before publication.
Not proven by a benchmark
Responsibility boundariesBoundary of inference
A retrieval benchmark does not prove every collection, legal conclusion, or deployment decision.