Use case
Use case: answer product questions from repository docs
Use indexed product documentation to answer a concrete question, then inspect the file behind the answer.
Why it matters
Product documentation often explains a feature across several files: an overview, a workflow guide and release notes. Repository search helps when you know the filename or exact term; it is slower when you only know the question.
Krynia lets you ask that question in your own words. The answer remains limited to the files already indexed and links the relevant source sections.
If support tickets or chat contain important context, they are not part of the answer today. Put the stable explanation into a supported document before relying on it here.
Useful for product overviews, workflows and release notes.
The answer can be checked before it is shared.
Unsupported systems are not silently treated as sources.
Related pages
Keep moving through the adjacent evaluation questions.
Use case
Use case: find the first repository document to read
A new colleague asks where to begin, then opens the cited repository documents in a useful order.
Open pageUse case
Use case: recover a decision recorded in documentation
Find a decision only when its explanation is present in the indexed repository or uploaded documents.
Open page