Docs · LLMs and developers
Version3.12.1Introduction
What Achiral docs cover and where to start.
Use these docs to understand the parts of Achiral that are live today: the workspace, Chiro, personal executive assistants, memory features, integrations, and APIs.
If you are new to the product, start with Getting started. If you are integrating with Achiral, start with Memory API and API reference.
What Achiral does
Achiral helps a team work with shared context. In the product, that shows up as:
- conversations with Chiro and personal executive assistants;
- teammate and task workflows inside the workspace;
- memory features that preserve useful context over time; and
- APIs for retrieval, inference, and memory operations.
The docs section explains the product surface. Concept essays and research pages explain the underlying ideas separately.
Start here
- Getting started covers signup, organization onboarding, and user onboarding.
- Agents covers durable memory identities for scoped AI workflows.
- Memory API documents the memory inference gateway and workspace memory routes.
- Meet Chiro and your EA explains the difference between the organization assistant and personal EAs.
- ACT-R memory explains memory tiers, governance, and why Achiral memory is not ordinary RAG.
Where to find things
| Section | Use it for |
|---|---|
| Getting started | Signup, organization onboarding, user onboarding, and quick start |
| Agents | Durable memory agents, OpenAI-compatible runtime calls, scoped retrieval, and write-back |
| Workspace | Browser workflows for Chat, Team, Tasks, teammates, and group conversations |
| Memory | Memory types, review flows, habits, and memory APIs |
| Models | Stack of models, Smart router, capability control, and training surfaces |
| Assistants | Chiro, personal EAs, privacy, work context, and assistant lifecycle |
| Reference | API conventions, capability metadata, and request/response examples |
Read ACT-R memory if you need the product's memory model. Read Introduction to ACT-R if you want the theory behind it.
Documentation contents
Start with setup, then move through the product surface, memory model, integrations, API reference, operations, and governance.