The documentation site does not exist. The white paper is the closest thing to it.
There is no documentation site today. If you are looking for the most complete technical description of how Atarla is designed to work, the white paper is currently it. This page describes what dedicated documentation would eventually cover and how it would be kept honest as the software changes.
What documentation would cover.
- Architecture, so a reader understands how the pieces fit before relying on any of them.
- Install and self-host instructions for the components that become open.
- SDK and API references, once either exists.
- Integrations, permissions, and agent interfaces.
- Model and provider support, and Node or deployment guidance.
- Worked examples, a security section, and a contribution guide.
Versioning and honesty about status.
Documentation is intended to be versioned against the software it describes, so a reader on an older build is not shown instructions for a feature that did not exist yet at their version. The plan is for the documentation site to share Atarla's visual system rather than becoming a separate, unrelated brand.
Every documented feature would carry the same status labelling used across this site, so a planned capability reads as planned rather than as something a reader can rely on today.
What is not claimed.
No documentation site exists. Nothing here is versioned, searchable, or hosted yet, and the white paper should be treated as the current technical reference in the meantime.