Documentation
Start here to understand what Reticuli is, what users can do with it, and how to move through the product without technical setup details.
Reticuli helps teams turn their own material into assistants that answer in context.
That material can be product docs, support history, policies, research notes, playbooks, links, or example replies. The product is designed to help users move from scattered knowledge to a useful assistant without needing to think about local development, architecture, or repo internals.
What Reticuli is good at
Reticuli fits best when the team already has knowledge worth reusing and wants a better way to turn that knowledge into answers.
- Product documentation to customer assistant
- Support tickets to reply helper
- Internal policies to team copilot
- Research notes to working memory and drafting support
- Course material to study assistant
The basic workflow
- Define the job of the assistant.
- Add the right knowledge and examples.
- Test the answers with real prompts.
- Fix what is weak.
- Share it when it is ready.
Recommended reading order
- Open the user guide.
- Start with Create your first assistant.
- Continue through the rest of the guide in order.
These docs are written for product users first: what to build, what to upload, how to improve answers, and when to share the assistant.