How it works
Datastat Docs keeps one reviewed source for each answer. The same approved page powers the documentation website, local search, and the Datastat agent.
The whole flow is:
Write → review → validate → publish → search or ask
The one-minute version
- An author writes or updates a Markdown page.
- A person who understands the subject reviews its meaning.
- Automated checks reject broken links, invalid metadata, unsafe media, and duplicate routes.
- Publishing makes the page available to the website, search, and the agent at the same time.
- People browse or search the documentation. They can also ask the Datastat agent a question in plain language.
There is no separate copy for the agent. When a source changes, every way of finding that source changes with it.
How information is organized
The product switcher contains several documentation areas. The code calls each area a tenant, but readers only need to choose the area that matches their question.
| Area | What belongs there |
|---|---|
| Datastat Docs | How this documentation system, search, publishing, and the agent work. |
| JudoNet | Installing, operating, and troubleshooting JudoNet. |
| Video CutterV2 | How contest recordings become individual clips. |
| Video Ingester | How videos are uploaded, queued, and encoded. |
| FairReplay | Recording, replay, and related video tools. |
Start in a product area when you need to do something in that product. Stay in Datastat Docs when you want to understand how documentation is found, trusted, or maintained.
One source, three ways to use it
| Experience | What it does |
|---|---|
| Documentation website | Presents a page for a person to read and share. |
| Search | Finds matching titles, headings, descriptions, keywords, and page text. |
| Datastat agent | Retrieves the smallest useful evidence, explains it, and cites the source. |
The agent is a reader of the documentation, not an independent source of truth. A confident answer without supporting documentation is not a documented answer.
What makes an answer trustworthy
Every published page has a stable identity, a canonical URL, a review date, a product area, retrieval keywords, and a record of where it came from. Public pages also pass security and personal-data review before they enter public search or agent output.
The page footer shows when the source was last reviewed. Use the canonical URL in the address bar when sharing an answer so everyone returns to the maintained source.
Where to go next
- Find documentation explains the reader experience.
- How the agent answers explains retrieval, language models, citations, and uncertainty.
- Update the docs shows how to correct a page in the browser or locally, review it, and publish it.