Answers that show where they came from
Ask your company’s memory a question and get a short answer where every claim points to the passage behind it. When the evidence is not there, it says so instead of guessing.
// An answer as Studio receives it (shortened)
{
"status": "answer",
"answer": "Refunds over 500 EUR need a manager's sign-off [1]. Since March, finance also reviews them weekly [2].",
"citations": [
{
"marker": 1,
"source": "handbook/refunds.md",
"section_path": "Refunds > Approval",
"text": "Refunds above 500 EUR require sign-off from the team manager."
},
{
"marker": 2,
"source": "finance-weekly-2026-03-04",
"text": "From this week, finance reviews all approved refunds every Friday."
}
]
}An answer you can check in one click
Every claim cited
Inline [n] markers point to the exact passage behind each claim, with its source and section.
Abstains instead of guessing
When the evidence does not answer the question, the result says so. Answers are written only from the evidence that was retrieved.
Says when access was the reason
If the asker’s access rules hid the answer, the response carries a policy note instead of pretending the records are silent.
Multi-step retrieval
A retrieval loop breaks hard questions into smaller ones and gathers evidence for each before anything is written.
Secure by design, not by checklist
Cambrian has no certifications yet. What it has is an architecture where access is enforced in the kernel, every decision is explained, and you run it yourself.